Server 2008 R2 Standard

[BAZZA]

Good morning to all.
I am very new to this, so please excuse me if I am in the wrong thread.
I have recently had server 2008 standard r2 installed on a dedicated machine.
I have 5 cals & 3 tsl and everything works fine execpt every morning I have to reboot
the server because nobody can connect through remote desktop. The actual server does not hang, so I gather it has to be a
connectivity problem with terminal services.Once I have rebooted it is fine
for the whole day but sometime between midnight and 8 am something happens to stop rdt from connecting.
I have done the basics such as turning off the firewall and setting all the options in power solutions
to NEVER...but to no avail.
Can anyone suggest something that I could try?
thanks
\Barry

 

[mmthomas]

What message do users get when they try to connect?

When users cannot connect, what is the RAM utilization on the server?

Are users logging off at the end of the day (as opposed to just disconnecting) so that all of the licenses are not seen as in use at the start of the next?

 

[BAZZA]

What message do users get when they try to connect?

When users cannot connect, what is the RAM utilization on the server?

Are users logging off at the end of the day (as opposed to just disconnecting) so that all of the licenses are not seen as in use at the start of the next?

 

[BAZZA]

Hi Matt
thanks for answering.
1) no ram utilization as it is a dedicated server only for rdt and this happens first think in the morning.
2) message is something like " no connection to the server is available at present"
3) everyone is logging off.

rgds

Barry

 

[mmthomas]

When users can't connect, if you reset the RDP-tcp connection rather than restart the server does that fix the problem? (Terminal Services Configuration > click the RDP-tcp connection, chose Disable Connection, OK and then re-enable the connection) If it does, the connection properties may be corrupted. You can Delete the connection in the same tool and Create New Connection to replace it.

 

[BAZZA]

Hi
no it happens to all remote machines. The reboot is the only option.
It happened again last night, at around 11pm when no machines were active.
All machines had logged off, but connection was not available until
the reboot.
see attachment

regardsView attachment 44

 

[mmthomas]

Ok, just in case it wasn't understood, I meant the master RDP-tcp connection -- so that would affect all connection ability from all remote machines. It's the connection that all RDP sessions connect to on the server, not an individual remote session.

This screen shot may look different from yours because I have deleted and renamed it:View attachment 45

 

[BAZZA]

hi
thanks again for the help. Unfortunately, I am a complete novice when it comes to servers, so please bear with me.. What I have done is gone into the server and taken the sceen shots attached that I think may bear some relevance to the problem. Everything works fine except for this problem whereby no remotes can connect until after the re-boot. Then it is ok for a few hours and then when the server has been inactive for a while, the problem starts again. As I type this now ( Sunday morning 11:47am ) I cannot log-on... strange
anyhow, I hope the attachments are helpful. there is a 2nd post to this message with one other attachment

regard

Barry

 

[BAZZA]

hi seems the systen will not allow me to upload anymore attachments for the moment.


rgds