Discussion Locked

WIN2K connecting to isp for no reason

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

Hi all,

I have a 2000 server that I have running a small LAN (15 users) for file and Print.

I have just added a router to allow the users to access the internet on demand.

The network does not have it's own domain registered and the LAN uses private IP addresses. When 2000 installed I gave the server COMPANYNAME.XXX when it asked for a domain.

I added the routers address as the Gateway for the server and the isp's DNS as the server's DNS entries. Sibnce doing that I see that the server brings the router up every 3-15 minutes with the following entry

IP/UDP 192.168.1.99 -> 192.111.39.1 XXXX -> DNS

xxxx = four digit incrementing number

I get the same trigger if I do "ping www.xxx.com"

Any ideas what is causing this please?

10 replies

by jack republic

it is not clear wethere the win2k server is a stand alone server or you created a new domain.anyway win2k uses dns to fined computers and if you entered the isp dns address to the server tcpip properties than
it is trying to locate other computers .
if you are not using this server to accsses
the internet just remov the dns entry.
if it is a d.c you have to install and configure dns .

by jason burns

Sorry - yes it is a domain controller - I tried running a START -RUN - \\nt to see what happens and that brings up the line also - is there anyway of preventing this from happening - bindings?

If I do have to install DNS locally what will that dofor me? If it can't find the name in the local dns it will still bring it up.

I noticed that if I type in the name of a local PC that does exist it still brings up the line!

Can I use WINS to any effect?

Can I use wins?

by lordinfidel

The answer here is to install dns on the server.

Change your root servers in dns to point to your ISP's dns.

If you are running your domain using AD. Make sure that you configure dns for dynamic updates.

Your dhcp settings should point thedefault gw and dns to your server that is connected to the isp.

**Note- It is NOT reccomended that a DC be multihomed (ie 2 NIC's). Bring another system online for this purpose, to be your DNS, GW, and Dhcp server. DO not make it a DC.

2K uses DNS extensively, regardless of whether or not AD is installed. If however you did install AD, then DNS is already installed on your DC. It does so by default and can not operate in any other way.

WINS will just cut down on broadcasts finding names on the local lan. It is not necessary for that small of a network or if all the clients are 2k machines and you are running AD.

by lordinfidel

Several things, ANd I think this will be your solution.

If your 2000 server is acting as a Domain Controller, IE you set up Active Directory. And your DC's DNS is pointing to your external DNS. Anytime one of your clients does any type of browse function, it calls on DNS to do so. Which is why you keep dialing up.

DNS is the corner stone of AD.

My advice is one of 2 routes and will depend if you are running clients other than 2k......

First thing first though.... Running a Multihomed DC is a very bad thing.
You will need to bring another server online to do that funtion.

Running pure 2k (native mode): Bring a second 2k server on-line. Member server, not a DC. Install DNS on it. Configure DNS to accept dynamic registrations. Configure DNS's root servers to point(forward) requests to your ISP's dns.
In DHCP (or static ip's), set your DNS to the new location.

In a mixed enviroment: You can install a nt4 server or 2k server. Install both DNS and Wins on it. Follow the same instructions for above. On the clients side, in tcpip, enable (Use Wins for Lookup). This will direct all requests to the wins server and will eliminate the broadcasts which is setting off the DC to do hostname resolution.

It will try to resolve first, when it can not resolve then it will do a broadcast. Which is what you are running into now.

Good luck

by cportman

You could also set up a forwarder in DNS instead of replacing root servers.

Look in your dns console to see if you have a zone folder for the "." - if so delete it. Wait 30 seconds then right click on your server and go to properties - click on forwarders tab, then enter the DNS address for your isp. This way all local queries will not go to your ISP. Also make sure both adapters are set for your local DNS server.

Good Luck

by jason burns

Thanks for all your suggestions - but it's still not working i.e. the line keeps coming up. The router is not physically connected to the server - it is on the LAN.

Arrrrgh - come back NT4 all is forgiven!

This discussion is closed to new replies.