Matthew Hill
January 9th 04, 09:52 PM
I am running a peer-to-peer network, using a Netgear USB
adaptor on the host and a Netgear PCMCIA card on the
client.
If I run the networking wizard on the client, it sets the
IP to 169.254.155.150 with a subnet of 255.255.0.0 which
I believe to be a (deliberately) invalid address
(according to Netgears Tech. Support) that is generated
when there is a poor connection.
However, if I manually configure the IP addresses as
follows, the network will allow me to share files between
the two machines:
IP: 192.168.0.2
Subnet: 255.255.255.0
Gateway: 192.168.0.1
DNS: 192.168.0.1
With this configuration though, Internet Connection
Sharing simply refuses to work. I have followed the MS
Help & Support Tutorial for networking, and doesn't solve
the problem, only telling me what I already know.
Does anyone else have this problem, and any insights into
it woyuld be greatfully appricated.
Incidentally, everything (file and internet connection
sharing) did work before I took the laptop on vacation,
where I was plugging it into a hard-wired ethernet
network, although I don't see how this would affect
anything. I have even gone to the extent of repairing
Windows in case of registry errors. When connected to
the hard-wired network, it also gave Internet Connection
Sharing problems (at initial connection) but after
several refresh attempts in Explorer it started to work.
However, this practice does not work for the wireless
setup.
Using the ipconfig /release and /renew commands report
that the DCHP server is unavailable. I know (well, think)
that this is a router function, but as the network is
peer-to-peer surely Windowes would assign an address in
the 192.168.0.x range, or whatever?
Any help really would be appreciated.
Thanks,
Matt.
adaptor on the host and a Netgear PCMCIA card on the
client.
If I run the networking wizard on the client, it sets the
IP to 169.254.155.150 with a subnet of 255.255.0.0 which
I believe to be a (deliberately) invalid address
(according to Netgears Tech. Support) that is generated
when there is a poor connection.
However, if I manually configure the IP addresses as
follows, the network will allow me to share files between
the two machines:
IP: 192.168.0.2
Subnet: 255.255.255.0
Gateway: 192.168.0.1
DNS: 192.168.0.1
With this configuration though, Internet Connection
Sharing simply refuses to work. I have followed the MS
Help & Support Tutorial for networking, and doesn't solve
the problem, only telling me what I already know.
Does anyone else have this problem, and any insights into
it woyuld be greatfully appricated.
Incidentally, everything (file and internet connection
sharing) did work before I took the laptop on vacation,
where I was plugging it into a hard-wired ethernet
network, although I don't see how this would affect
anything. I have even gone to the extent of repairing
Windows in case of registry errors. When connected to
the hard-wired network, it also gave Internet Connection
Sharing problems (at initial connection) but after
several refresh attempts in Explorer it started to work.
However, this practice does not work for the wireless
setup.
Using the ipconfig /release and /renew commands report
that the DCHP server is unavailable. I know (well, think)
that this is a router function, but as the network is
peer-to-peer surely Windowes would assign an address in
the 192.168.0.x range, or whatever?
Any help really would be appreciated.
Thanks,
Matt.