brooke82
asked on
Terminal services has stopped working
Hi All
I am currently having issues with terminal services. I had installed Windows 2003 SP1 and etrust antivirus v8. Now i am unable to term in. I keep getting the below error:
The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be to busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connecting later.
i orgianally thought that it was a router problem, so i applied the latest firmware and opened the apporiate ports but it is still not working. So i uninstalled and reinstalled terminal services, removed SP1, reinstalled licensing server (even though i believe temporary licenses should be working as the server has only been running for the last month.) I checked services and they are fine, i checked the event log but nothing stands out.
It would be great for some feedback
Thanks
I am currently having issues with terminal services. I had installed Windows 2003 SP1 and etrust antivirus v8. Now i am unable to term in. I keep getting the below error:
The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be to busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connecting later.
i orgianally thought that it was a router problem, so i applied the latest firmware and opened the apporiate ports but it is still not working. So i uninstalled and reinstalled terminal services, removed SP1, reinstalled licensing server (even though i believe temporary licenses should be working as the server has only been running for the last month.) I checked services and they are fine, i checked the event log but nothing stands out.
It would be great for some feedback
Thanks
ASKER
Hi Jay Jay70
I don't believe it's a licensing issue, terminal services was installed about 30days ago. There is no licensing issues in the event viewer.
I don't believe it's a licensing issue, terminal services was installed about 30days ago. There is no licensing issues in the event viewer.
brooke82,
do you terminal services in from a remote location or inside a LAN environment? can you give me a brief run down on how you use it at the moment just so i know where to head....
do you terminal services in from a remote location or inside a LAN environment? can you give me a brief run down on how you use it at the moment just so i know where to head....
ASKER
Hi Jay
I can use remote desktop from inside the lan, but externally it won't work.
I can use remote desktop from inside the lan, but externally it won't work.
ASKER
I could access externally until thursday morning it would not work. I could use it Wednesday night, thats when i applied SP1 and etrust anti-virus. I use the windows remote desktop connection to access terminal services.
can you check the windows firewall service isnt started since the SP1 install...
ASKER
I have removed SP1 and the firewall service is not running
if you can still use terminal services within the LAN then it is not your Server that is the issue, Terminal services doesnt care if it is an internal or external connection - all it sees is an incoming connection
if you have SP1 installed and you can still access the terminal server from internally then i think we are looking at the wrong thing, i know you said this happened the same time as the install and i agree that somehow it is tied but i cant blame the SP1 install completely.....
what VPN setup do you have do you use RRAS on a 3rd party client?
if you have SP1 installed and you can still access the terminal server from internally then i think we are looking at the wrong thing, i know you said this happened the same time as the install and i agree that somehow it is tied but i cant blame the SP1 install completely.....
what VPN setup do you have do you use RRAS on a 3rd party client?
ASKER
No i had removed SP1 thinking it was the problem, but it doesn't seem to be, as terminal services is still not working. The VPN setup i have is Windows 2003 terminal services, using RDP to access the server internally and externally.
ASKER
Could etrust be blocking it somehow?
etrust?? havent dealt with it deffinitely get rid of it for testing purposes though as well as any firewall / security solution as something is blocking RDP connections into your server.....
brooke82,
what ports do youhave forwarded also key port for rdp is 3389
what ports do youhave forwarded also key port for rdp is 3389
ASKER
Yeah i have open that port, i will unistall anti-virus now and double check secuirty settings.
also check any other firewalls / security software - zonealarm, norton.. anything you have installed to do with security...
ASKER
Ok, i have uninstalled Etrust, doubled checked that there is no firewall on, checked port settings. I can ping from the router to the server ok. And i can still not access it externally
try another test for me - under computer management and remote access - choose allow remote connections or whatever it is ( my servers are at work and im on an xp machine) see if you can connect using a basic remote desktop session rather than a terminal services session.... this may or may not require you to uninstall temporarily - at least this will tell if any rdp packets are being allowed through
ASKER
I'm thinking it must be a router problem. Also something else, does SQL run on terminal services?
http://support.microsoft.com/?id=327270
for your SQL question.....
i am also thinking its a router issue if you can connect internall then there is no windows config that will be blocking external connections..... no ISA server or anything like that installed?
for your SQL question.....
i am also thinking its a router issue if you can connect internall then there is no windows config that will be blocking external connections..... no ISA server or anything like that installed?
ASKER
yeah i have made sure that remote connections is allowed, because thats how i'm getting to the server internally i believe.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
if you get the chance - can you let me know if it was the router in the end??
cheers mate
cheers mate
ASKER
Surely will, i have just emailed Dlink, and i will phone them first thing tomorrow.
Thanks for your time, it was greatly appreciated.
Thanks for your time, it was greatly appreciated.
not a problem my friend
have a good evening :)
James
have a good evening :)
James
the temporary licences in terminal services may have expired they only last 60 days or so from memory - check your event viewer for licencing errors how long since the OS was installed
if your local polices all allow terminal services connections and the user accounts are all set to allow logins, then its licencing.
Cheers!