Ad Hoc networks

[ffutures]

Trying to set up an ad-hoc wireless network for my bro-in-law and can't seem to get the damned thing to work. I'd appreciate comments from anyone who knows this stuff:




The idea is that their main computer (windows XP, 802.11g network adaptor) will connect to the internet, while the laptop (windows 98, 802.11b) will connect to that when needed. The laptop is my old one and was working fine with the router I have up here, but I can't seem to get either to work at all on an ad-hoc basis - they seem to be aware of each other's existence but they can't exchange data, even with encryption switched off, and the laptop can't connect to the internet. The odd part is that I can't contact either via the iBook, although I can pick up the signal, which makes me think that something has gone wrong with the actual setup, but I have no idea what. I've tried to make it as simple as possible. My prime suspect is the firewalls on both PCs, but even when I disabled firewalling on the wireless connection on the main PC nothing happened. I used Windows network setup on the XP machine to make a setup disk for the laptop, and I really don't quite understand why it isn't working.

I would have preferred to build a proper router-based setup; a guy at work said he had one spare, but it turned out to be an ADSL modem/router, and sod-all use for cable. It then turned out that the 802.11g card he also had doesn't work properly with Windows XP SP2, so bro-in-law got a USB adaptor instead. It was my idea to get 11g rather than 11b, since it is supposedly downward compatible, and I'm praying that this isn't part of the problem.

Anyway - what I would be grateful for is some default settings for an ad-hoc network like this, or suggestions for alternatives. And not too much mocking laughter...

Comments

[bellwethr.livejournal.com]

So, this (http://www.practicallynetworked.com/sharing/xp_ics/) page indicates the host computer network adapter (the wireless one in this case) should automatically have it's IP set to 192.168.0.1. The client laptop should have it's IP set to something else in the 192.168.0.x subnet (like 192.168.0.2). You'll likely also need to set up the gateway (192.168.0.1) and subnet mask (255.255.255.0) and broadcast (192.168.0.255). Nameservers will likely be whatever the main PC uses. After setting this up, you should be able to test connectivity by pinging 192.168.0.1 from the laptop.

Now, if the primary network adapter on the main PC is also using addresses in the 192.168.0.x subnet, you may have a problem.

[ffutures.livejournal.com]

Thanks - I'll try that tomorrow evening.