I have (some of the time) a recently set-up wireless network. Router is wired to a windows 7 pc, and there is an XP machine with a USB adapter as well. Both PCs are switched on, and the XP shows a wireless connection with a "very good" signal. When I try to start IE on the XP it fails to connect. When I then run the network diagnostic the connection dies, at about the point where the diagnostic attempts to re-enable the adapter. The diagnostic output reports "Error renewing IP address: semaphore timeout period has expired", and "Default gateway 0.0.0.0". If I then run ipconfig /all there is absolutely NO output. This happened yesterday, so I manually reset the IP following the instructions in 299357, and same thing has happened again. I did the reset again, and re-booted the XP. The router shows it has recognised the XP, and ipconfig /all on XP shows various things, includingIP address 192.168.2.6; subnet mask 255.255.255.0; default gateway,dns server, and dhcp server as 192.168.2.3 (router's IP address); dhcp and autoconfiguration enabled. IP routing and WINS proxy are disabled.While I was typing the above the router has lost sight of the XP box, although the XP box still reports a 'very good' signal and a continued connection.So far I've had this network in place for 10 days, but only been able to use the connection to the outside from the XP pc on one day, which followed my re-configuring the router to make its IP address 192.168.2.3 rather than 192.168.2.1 as recommended in the set-up, because 192.168.2.3 was what the XP box was trying to connect as. Both pcs were turned off overnight, and worked fine when started the next morning for the whole day. The next day the XP had a connection for long enough to get to the website where I was looking for updated printer drivers, then lost it when I started to download them, and nothing since. The IP information now suggests that I might have some joy for a while if I again reset the router's IP address to 192.168.2.6 this time, but I don't see why I should have to keep doing that.Running some of the other TCP?IP connectivity troubleshooting:ping 127.0.0.1 returns OK; ping 192.168.2.3 times out; ping 192.168.2.6 is OK; ping host name doesn't work (Assuming that the host-name is just the computer name of the win 7 pc); pathping 192.168.2.6 works.(If what that shows is in fact the hostname then pinging that name doesn't work either; there are no entries in the ARP cache; don't know any valid IP addresses to test those.Suggests that I have issues with the default gateway, and the name resolution, but I don't know how to set about resolving them, unless by changing the router's IP address, which may do the first, but not the second.Suggestions welcome. The fact that things worked fine for a day suggests that the hardware is OK, and I have checked that I have the latest firmware for both the router and the USB adapter. The router's security is disabled, as is the firewall on the XP, neither of which is ideal1 person needs an answerI do too

Actually, my first instinct was that the wireless adapter on the XP machine sounds flakey. What if you give the XP machine a static IP address, say 192.168.2.7, with the proper gateway and subnet information as you have now. Does that work? -B- http://www.officeforlawyers.com Author: The Lawyer's Guide to Microsoft Outlook

Eventually Belikin's tech support decided that the adapter was flakey too, and needed to be replaced. So they referred things to the Customer Support, and I haven't heard from them since, apart from s amessage which seemed to query whether or not I'd registered it with them..................So what about the network?Packed up the wireless router, and got some devolo kit for a powerline (over the mains electricity) network set up instead. More expensive, yes but IT WORKS !!!! 6 weeks later, still no problem accessing Internet from either PC.