zpitzy
asked on
Remote Desktop stopped working
Hi
Yesterday remote desktop was working but to day it has stopped, we ahd a power failure thsi morning and both servers shut down unexpectedly.
The RDP problem was discovered as I could nto RDP from home throguh the router.
To elimante router problems I tried to rdp internally within the office.
I have a Windows 2003R2 server with SP1.
I alos have a second windows 2003 R2 server with excahnge 2007 on and now i cant remote desktop to either typing their IP addresses yet I can ping them. Email/excahnge is working and webmail is still working (port 80 and 443 redirects by the router) domain name office.domain.com so the external domain is OK.
I have been searching the internet but cannot find any thing relevant or toher than the basic steps check Ip address etc.
I think it may be a red herring as the problem existed before but I also get a WMi error .. needed to close on the main server, but this has been here before.
There does not appear to be anythign in the evnet log that is relevant.
The terminal server service is running.
Any extra pointers or a solutionw oudl help.
Thanks
Kevin
Yesterday remote desktop was working but to day it has stopped, we ahd a power failure thsi morning and both servers shut down unexpectedly.
The RDP problem was discovered as I could nto RDP from home throguh the router.
To elimante router problems I tried to rdp internally within the office.
I have a Windows 2003R2 server with SP1.
I alos have a second windows 2003 R2 server with excahnge 2007 on and now i cant remote desktop to either typing their IP addresses yet I can ping them. Email/excahnge is working and webmail is still working (port 80 and 443 redirects by the router) domain name office.domain.com so the external domain is OK.
I have been searching the internet but cannot find any thing relevant or toher than the basic steps check Ip address etc.
I think it may be a red herring as the problem existed before but I also get a WMi error .. needed to close on the main server, but this has been here before.
There does not appear to be anythign in the evnet log that is relevant.
The terminal server service is running.
Any extra pointers or a solutionw oudl help.
Thanks
Kevin
ASKER
Hi
Thanks, I will run chkdsk /r tongith.
I am trying both internally and externally.
I tried a second server and RDP is nto workign on thsi either, but evyerhting else on the network works, printing, internet etc. Even logmein is working on all machines.
All services are running that are started automatically as ewll as a few tha are manual. including Terminal Services.
there is nothing in the event log that wasnt happening before and the WMI errror ahs been happening snce 2008. EXCEPT a new error on the second reboot today not the one after the power failure and that is Fault Bucket "1232332732". I canfind no help with this.
What seems strange is that neitehr server can now allow RDP, so I woudl guess either there is a corruption in AD which has repalcieted as they are both domain controllers or a strange problem on the network.
Any more suggestions woudl help
Thanks
Kevin
Thanks, I will run chkdsk /r tongith.
I am trying both internally and externally.
I tried a second server and RDP is nto workign on thsi either, but evyerhting else on the network works, printing, internet etc. Even logmein is working on all machines.
All services are running that are started automatically as ewll as a few tha are manual. including Terminal Services.
there is nothing in the event log that wasnt happening before and the WMI errror ahs been happening snce 2008. EXCEPT a new error on the second reboot today not the one after the power failure and that is Fault Bucket "1232332732". I canfind no help with this.
What seems strange is that neitehr server can now allow RDP, so I woudl guess either there is a corruption in AD which has repalcieted as they are both domain controllers or a strange problem on the network.
Any more suggestions woudl help
Thanks
Kevin
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well - it is finally fixed.
I have no idea how or what changed.
I think changing the RDP port was the solution, so maybe it was corrupted in the registry and by changin it it rset the port number.
Thank you for your help and suggestions
I have no idea how or what changed.
I think changing the RDP port was the solution, so maybe it was corrupted in the registry and by changin it it rset the port number.
Thank you for your help and suggestions
ASKER
Not hte fix (I dont think) there was nothing in the logs and I had checekd these but at least someone tried to help.
Thank you
Thank you
If it didn't work from inside your Office either, then check that the services have started on the server, and if not try starting them. If they don't start, check the error-message you get when trying to start them. Also check the server's Eventlog for problems.
Run a chkdsk /r on all drive letters of your servers (depending on the disk-sizes this can take a long time, and it will do that while the server is booting and before it gets available, so make sure you do that during times when the server isn't being used). Power-failures can corrupt file-systems, and this will repair those corruptions.