tklange
06-01-2005, 11:53 PM
Hi All,
I'm new to this forum but after reading some posts, it appears there are some intelligent people here. I consider myself pretty darn computer savvy (as do 95% of my friends who don't like to pay for others for tech support I can provide them for free!) but I am totally STUMPED with this one:
I built my friend a new PC (Asus motherboard w/ built in LAN, Athlon 2800+ 64bit, dual drives, etc...). Not quite "the works" but in the top 1/2, I'd say, with really good room for future expansion. I set it all up at my house with my DSL connection. ALL known updates were done to Win XP Pro w/ SP2, software, drivers, firmware, BIOS, you name it. It was all working just peachy and I was actually quite envious of it compared to my year old system. There was nothing more that could be done to it so I released it to him today.
He took it home, unplugged his old boat anchor (also a Win XP Pro machine) from his DSL connection, plugged in this one and... ... nothing. Both DSL connections are the “always on” variety with no username, account, passwords or anything else needed.
No internet detected whatsoever. The old system can be swapped back and confirms that the DSL signal and the DSL modem are present and working fine at his house. The new system clearly detects a network but won't find any web site or connect using any other software that needs the internet. The modem is connected directly into the PC - no routers used.
Everything I can think of (and then some) has been checked. NIC diagnostics are good, networking is all set up (just the basics that XP installs - the same ones that had work fine at my house) and gets numbers assigned as needed (no pre-assigned IP numbers, gateways, etc), "Repair" fails with a generic non-specific error to contact the LAN person. I've tried ipconfig in every way I could think of, any other commands I could find online (arp, nbtstat, flushing and registering dns, netsh, many others I could list as well). Nothing seems to get the DHCP to generate an IP address beyond the generic 169.254.x.x that gets assigned when it can't find what it is looking for (i.e.: a real IP address assigned by the DSL host).
ANYONE know why this system is not getting an IP address automatically assigned? I’ve disabled firewalls and experimented with about every setting I can think of with no luck. I am truly stumped (but still searching the net for that elusive answer to all this).
Do I have to wait a day or more for some DSL signal to reset some internal numbers to make it all work?? Anyone have insight to how DSL behaves?
THANK YOU in advance if you solve this one.
I'm new to this forum but after reading some posts, it appears there are some intelligent people here. I consider myself pretty darn computer savvy (as do 95% of my friends who don't like to pay for others for tech support I can provide them for free!) but I am totally STUMPED with this one:
I built my friend a new PC (Asus motherboard w/ built in LAN, Athlon 2800+ 64bit, dual drives, etc...). Not quite "the works" but in the top 1/2, I'd say, with really good room for future expansion. I set it all up at my house with my DSL connection. ALL known updates were done to Win XP Pro w/ SP2, software, drivers, firmware, BIOS, you name it. It was all working just peachy and I was actually quite envious of it compared to my year old system. There was nothing more that could be done to it so I released it to him today.
He took it home, unplugged his old boat anchor (also a Win XP Pro machine) from his DSL connection, plugged in this one and... ... nothing. Both DSL connections are the “always on” variety with no username, account, passwords or anything else needed.
No internet detected whatsoever. The old system can be swapped back and confirms that the DSL signal and the DSL modem are present and working fine at his house. The new system clearly detects a network but won't find any web site or connect using any other software that needs the internet. The modem is connected directly into the PC - no routers used.
Everything I can think of (and then some) has been checked. NIC diagnostics are good, networking is all set up (just the basics that XP installs - the same ones that had work fine at my house) and gets numbers assigned as needed (no pre-assigned IP numbers, gateways, etc), "Repair" fails with a generic non-specific error to contact the LAN person. I've tried ipconfig in every way I could think of, any other commands I could find online (arp, nbtstat, flushing and registering dns, netsh, many others I could list as well). Nothing seems to get the DHCP to generate an IP address beyond the generic 169.254.x.x that gets assigned when it can't find what it is looking for (i.e.: a real IP address assigned by the DSL host).
ANYONE know why this system is not getting an IP address automatically assigned? I’ve disabled firewalls and experimented with about every setting I can think of with no luck. I am truly stumped (but still searching the net for that elusive answer to all this).
Do I have to wait a day or more for some DSL signal to reset some internal numbers to make it all work?? Anyone have insight to how DSL behaves?
THANK YOU in advance if you solve this one.