Can't connect to LAN Workgroup from XP. - by Ostriig
Ostriig on 27/7/2009 at 18:20
Now it works. Just like that. I looked into the stuff you guys told me to yesterday and it was still going hurr durr error on me, and now, a day later, after having done nothing more, it's working. I don't get it.
Hm, I remember that I had this one thing last week when I disabled the wireless, then unplugged the LAN cable from the desktop and stuck it in the laptop. Could that have, I don't know, confused the router somehow? Though that still wouldn't explain why it's working now all of a sudden, while resetting the bloody thing yesterday did nothing.
Al_B, the mapping command I haven't tried, but I will the next time it acts up this way. Naturally, I hope it won't, but I'm not much of an optimist.
Thank you both very much for your help! And thank you for the offer, Biker, I really appreciate it!
Al_B on 27/7/2009 at 18:49
Glad it's working now. I have seen problems where switching from one physical LAN to another with the same network address can cause problems when it doesn't do a full DHCP renew. I would suspect something similar may have happened in your case and that your DHCP lease expired between yesterday and today.
However, that doesn't quite tie up as you did a repair on your connection which should have forced the same thing.
Ostriig on 27/7/2009 at 19:37
I did run repair, it was the very first thing I tried when I started getting the error.
However, assuming that changing the physical connection was the source of the problem, what would be the proper way to do it so as to avoid the problem in the future? I think I just directly Disabled the wireless, rather than disconnecting from the network first, and then plugged in the cable. Should I have first disconnected from the network (without disabling the wireless, or doing it after), and then plugged in the cable? Or even do a full reboot?
bikerdude on 27/7/2009 at 21:13
Quote Posted by Ostriig
However, assuming that changing the physical connection was the source of the problem, what would be the proper way to do it so as to avoid the problem in the future?
The router should be smart enough to do it for you, but a sure fire way of avoiding this is to release the Ip address before changing connection type.
1. Click start>run and type 'cmd'
2. In the cmd prompt type " ipconfig /release "
3. Disconnect/disable said connection and reboot.
4. Upon booting choose connection type and windows will automatically pickup an IP from the chosen connection.
:thumb:
Ostriig on 27/7/2009 at 21:32
Right, thanks! I'll do that next time I need to switch the connection, though I should probably see to testing whether it's the swapping and DHCP lease that was the source sometime. Probably when I have a few free days in a row in which I don't expect to use the workgroup much.
bikerdude on 28/7/2009 at 00:10
Quote Posted by Ostriig
I should probably see to testing whether it's the swapping and DHCP lease that was the source sometime.
The router should habd out a different Ip, as the ne wmac address on the wifi and network adapter are different - what is the make and model of the router..? I would consider upgrading the firmware.
Ostriig on 28/7/2009 at 13:05
All it says is O2 Wireless Box II. I wouldn't be surprised if it's a turd.
bikerdude on 28/7/2009 at 15:22
Quote Posted by Ostriig
All it says is O2 Wireless Box II. I wouldn't be surprised if it's a turd.
Thats probably the same box as I have (Im with O2 aswell), well I know for a fact it will assign different IP's for different adapters on the same computer... so dont whith out seeing it in person is going on with yours..
Ostriig on 28/7/2009 at 15:36
Hm... I'll have to look into it. I never checked the IP when on the cable connection, though if I recall correctly, the router has a single IP assigned to give to the laptop. I'm leaving on a two weeks' holiday this Thursday, though, so I'll have to check it when I come back.
dvrabel on 28/7/2009 at 18:45
Quote Posted by Bikerdude
...it will assign different IP's for different adapters on the same computer...
This is the correct behavior. An IP address is a property of a network interface, not the whole machine.
