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.