Networking help

earthling30

Senior member
Mar 18, 2004
483
0
0
I've been searching this forum and THIS is what I found that is very similar to my problem. I've even replied to it but no one has answered my question.

Here is my confuser troubles.
My winXP PC was connecting to my Linksys router just fine then one day, all of a sudden, it decides that it doesn't want to accept the IP address that the DHCP server issues from the router, which wouldn't allow it to connect to the internet, router, or the other computers. :confused:

I tried the following:
1. From the run command typed in CMD.
2. ipconfig/flushdns
3. ipconfig/registerdns
4. ipconfig/release
5. ipconfig/renew
6. Uninstalling the Ethernet card, restart and let it reinstall
7. Updated the drivers for my Ethernet card
8. Made sure all of the appropriate services are running
9. Even tried uninstalling the TCP/IP protocol in the network properties (unsuccessful in doing this, it wouldn't let me)
10. I finally had to assign a static IP address on that PC and it connects just fine. (i.e. IP Address 192.168.1.XX, Subnet Mask 255.XXX.XXX.XXX, Gateway 192.168.1.XX, DNS Servers 1ST 24.168.XX.XX 2ND 64.74.XX.XX)

My question is, what in the world causes this? How do you fix it? I would rather my pc obtain an IP address automatically if at all possible but it want. My pc is free of viruses (ran full virus scan 2 days ago), adware, and spyware (scanned for these the same day as the virus sys scan), man I'm about ready to say @#$%^%^ :confused: with it. BTW I found some of these things on some other forums.

I have noticed that the whole time this was happening, on the front of my router I have activity lights and the PC that I'm having trouble with stayed on even with the PC off but my other hard wired PC shuts off. Could this be something to do with it? Now, after some time has gone by, the lights on the router shut off with the PC. Dude 'm like confused as to what is going on here. I'm usually pretty good about trouble shooting, but with Networking it's all different.
:confused:
Thanks in Advanced!
 

JackMDS

Elite Member
Super Moderator
Oct 25, 1999
29,563
432
126
First go over all Network Settings.

Log to this page it has a lot of links to instructions to Windows Network Settings, and Sharing.

Link to: Windows Network - Installing & Sharing.

If every thing check right it is possible that the TCP/IP Stack is partially "Trashed" (AS an Example, repetitive usage of the Network Wizard might cause this "Trashing").

When this "Trashing" occurs it is quite common that the Internet connection would work correctly, and File Sharing would not.

What to do?

Option 1. Uninstall the Network, reset the TCP/IP Stack, and Reinstall the Network.

Link to: How to Reset Internet Protocol (TCP/IP) in Windows XP.

Option 2. Leave every thing as is. Install NetBEUI, and Bind NetBEUI to File Sharing.

Link to: Set NetBEUI as the Default Sharing Protocol in WinXP.


Why NetBEUI?

NetBEUI is very simple it just uses the computer name does not need the complicated IP system.

TCP/IP uses the IP system which involved numerous amounts of Registry lines with variety of information.

Action like the network Wizard, some Network Application, and Tweak utilities make changes to the Registry without erasing previous information. As a result sooner or later the registry contains conflicting information and Sharing through TCP/IP get Sc** Up.

In addition many computer have applications like Firewalls, Antivirus etc, that intercept the TCP/IP some of them might interfere with the proper work of TCP/IP impeding File Sharing.

NetBEUI is fast simple solution.


:thumbsup:
 

earthling30

Senior member
Mar 18, 2004
483
0
0
Thanks JackMDS for the reply! I'll give that a try later, I'm away from my PC at the moment.
I'll keep you posted!
 

spidey07

No Lifer
Aug 4, 2000
65,469
5
76
Originally posted by: earthling30
Option 1. Uninstall the Network, reset the TCP/IP Stack, and Reinstall the Network.

Link to: How to Reset Internet Protocol (TCP/IP) in Windows XP.
Thanks JackMDS for the reply! Your response listed above worked like a charm! I'll have to add this to my long list of notes.
:D

hmmm...so XPs stack can get fubarred?

Interesting, I thought MS had pretty much fixed those problems. Nice link Jack.