Windows Forum

Ask something
Discussion Locked

TCP/IP problems Win2000srv /Win98 WS

0 helpful
9 replies

by mark

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have just setup a Windows 2000 server as the Primary Domain. The server name is mainsrv and the domain is SLTL I am not on the internet and setup the Server with the default setting using "local" in my DNS setup. The server is 10.10.1.1 & 255.0.0.0 as a subnet. When I boot the server I get no errors in any event log. When I run ipconfig /all everything looks great. I can ping my sever by name "mainsrv"

When I attempt to log in with a Win98 workstation (setup correctly) using a ip of 10.10.1.2 and subnet of 255.0.0.0 and dns enable (host) ws (the name of the win98 workstation) domain (sltl.local) and a dns server number of 10.10.1.1 I can't connect to the domain and I get a error in the servers event log stating "the master browser has received a server announcement from the coumer ws that believes that it is the master browser for the domain on transport NetBT_Tcpip_{9CB12BD2-632B-4B0A-92E7}. The master browser is stopping or and election is being forced". When I change the TCP/IP on the ws to some other ip like 198.162.0.2 and a subnet of 255.255.255.0 I can log into the domain but thats because I've got netBEUI loaded on the server and ws and I'm sure it's just not using the TCP/IP protocal and instead connecting via netBEUI.

I'ved tried setting up the DHCP on the server and I get the same results. Even odder when everything is setup how it should be I can (from the ws) ping the server by name or IP number, but the server won't ping the ws either by name our IP number.
HELP!

9 replies

by pan 13 x

try adding the computer account into active directory users and computers. add the computer name of the ws and see if that doesn't help the problem. Being is that it is win98, you may want to add a wins server to your network also. This will helpalot with name resolution. configure the win on a server if not the same server as dns and see it that doesn't fix your problem

by mark

thanks for your help, it ended up being something really stupid. It was Norton Internet Security that was being activated on boot up that was causing the problems. Of course your right I did need to setup WINS, but that went just fine

by beermonster

Adding a machine account for the 98 box will achieve nothing, as 95 \ 98 machines do not use machine accounts in NT (any flavour) - It sounds like your problem is DNS - win2k uses a whole new version of dns - Dynamic dns. your 98 machine neither uses nor understands the additional functionality of the new dns structure, which is why you are getting these problems. pre win2k machines use WINS to locate domain controllers. You need to configure WINS on the win2k server, and add this as the primary wins on both the win2k server and any clients. This way, your 98 machine is able to use WINS to locate a domain controller. The browser announcement you are seeing is not related to your comms issues, and is well documented on technet. go to www.microsoft.com/technet and do a search on your error message.

by mark

thanks for your help, it ended up being something really stupid. It was Norton Internet Security that was being activated on boot up that was causing the problems. Of course your right I did need to setup WINS, but that went just fine

by jack republic

1. you need to disable the master browser
option on win98 machine. go to tcpip properties / master browser select no
2. open regedit on the server go to hkey_localmachine/system/current controlset/
services/browser/parameters.you can see if
you server is domain master and
maintain server list
3.on the w.s do same thing

4.try instaling dhcp and configure the w.s
to obtain ip address automaticly

by mark

thanks for your help, it ended up being something really stupid. It was Norton Internet Security that was being activated on boot up that was causing the problems. Of course your right I did need to setup WINS, but that went just fine

by elmagoal

User BOSOLA was correct you NEED A WINS SERVER OR WINS INSTALL IN THE WIN2K SERVER. DO not look anywhere else that is the problem. Only w2k PC will access the server using DNS all others including NT and W9x use WINS.

by mark

thanks for your help, it ended up being something really stupid. It was Norton Internet Security that was being activated on boot up that was causing the problems. Of course your right I did need to setup WINS, but that went just fine

This discussion is closed to new replies.