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.

Win98 can't see Windows 2000 Server

Discussion in 'Networking (Hardware & Software)' started by eisenerg, 2006/01/16.

  1. 2006/01/16
    eisenerg

    eisenerg Well-Known Member Thread Starter

    Joined:
    2002/01/07
    Messages:
    40
    Likes Received:
    0
    Hello all,
    Specs:
    Server1: Windows 2003, domain=XXXXXX03, PDC
    Server2: Windows NT4.5, domain=XXXXXX (same as Server 1 without 03)
    Server3: Windows 2000, BDC, domain=XXXXXX03

    Workstations: Mixture of Win98, Win2000 & WinXP

    All workstations log into Server1.

    Two weeks ago, everything was fine. Then I installed a new network card in Server 3 (It is a Compaq server and I installed an approved Compaq NIC). The installation seemed to go fine, I was able to see Server3 from Server1 and from a Win2K workstation. Next day I find out that Win98 machines can't connect to Server3. I check the lmhost file, the ip address and server name is in there. Go to network neighborhood and the server name shows up in the list, but when I click on it I eventually get an error:
    \\{server3} is not accessible
    The computer or sharename could not be found. Make sure you typed it correctly, and try again.
    After banging my head for about a day I uninstalled the new NIC and set everything back the way it was. Unfortunatly the problem stayed. I still can not access server3 with a Win98 workstation. These workstations can access both of the other servers.

    Any Ideas?

    J.
     
  2. 2006/01/16
    McTavish

    McTavish Inactive

    Joined:
    2005/06/24
    Messages:
    576
    Likes Received:
    1
    You are binding the required protocol to the NIC card? This is not really my area but perhaps the 98 machines are configured for NetBEUI while everything else is on NetBIOS – or vice versa.
     

  3. to hide this advert.

  4. 2006/01/16
    eisenerg

    eisenerg Well-Known Member Thread Starter

    Joined:
    2002/01/07
    Messages:
    40
    Likes Received:
    0
    Hi McTavish,
    Everyone is NetBios.
     
  5. 2006/01/17
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    Was the new card assigned with a different IP address? If so the problem could be in your WINS and or DNS. Check the DNS setting for the server (what does NSLOOKUP say for the server's IP address) and flush the WINS database.

    One thing that would definitely change would be the MAC address (as that is assigned to the network card in manufacture). Have you used an ARP set up to match an IP address to a MAC address anywhere.

    Uninstall NetBEUI. You don't need it, and all it will do is add unwanted traffic.
     
  6. 2006/01/17
    eisenerg

    eisenerg Well-Known Member Thread Starter

    Joined:
    2002/01/07
    Messages:
    40
    Likes Received:
    0
    Hey ReggieB,
    I had pinged the server's IP address and it worked so I didn't think any more of it (Other than the confusion of well, I can ping the stupid thing, why can't I see it). After reading your reply I pinged it again only with the server name. I noticed right away that when it resolved the name it was the wrong address. Went in to the WINS console on the main server and for some reason it had been asigned a different address by the WINS server. Straightened that out and everything is fine again. Thanks for your help.

    J.
     

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.