Remote Desktop
I have a workstation running Windows 7 Ultimate 64 Bit that we cannot Remote Desktop into. I have successfully used RDP for years on various machines. I have a similar machine (running Win 7 Ultimate 32 bit) sitting next to the 64 bit and we can remote into with no problem. In fact it has only been in the last couple of months that RDP on 64 bit quit working. We get a 'Remote Desktop can't connect to the remote computer for one of these reasons:..... I know that none of the three reasons given is the problem. The setup:
RDP is configured to port 3379 on the 64 bit machine
The network firewall is setup with the needed entries
We run Symantec Endpoint on our systems which takes over the Windows firewall. I've made allow entries on this machine for port 3379 - TCP and UDP.
I have tried with Symantec disabled - no help
I have checked and rechecked everything on the machine that has to do with RDP...still get the error.
I am sure I am missing something and it may be obvious, but I just can't see it.
Any thoughts?
RDP is configured to port 3379 on the 64 bit machine
The network firewall is setup with the needed entries
We run Symantec Endpoint on our systems which takes over the Windows firewall. I've made allow entries on this machine for port 3379 - TCP and UDP.
I have tried with Symantec disabled - no help
I have checked and rechecked everything on the machine that has to do with RDP...still get the error.
I am sure I am missing something and it may be obvious, but I just can't see it.
Any thoughts?
BillBondo
Are you using 3379 intentionally? RDP uses 3389
Have you checked following
-Remote desktop service running
- Account used to RDP have been added with appropriate permissions
-Remote desktop service running
- Account used to RDP have been added with appropriate permissions
Simply test if that port you configured can be reached using
telnet vistaultimate 3379
telnet vistaultimate 3379
ASKER
I have several machines that are setup for external RDP so we have assigned alternate ports for some of those.
Yes, remote desktop service is running and accounts have appropriate permissions.
Yes, remote desktop service is running and accounts have appropriate permissions.
ASKER
Telnet fails.
Well, next step is to see if the server is listening on that port:
netstat -ano |findstr 3379
...if it were, you would be shown some output, if not: not.
If you get output, then some firewall is blocking access.
netstat -ano |findstr 3379
...if it were, you would be shown some output, if not: not.
If you get output, then some firewall is blocking access.
ASKER
I get no output with netstat -ano |findstr 3379
So make sure if your listening port is really set to 3379. Also repeat the command with 3389.
ASKER
Ok,
After a restart I was able to get on through RDP. However after a few minutes something is starting up that is blocking access.
After a restart I was able to get on through RDP. However after a few minutes something is starting up that is blocking access.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
We use SEP and it should not block RDP unless it does not know about the 3379 vs 3389 change. Can you confirm it's 3379 you are using?
ASKER
Seems that after uninstalling and reinstalling Symantec a second time I was able to connect.