Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.
Course Of The Month
8 days, 22 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Terminal Server running Windows Server 2003 requires an ipconfig /flushdns about once a week.
Posted on 2006-07-11
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!
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!
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3 Comments
Active today
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.
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?
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?
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
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
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
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,…
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special.
It's completely agentless, but does let you create an agent, if you desire.
It offers powerful scalability …
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month8 days, 22 hours left to enroll
617 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.