Windows XP wont connect to Router/internet
I've read a bunch of threads on similar problems but no one has quite the same problem, so here goes.
I put a new processor, mobo, hdd into my tower. After some problems installing I got windows xp installed, right off the bat my onboard network adapter wont connect to my router, even though it's connected. I tried pinging the router and nothing. My laptop has no problems connecting.
I saw the article on slip streaming, so i have service pack 3 installed, installed router drivers, nlite (not sure what it does, hate to admit it but i'm ignorant of what SATA does or how to configure. I know it's faster, but been awhile since i've built). I'm thinking of just taking my machine to a repair shop, but the one i want to go to is closed today. So if you guys can help it would save me some cash.
Here are my stats
Win XP
Phenom II 2.8 gb quad core
Biostar A770E3
Pny 4gb Dimm DDR3
Hitachi 500gb HDD
Not sure what else you all need, so just let me know.
also, I did turn my onboard Network Adapter on in Bios
Thanks
Jon
I put a new processor, mobo, hdd into my tower. After some problems installing I got windows xp installed, right off the bat my onboard network adapter wont connect to my router, even though it's connected. I tried pinging the router and nothing. My laptop has no problems connecting.
I saw the article on slip streaming, so i have service pack 3 installed, installed router drivers, nlite (not sure what it does, hate to admit it but i'm ignorant of what SATA does or how to configure. I know it's faster, but been awhile since i've built). I'm thinking of just taking my machine to a repair shop, but the one i want to go to is closed today. So if you guys can help it would save me some cash.
Here are my stats
Win XP
Phenom II 2.8 gb quad core
Biostar A770E3
Pny 4gb Dimm DDR3
Hitachi 500gb HDD
Not sure what else you all need, so just let me know.
also, I did turn my onboard Network Adapter on in Bios
Thanks
Jon
0
Comments
Is your computer connected to the route via wired or wireless?
What is the make and model of your router (or just make if you can't find the model number)?
Can you please do this while you are connected to the router:
1. Go to the Start menu
2. Click Run
3. Type "cmd" and press enter
4. A black console should show up, type "ipconfig /all" and press enter
5. Right click anywhere in the text, and select all
6. right click again now that the text is highlighted, and click copy.
7. paste the results here.
----
Regarding SATA and nlite...these are things unrelated to your network problem. They have to do with hard drive interfaces and booting. So you do not have to worry about these things.
Meanwhile, you should NEVER have to install drivers for a router.
I cant copy/past (i'm on my laptop) so here is the info
Host name .............commputer
Primary Dns Suffix.......... (blank)
Node Type.............Broadcast
IP Routing Enabled..........no
WINS Proxy enabled.......no
Ethernet adapter Loccal Area Connection:
Connection-specific DNS Suffix...hsd1.co.comcast.net
Description....................Realtek PCIe GBE Family controller
Physical Address............00-30-67-BB-6F-25
DHCP Enabled................yes
Autoconfiguration Enabled...Yes
IP Address....................0.0.0.0.0
subnet mast..................0.0.0.0.0
Default Gateway............(blank)
DHCP server................... 192.168.1.1
DNS ............................68.87.85.102
68.87.69.150
as a side note, i cannot see any connection anymore either in my notification or in the network
connections folder.
*edit* wired connection. that worked until i intalled all this new equipment.
First:
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
Go there and download the top file in the list:
"WinXP, Win2K, Win2003 Auto Installation Program (SID:1462015)"
Get this file on to the computer that does not connect to the Internet and we will use it later.
Next:
1. Right click "My Computer" on your desktop and left click properties
2. Go to the hardware tab and click device manager
3. find your Realtek controller listed under the network adapters or communication devices (I forget in WinXP exactly)
4. Right click it and select uninstall
5. When it is finished removing the device go to the file you downloaded and run through the installation
It will likely ask you to restart, and hopefully when you are done you will be connected to the Internet.
If not there could be an issue with your TCP/IP stack and we may need to repair it.
I'd try this:
1. If you did not run the software from the last post, run it to make sure you have the right driver installed.
2. If that doesn't fix it right off, follow steps 5-9 in this guide:
http://portforward.com/networking/static-xp.htm
using these numbers:
ip address: 192.168.1.10
subnet mast: 255.255.255.0
gateway: 192.168.1.1
primary dns: 192.168.1.1
secondary dns: <leave blank>
Once all that is set give her another whirl.
Let me know if that takes care of it.
This is all based on a fresh install of Windows right?
If so it is very unlikely your tcp/ip stack is corrupt. I still feel like there may be some weird incorrect driver installed.
Are there other computers connected to the router that work?
Also, did you try entering a static ip?
If that doesn't fix it right off, follow steps 5-9 in this guide:
http://portforward.com/networking/static-xp.htm
using these numbers:
ip address: 192.168.1.10
subnet mast: 255.255.255.0
gateway: 192.168.1.1
primary dns: 192.168.1.1
secondary dns:
If it is too late sorry we couldn't help you out in time. Best of luck getting it fixed and welcome to Icrontic!
Have you tried simply power cycling the router?
Are there any computers hooked up to the same router that work?
http://support.microsoft.com/kb/822123
There is something screwy with the dhcp. It isn't flat out not working otherwise you would get a Windows assigned 169.254.etc. Instead you get this 0.0.0.0.
A quick google search revealed the kb article above which looks like it could really help you out. You just need to have the patience to run through the steps. It shouldn't take more than 15 minutes.
When you do this:
Right-click My Computer, click Manage, and then click Device Manager under Computer Management.
Expand Network Adapters
What is listed under Network Adapters? Anything?
Method 3: Verify That the Dynamic Host Configuration Protocol (DHCP) Client Service Is Started
Verify that the DHCP Client service is started. To do so, follow these steps:
Right-click My Computer, click Manage, expand Services and Applications under Computer Management, and then click Services.
Verify that the DHCP Client service is running.
If the service is stopped, right-click DHCP Client, and then click Start.
Also right click on DHCP, select "Properties" and the "General tab". Then make sure that automatic is seclected, click apply and OK.
No, not really. The router light is on for the cable connect from the server, and the nic light is on. Both are natively IPv6, and are talking to each other, or both lights would not be on. Problem is not with card or router, that much was gotten right.
Meanwhile, XP thinks it has a IPv4 device pair, and tries to set up an IPv4 stack for it. XP can barely recognize an IPv6 addressing device. The stack setup will have to be completely manual, and I wouldd get Comcast tech support to do that.if they will.
John
This is a great question, my next is: Are all devices connecting to this access point experiencing the same problem?
If the cable/NIC is detected and this is the only machine having the problem, try rebuilding TCP/IP Stack and Winsock via the below commands via Start>Run>cmd
netsh int ip reset reset.log
netsh winsock reset catalog
Make sure you reboot after running these commands. Should you still be unable to establish a connection, make sure any Firewall software you have installed is disabled temporarily (Norton, McAffe, and other Anti-Virus applications commonly include a firewall component).
Should you not have any, make sure you temporarily disable the Windows Firewall by typing the following command in Start>Run>cmd
Disable Firewall: netsh firewall set opmode disable
To reenable it later: netsh firewall set opmode enable
It was the way you worded your original post that sparked the derp? I believe. In essence, why not just say remove ipv6 from the stack? There are some easy step by steps to do that in WinXP. Regardless, I think the guy took it to the shop. We may never know if this was resolved.
GG all, I'm proud of everyone who tried to help