Windows 2003 R2 server hangs
We have windows 2003 R2 server which hangs for few minutes whenever we try to access remote Console using "mstsc /admin". All terminal connections stop responding during that time. After few minutes, all terminal connections including remote
consol works fine.
Checked few existing topics but they are not much helpful.
Thanks in advance for any help
Venkatesh R
September 22nd, 2012 7:10am
Hello,
sorry but this is too less information.
What about event viewer errors and messages when doing the connection attempt?
Are the machines on the same subnet? Please post an unedited ipconfig /all from the problem server and the machine where you try it from.
"All terminal connections stop responding " Is that a Terminal server and other users are logged on and not able to work or what does this mean? Are the lastest SP and all updates installed?
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2012 10:06am
Hi Meinolf,
No errors displayed or logged in event logs.
Yes, all machines are on same subnet. Trying to access remote console from an RDP connection to the same server. Same was working fine so far and this problem is only for past week or so
C:\>ipconfig /allWindows IP Configuration Host Name . . . . . . . . . . . . : chennai-ts1
Primary Dns Suffix . . . . . . . : jeenaco.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : jeenaco.comEthernet adapter Local LAN: Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC382i DP Multifunction Gigabit Server
Adapter #3
Physical Address. . . . . . . . . : 78-E7-D1-E8-F2-18
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.15.71
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.15.243
DNS Servers . . . . . . . . . . . : 192.168.103.7
---- PDC
192.168.103.6 ----
Backup DC
192.168.15.71C:\>
Yes, This server is Local Domain controller and Terminal Server. No response for all users on thier terminal screens for few minutes.
All patches till Sep. 11, 2012 are updated in the server
Venkatesh R.
September 24th, 2012 1:16am
First of all, installing TS role on Domain Controllers is NOT a good practice. You might need to consider the moving the TS role to a member server.
http://technet.microsoft.com/en-us/library/cc742817(v=ws.10).aspx
IP config of the server in question looks OK except 3 IPs in DNS servers.
As you have mentioned this is a domain controller, you might want to use its own IP as primary DNS and rest as secondary and tertiary. In fact, 3 DNS IP is not needed.
Also, check following:
Make sure to configure this server as GC if it is not configured already.
Disable AV services temporarily and check if RDC works without any issues. Sometimes, AV might block incoming connections.
If Windows firewall service is enabled, make sure to exclude RDP port.
Make sure server time is in sync with DC which holds PDC emulator role.Regards, Santosh
I do not represent the organisation I work for, all the opinions expressed here are my own.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
September 24th, 2012 2:20am
First of all, installing TS role on Domain Controllers is NOT a good practice. You might need to consider the moving the TS role to a member server.
http://technet.microsoft.com/en-us/library/cc742817(v=ws.10).aspx
IP config of the server in question looks OK except 3 IPs in DNS servers.
As you have mentioned this is a domain controller, you might want to use its own IP as primary DNS and rest as secondary and tertiary. In fact, 3 DNS IP is not needed.
Also, check following:
Make sure to configure this server as GC if it is not configured already.
Disable AV services temporarily and check if RDC works without any issues. Sometimes, AV might block incoming connections.
If Windows firewall service is enabled, make sure to exclude RDP port.
Make sure server time is in sync with DC which holds PDC emulator role.Regards, Santosh
I do not represent the organisation I work for, all the opinions expressed here are my own.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
September 24th, 2012 2:23am
Thanks Santosh
Planning to deploy separate server for DC and remove DC from this server... Shall check other points you have suggested after removing DC role from this server..
Venkatesh R.
Free Windows Admin Tool Kit Click here and download it now
September 26th, 2012 5:23am
Sounds good Venkatesh :)Regards, Santosh
I do not represent the organisation I work for, all the opinions expressed here are my own.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
September 26th, 2012 5:37am


