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?
John WilsonVP of Administration, Safety, & HRAsked:
Who is Participating?
 
McKnifeConnect With a Mentor Commented:
Uninstall Symantec Endpoint and restart.
0
 
BillBondoCommented:
Are you using 3379 intentionally? RDP uses 3389
0
 
Yagya ShreeCommented:
Have you checked following

-Remote desktop service running
- Account used to RDP have been added with appropriate permissions
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

 
McKnifeCommented:
Simply test if that port you configured can be reached using
telnet vistaultimate 3379
0
 
John WilsonVP of Administration, Safety, & HRAuthor Commented:
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.
0
 
John WilsonVP of Administration, Safety, & HRAuthor Commented:
Telnet fails.
0
 
McKnifeCommented:
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.
0
 
John WilsonVP of Administration, Safety, & HRAuthor Commented:
I get no output with netstat -ano |findstr 3379
0
 
McKnifeCommented:
So make sure if your listening port is really set to 3379. Also repeat the command with 3389.
0
 
John WilsonVP of Administration, Safety, & HRAuthor Commented:
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.
0
 
Tony GiangrecoCommented:
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?
0
 
John WilsonVP of Administration, Safety, & HRAuthor Commented:
Seems that after uninstalling and reinstalling Symantec a second time I was able to connect.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.