| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 82900 | 2007-09-12 10:56:00 | Network connect ok from c:\ not from d:\ | Hokonui (8280) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 590549 | 2007-09-12 10:56:00 | I have a WinXP install with working network and internet on c:\ -- router at 192.168.1.1 and pc at 192.168.1.2 (and a wireless connection at .3) I have a 2nd clean WinXP install on a different drive of the same pc (e:\). Ie dual boot with everything loaded as above but I can't get a connection to the router when logged on to this install. If I enable DHCP, the assigned pc address is 169.254.140.227 and no connection. If I disable DHCP and enter addresses manually as above the status shows as connected but I can't ping the router and no traffic is sent/received. It would seem I've overlooked something but I don't see what, any help would be appreciated. |
Hokonui (8280) | ||
| 590550 | 2007-09-12 11:22:00 | A 169.254.x.x is a sign of a DHCP that isn't working correctly. Have you tried manually assigning an IP address to the second computer? On the first computer, are you getting an IP from the Router (DHCP) or is it manually assigned? |
Bozo (8540) | ||
| 590551 | 2007-09-12 12:36:00 | Sounds to me like a network card driver problem. If, as you say, it all works fine when running off the C: then it can't be a hardware problem. |
CYaBro (73) | ||
| 590552 | 2007-09-12 22:14:00 | Thanks, I'll try reloading the onboard lan drivers - it shows as working ok in sys devices but there's a problem. I have MAC address filtering active on the router but MAC addresses are unique to the hardware and not reliant on the o/s aren't they? |
Hokonui (8280) | ||
| 590553 | 2007-09-12 22:36:00 | I have MAC address filtering active on the router but MAC addresses are unique to the hardware and not reliant on the o/s aren't they? Yes that's correct. |
CYaBro (73) | ||
| 590554 | 2007-09-12 22:46:00 | A 169.254.x.x is a sign of a DHCP that isn't working correctly. Have you tried manually assigning an IP address to the second computer? On the first computer, are you getting an IP from the Router (DHCP) or is it manually assigned? Thats most likely the problem. Shouldn't be any hardware issues. Download this (majorgeeks.com) and run it on the machine in question. Then reboot, and try to reconnect. |
wratterus (105) | ||
| 590555 | 2007-09-13 22:20:00 | Thanks guys - it does seem to have been a driver problem. The windows generic driver wasn't working properly and neither was the original mboard lan driver but the latest from the chipset maker sorted it immediately. |
Hokonui (8280) | ||
| 1 | |||||