1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows XP network down after repair install

Discussion in 'Networking (Hardware & Software)' started by sempei, 2007/01/17.

  1. 2007/01/17
    sempei

    sempei Inactive Thread Starter

    Joined:
    2007/01/17
    Messages:
    4
    Likes Received:
    0
    Hi all, I need some help here. I had a perfectly functioning XP SP2 network between 2 machines with a 5 port Dlink switch. Then the motherboard died on computer #1 which I was using to share the internet and files with computer #2. I replaced the motherboard and did a repair install of XP and since then no amount of tinkering will bring my network back.
    Both machines are in the same workgroup and use static IP addresses in the same range, ie. 192.168.0.11 and 192.168.0.12. Both subnets are the same, 255.255.255.0. Both machines have Netbios over TCP/IP enabled. I have reset the TCP/IP stacks on both machines. I've removed all phantom entries of the previous motherboard's NIC. Windows firewall is disabled. I run Zone Alarm firewall and AVG anti virus, both are turned off at present time until I get this working.
    Computer #1 with the internet connection cannot see computer #2 in the workgroup or ping it.
    Computer #2 however can see computer #1 in the workgroup, but still cannot ping it.
    I've tried so many things I can't remember them all, please help if you can
     
  2. 2007/01/18
    Dcrypter

    Dcrypter Inactive

    Joined:
    2002/09/19
    Messages:
    158
    Likes Received:
    1
    OK so you did a repair install. Thats ok we can try and fix this. Windows XP runs on the IP stack more or less.
    1) Shutdown the machine remove NIC/disable in BIOS
    2) Get back into windows (let windows do its thing)
    3) Shutdown machine reinstall NIC/enable
    4) Boot back into windows (let windows do its thing again)
    5) Go into the NIC properties (IP and such) dump NetBIOS its a broken protocol
    6) Dump the QoS its a waste of time and no app that I know of uses it, plus it causes problems
    7) Step 5 and 6 do on the other machine
    8) You should only have and require:
    a) Client For Microsoft Networks
    b) File and Printer Sharing
    c) TCP/IP Internet Protocol
    9) Put your IP, Subnet info in
    10) On the local machine open a command prompt. Type ping 127.0.0.1
    11) You should get a response, then ping the local IP you should get another response.
    12) Ping the other machine
    13) If that all works you are good to go. If not move the NIC and or add a NIC and disable onboard.

    Windows XP is goofy how it plays with the NIC settings.

    Make sure all security software is turned off while you are pinging otherwise you will get no response.
    Also try changing your IP (original 192.168.0.11 - New 192.168.0.13) stranger things have happened.

    If all else fails backup data format and start again.

    Hope that helps
     
    Last edited: 2007/01/18

  3. to hide this advert.

  4. 2007/01/21
    sempei

    sempei Inactive Thread Starter

    Joined:
    2007/01/17
    Messages:
    4
    Likes Received:
    0
    Didn't solve the problem

    Followed that procedure and had no luck.
    Formatting and reinstalling is not my option of choice at this time. I have so much loaded on the computer the time to restore would be phenomonal.

    At this time, both computers are showin in the workgroup in Primary computer, however Backup computer states the workgroup is not accessible. Still cannot ping between the 2 however each one can ping itself and the loopback. After trying to access the workgroup from Backup, I checked the event log and it states:
    "The name Workgroup could not be registered on the interface with IP address 192.168.0.2. The machine with IP address 192.168.0.1 (which is IP for Primary) did not allow the name to be claimed by this machine "


    Still looking for help...
    Thanks
     
  5. 2007/01/22
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    4,076
    Likes Received:
    178
    By any chance is the name of any computer Workgroup and the workgroup name is also Workgroup ?
     
  6. 2007/01/22
    sempei

    sempei Inactive Thread Starter

    Joined:
    2007/01/17
    Messages:
    4
    Likes Received:
    0
    The workgroup name is the same on both computers, both computers have different names not the same as the workgroup name
     
  7. 2007/01/23
    Dcrypter

    Dcrypter Inactive

    Joined:
    2002/09/19
    Messages:
    158
    Likes Received:
    1
    The only other thing I can think of is make sure that both computers have unique names and move them into a differently named workgroup.
     
  8. 2007/01/24
    sempei

    sempei Inactive Thread Starter

    Joined:
    2007/01/17
    Messages:
    4
    Likes Received:
    0
    Tried that too

    I have already tried different computer names and 3 different workgroup name, always the same result
     
  9. 2007/01/31
    jmatt

    jmatt Well-Known Member

    Joined:
    2002/01/12
    Messages:
    189
    Likes Received:
    0
    Have you enabled NetBios?
    Control Panel > Network Connections > Right-click your main network connection, choose
    Properties > Networking, Double-click "Internet Protocol (TCP/IP)" > Click Advanced button > Select WINS tab.
    Click > "Enable NetBIOS over TCP/IP. "

    Network Troubleshooting and Check Lists
    http://www.chicagotech.net/nettroub...
    Another common problem in mixed (win95/98, NT, ME, Win2K and XP) workgroup network is name resolution. If you can ping IP but not computer name, this may be a NetBIOS issue. You may try to enable NetBIOS over TCP/IP on win2K/XP if you don't have WINS server. For some reasons, you just can't ping the computer name even you enable the NetBIOS over TCP/IP, you may try to install NetBEUI on win2K/XP. If you can't see other computers but you can map the other computers' shared folder using UNC (\\computername\sharedfolder), this may be master browser issue. You may want to disable master browser on W2K/XP in a small mixed OS workgroup network.

    Common NetBIOS name problem
    http://www.chicagotech.net/netfaqs.htm
    NetBIOS names must be between 1 and 15 characters long (the names are up to 16 characters, but the last character is reserved as a special characters). For that reason, you should not give a computer name longer than 15 characters.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.