rockinup1231
08-01-2010, 11:04 PM
I've exhausted Google and my own networking knowledge on this issue for the past two days. I didn't really want to have to ask for help but, meh.
Anyway..
My father recently had cable internet installed in his home for the new computer I built for him. He wanted to have wireless set up for my laptop and other devices they may obtain later on, but didn't want to spend $50 on a new wireless router. I offered up one of my spare USB wireless adapters (a NETGEAR W111 v2) to the cause.
I managed to get an ad-hoc network going that is visible to my Windows 7 laptop. However, when I try to connect (with DHCP enabled on my Win7 laptop), it comes up with a default ip address (one in the 169.xxx.xxx.xxx range), and fails to completely connect to the network. Likewise, it doesn't get any internet access.
I tried using static ip addresses. I set the ip of the wireless adapter on the XP Machine to 192.168.0.1, and the netmask to 255.255.255.0. On the laptop, I set its ip address to 192.168.0.2, the netmask the same as the XP machine, the default gateway to 192.168.0.1, and the preferred DNS server to 192.168.0.1.
Initially with this setup, I was unable to detect the ad-hoc network. Then I read something that mentioned that the workgroups should be the same (which I had overlooked before), so I changed their workgroups to "WORKGROUP" and now the laptop can detect the XP ad-hoc network, but the end-result is only partial connectivity and no internet access.
ICS is enabled on the XP machine. There is no encryption or security of any kind set up on the connection. I know the adapter is good since I've used it for ad-hoc on a different machine prior, and for normal use as well; worked fine then.
And ya know, I'm sure it's something simple I've overlooked (it seems like it always is) but I can't think of what it could be.
Any ideas?
Relevant specs:
The PC:
OS: Windows XP SP3 (I had a license for Windows 7 Pro from my college I was willing to sacrifice for his computer but he wanted XP...)
My laptop:
OS: Windows 7 Home Premium x64
Anyway..
My father recently had cable internet installed in his home for the new computer I built for him. He wanted to have wireless set up for my laptop and other devices they may obtain later on, but didn't want to spend $50 on a new wireless router. I offered up one of my spare USB wireless adapters (a NETGEAR W111 v2) to the cause.
I managed to get an ad-hoc network going that is visible to my Windows 7 laptop. However, when I try to connect (with DHCP enabled on my Win7 laptop), it comes up with a default ip address (one in the 169.xxx.xxx.xxx range), and fails to completely connect to the network. Likewise, it doesn't get any internet access.
I tried using static ip addresses. I set the ip of the wireless adapter on the XP Machine to 192.168.0.1, and the netmask to 255.255.255.0. On the laptop, I set its ip address to 192.168.0.2, the netmask the same as the XP machine, the default gateway to 192.168.0.1, and the preferred DNS server to 192.168.0.1.
Initially with this setup, I was unable to detect the ad-hoc network. Then I read something that mentioned that the workgroups should be the same (which I had overlooked before), so I changed their workgroups to "WORKGROUP" and now the laptop can detect the XP ad-hoc network, but the end-result is only partial connectivity and no internet access.
ICS is enabled on the XP machine. There is no encryption or security of any kind set up on the connection. I know the adapter is good since I've used it for ad-hoc on a different machine prior, and for normal use as well; worked fine then.
And ya know, I'm sure it's something simple I've overlooked (it seems like it always is) but I can't think of what it could be.
Any ideas?
Relevant specs:
The PC:
OS: Windows XP SP3 (I had a license for Windows 7 Pro from my college I was willing to sacrifice for his computer but he wanted XP...)
My laptop:
OS: Windows 7 Home Premium x64