Question Locked

W2K Server DNS Problem

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

Hello,

I am a property manager for a small non-profit so it has fallen into my hands to provide computer and server support. I have not messed around with a server since my days at UofT and their old sun boxes. (Newbie)

I have a new poweredge 1900 (virtually no legacy support) running W2K server SP4. The problem I am having is that the DNS seems to time out and there is intermitant access to network resources. I am unable to ping computers on the network, nslookup can not find the server, intermitant access to internet.

I have both forward and reverse lookup zones set and pointing to the server. The zones are linked to the active directory. I also have forwarding setup. Dhcp seems to be issuing ip addresses correctly.

I have tested my router and switch (try to rule out hardware problems for some of the behaviour. Does anyone have any suggestions.
Any help would be greatly appreciated.

9 replies

by p.j.hutchison

What dns address do clients pick up when they boot up? Is the DNS from the server or from the router?
Ideally, clients should pick up DNS from the server, and external dns (internet) should be forwarded to the router (see Forwarders tab in the DNS console).

by propertymanager

I checked the settings from one of the clients on the network and it came back as

Windows IP Configuration
HostName: MNOF0002
Primary DNS: company.local
Node Type: Unknown
IP Routing: No
Wins Proxy Enabled: No
DNS Suffix Search: company.local
company.local

Ethernet Adapter local Area Connection
Connection-Specific DNS Suffix: company.local
Description: Broadcom Netxtreme 57xx Gigabit
Physical Address: xx xx xx xx xx
Dhcp Enabled: Yes
Autoconfig Enabled: Yes
Ip Address:192.168.2.107
Subnet mask: 255.255.255.0
Default Gateway: 192.168.2.1
DHCP:192.168.2.50
DNS:192.168.2.50

The DHCP and DNS ips coorespond to the server

The connections seems to time out and the computer has to re-establish the connection
to the server.
I can now ping across the network. The clients were run xp with the firewall activated.

The server is running Trend Micro SMB Server protect.

by cg it

any time a host times out when trying to contact a DNS server, the most common problem is that the clients have the wrong DNS server listed in the DNS entries for the NIC card.

The second most common problem is that a firewall is preventing the hosts from contacting the DNS server.

If your TrendMicro SMB has a firewall, create an exception for DNS traffic on the LAN to the server. Make sure hosts with firewalls also have an exception for DNS traffic.

A lessor know problem is that the NICs have power management enabled that lets the computer turn off the NIC when the comp is idle. Though normally users don't see this problem when the computer wakes up and the NIC wakes up, there can be a delay with establishing a network connection.

by propertymanager

Ok, I followed suggestions and set PTR in the reverse look up zone. NSlookup was still not behaving properly and I was still getting intermittent service on both internet and server applications.

I got installed another NIC and service improved a little. I now have two IP addresses for the server. I then went into cmos setup and adjusted the settings for the on board Broadcom Gigabit NIC. I Disabled PXE on boot.

I had everyone using the system report any problems and spoke to them several times about network performance and everyone the it was working fine and the had no service interruptions. I can not for the life of me fiqure out why this seems to have worked.

I then also disabled Remote access service because I was reaching the limit of my licenses and allowable connections.

Would anyone hazard to tell me why these changes worked. I am guessing a noisy NIC and interfaring with the DNS. From what I understand the PXE is only to look for and get information from other DHCP And DNS active on the network.

Thanks for all the help so far.

by cg it

other than creating a pointer record, none of what you mention makes sense regarding making DNS work better.

Basic DNS records in the forward lookup zone for the domain name are A records. They provide name to IP address translation. Reverse lookups are IP address to name. Reverse aren't required for DNS to operate.

A second NIC doesn't do anything for DNS. PXE is for RIS servers and deploying O/S images remotely to hosts. PXE NICs aquire a DHCP assigned IP address so that clients can contact a RIS server. NSlookup is just a query to DNS to resolve a name to address in the forward lookup zone for the domain name.

by propertymanager

Your comments gave me something to think about, so I pulled out the previous server out of storage ( poweredge 500 series). This server ran for 3 solid years with only interruptions caused by power outages and windows updates. This server was configured by an contract tech company.

I compared the setups on both servers and they were identical except for minor active directory user accounts.

I preformed nslookup tasks and received the same response as found in my intial post. (ie domain does not exist etc).

I activated RAS and received the following message when tried to navigate to the server via network places on a client. ( You may not have the authority to access the server contact your administrator. The server has reached the maximum allowed connections)

I have 40 CALs and only 26 of them being used with RAS activated.

by cg it

DNS has a built in test program you can run beside NSlookup. It's a simple and recursive query against DNS.

open up administrative tools, open DNS. right click on your server and choose properties. This will open up the dnsmgt window. In the dnsmgt window, click on the monitoring tab. check the boxes simple and recursive and click the test now radio button. results will be shown in the lower test results pane. Both should show pass[provided that you have both forward and reverse lookups.Recursive is reverse lookup query against DNS] click the interfaces tab. verify that the NIC static IP address is listed and the only the following IP addresss button is selected. click the forwarders tab. verify that your ISP DNS servers are listed as the only DNS servers listed and that under forward queries for names in the following domains, all other DNS domains is listed.

on the advanced tab, make sure that the "load zone data" is from Active Directory and registry.

next in the dnsmgt window, in the left pane, expand your server. In the forward lookup zones, you should have a zone for your domain name. click on your domain name zone in the left pane. in the right pane, a listing of all your records for your domain will be shown. you should have SOA, NS, Host [A] records as a minimum.

your SOA record should show your server name.domain name
your NS record should show your server name.domain name
your Host [A] record should show your server IP address.

note: you will probably have A records for all hosts on the network, however your only interested in your DNS server records.

double click your SOA record in the right pane. click the General tab. This should show the status of your DNS server,whether is AD intergrated and the secure only, secure and non secure or none updates. click on the name servers tab. in the reading pane, you should see your servername.domain name and IP address of the server. click zone transfers tab. This will tell you if you allow zone transfers and to which servers.

If you don't any information above for your domain e.g. in the forward lookup zone, you don't have your domain listed, you'll have to create a zone for your domain and the records needed for your domain.

finally, have to say this even though you probably already know, ... your server must have a static ip address for it's NIC.

As far as the CALs problem with RAS, first things first which is the DNS problem.

Ask a seperate forum question for RAS and CALS so that others can provide suggestions. Kept here, you might not get any suggestions.

by propertymanager

Setting up the reverse look-up and redoing the forward look-ups seems to have done the trick for the DNS time out. The Server was also set to use the router as DNS to resolve internet calls.

As for the internet, it appears to have been a power surge the took out three of my routers at once. The routers worked but would time out.

Both these issues occurred at the same time.

Thanks for all the help.

This discussion is closed to new replies.