Solved

Terminal Server running Windows Server 2003 requires an ipconfig /flushdns about once a week.

Posted on 2006-07-11
3
925 Views
Last Modified: 2012-08-13
I am running a Terminal Server with Microsoft Windows Server 2003.  It is in great condition except that about one time a week the server requires us to flush the DNS (or reboot).  We have anotherTerminal Server (TServ2) that does not have this problem and we have narrowed the problem to one server talled TServ1.

What happens is that TServ1 will maintain an internet connection, however about one time a week, its DNS will get jammed, and need to be flushed by going to the command prompt and typing ipconfig /flushdns .  When the DNS is jammed it cannot connect to our Exchange server, and sometimes other servers as well.  TServ1 has two network cards.

Thanks!
0
Comment
Question by:freddy9000
3 Comments
 
LVL 84

Expert Comment

by:oBdA
ID: 17084603
You probably have an external DNS server specified in the TCP/IP properties of this server. Use only your internal DNS server, and configure forwarders on this one for external name resolution.
0
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 17084726
make sure DNS is setup similar to this (same type of suggestion already made by obda)

Server DC 1
NAme:  ServerDC1
IP:  10.10.10.5
subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS1:  10.10.10.5 or 127.0.0.1  <--- must point to itself and not to ISP DNS server
DNS 2: Some other internal DNS server in the internal domain ....recommended also to be in the same site if possible

Client IP settings
Name:  Clientworkstation1
IP:  10.10.10.25
subnet: 255.255.255.0
Gateway:  10.10.10.1
DNS1:  10.10.10.5  <--- do not point to ISP ,...must point to local DNS server of the windows domain
DNS2:  some other internal Windows 2003 DNS server....but not to domain.


Why does the TSserver1 have two network cards?  do you have two networks conencted here...or do you have nic teaming enabled?
0
 
LVL 8

Accepted Solution

by:
bilbus earned 250 total points
ID: 17088080
sounds like your dns settings on the TS may be registering connection.

When it locks up, ping the TS1 address, i bet you it has changed from the one you set.

Lan card, TCPIP, advanced, DNS, uncheck register this connection.

Do it for both lan cards.

Make a entry in dns for the name of TS1. I bet that will fix it
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…

792 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question