sherenian
asked on
Remote Desktop (RDP) only works during the day an not at night, need to fix it.
I have a network of 8 PC's and 1 Server. I can remotely connect to the Server using RDP just fine. Once on the server, I use RDP locally to connect to the 8 client PC's. I also have one of those PC's setup as a DVR with camera's connected. During the day I can RDP to this machine using the IP or Hostname just fine. But at night, I lose the ability to connect to this machine. I can connect to the network and RDP to the other 7 PC's but not to the DVR. I can ping it and get a response but nothing on RDP. I checked the PC itself, the settings, the router, everything. I can't figure out why it dies on me in the evening, then the next day, works as if nothing happened, no reboots necessary. Any ideas ? I don't need another solution like VNC, Logmein, etc. I need to make RDP work. At the moment it is almost midnight, I can ping the PC but can't RDP to it, it just says the connection timed out when I try. However, I know that if I physically walk up to the machine it will perform normally and show me the camera feeds.
Tony Giangreco
It sounds like there might be a time restriction on the DVR. Check it's settings and see if access is blocked after a certain time of day.
Check your group policy of domain users on domain controller. you have enabled logon hours restriction
ASKER
TG-TIS, it has nothing to do with the DVR time restriction because RDP should allow access all the time, the time restriction is for the DVR viewer client only based on username and shouldn't have an effect on remote access via RDP.
rizwanidrees, I have checked my group policies and no restrictions are enabled. I can connect to the other PC's just fine.
One other thing to add, this "used" to work fine...and every now and then it still does. So I don't want to call it intermittent because it isn't working most of the time, but on a random day, it will work just. This tells me that it isn't a setting or checkbox in some menu. It is a problem that requires investigating.
I have a feeling that it has something to do with the fact that all the camera motion triggers during the day are keeping the machine active but at night when no one is in the building, the lack of activity almost makes the PC go into an unresponsive state, even though its up and running and I can see the camera feeds....but then again, it wasn't working last night when I posted this and its up and running right now on a Saturday afternoon with no one in the building.
rizwanidrees, I have checked my group policies and no restrictions are enabled. I can connect to the other PC's just fine.
One other thing to add, this "used" to work fine...and every now and then it still does. So I don't want to call it intermittent because it isn't working most of the time, but on a random day, it will work just. This tells me that it isn't a setting or checkbox in some menu. It is a problem that requires investigating.
I have a feeling that it has something to do with the fact that all the camera motion triggers during the day are keeping the machine active but at night when no one is in the building, the lack of activity almost makes the PC go into an unresponsive state, even though its up and running and I can see the camera feeds....but then again, it wasn't working last night when I posted this and its up and running right now on a Saturday afternoon with no one in the building.
ASKER
I just checked on my login attempt from last night and I see an error in the Event Log, it says " Terminal Service session creation failed. It has an error code of 0x102. Its stamped 11:27pm which is when I tried to connect. So it seems we have a problem on this PC.
One possibility can be if you have restricted users to one session, Licensing Mode to Per User in Terminal Service Setting and haven't provided end session limit for idle sessions. in this case if you have created session at office and didn't disconnect your session than you will be unable to connect from different machine.
second possibility is to investigate your internet connection speed at night.
If you tell exact message you get on client side and in server log than may be i can help.
second possibility is to investigate your internet connection speed at night.
If you tell exact message you get on client side and in server log than may be i can help.
Also check Power Settings of system, if you want 24hrs availability of system than Turnoff Hard disks and stand by should be never
ASKER
rizwanidrees, its not the terminal licensing because I can make make and break connections successfully during the day but not at night. Its also not the internet connection speed because i'm making the RDP connection to the server and then trying to make the second RDP connection from inside the network. That connection successfully works to the other 7 PC's, just not the DVR machine.
I have narrowed it down to being a problem with the PC itself, either hardware or software...and the fact that it only happens at night it pointing more towards software. I double-checked all power save settings, running services, processes, and permissions. Everything is good. I may re-install service pack 3 just to see if there is any change. I am still trying to see if there is any information that may be of use relating to the Error 1036 " Terminal Service session creation failed." error code of 0x102.
I'm trying to avoid an overhaul and OS reinstall but I think i'm nearing that point.
I have narrowed it down to being a problem with the PC itself, either hardware or software...and the fact that it only happens at night it pointing more towards software. I double-checked all power save settings, running services, processes, and permissions. Everything is good. I may re-install service pack 3 just to see if there is any change. I am still trying to see if there is any information that may be of use relating to the Error 1036 " Terminal Service session creation failed." error code of 0x102.
I'm trying to avoid an overhaul and OS reinstall but I think i'm nearing that point.
Re-Install SP3 Plus also check event log of other applications (i.e. scheduled jobs, anti virus scheduled scans and other legacy software which activates at night) may be causing this problem
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.