Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Incoming Remote Desktop cannot connect using IPv4, only IPv6 - Windows 7 Pro x64

Posted on 2011-03-16
3
Medium Priority
?
3,541 Views
Last Modified: 2012-08-13
I have a Windows 7 x64 Professional PC that is set to allow incoming remote desktop connections. Until a few days ago this was working perfectly, but without warning it has started to refuse connections that are targeted at its IPv4 address - the system attempting to establish the connection just times out. The system is not set to require NLA.

Bizarrely, when using the IPv6 address, it accepts the connection and works normally.

I have verified that all the services are running, and that it is listening on port 3389 (both IPv4 and v6), and have tested without any firewall turned on - same result. Since the problem manifested, I have installed Win 7 service pack 1, which has made no difference. All other incoming IPv4 connections are accepted normally (file sharing, TFTP, etc).


Please advise the next steps I should take to troubleshoot this. Thanks in advance.
0
Comment
Question by:sam_gcaus
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 30

Accepted Solution

by:
ded9 earned 2000 total points
ID: 35163199
Do clean boot

Clean Boot Process
Click Start-msconfig-click on services tab -put a check on hide all microsoft services and then click disable add. Click on startup tab and disable all.

Restart the computer.

Now check. Post the results


Ded9
0
 

Author Closing Comment

by:sam_gcaus
ID: 35185840
This pointed me in the right direction and allowed me to pinpoint the cause of the issue.
0
 

Author Comment

by:sam_gcaus
ID: 35185856
Thanks ded9. RDP worked fine using the IPv4 address with all startup items and services disabled. It actually turned out to be our Trend Micro WFBS personal firewall. It should actually be disabled, as I use the Windows 7 built-in firewall, so the real issue is that the settings specified on the Trend server are not applying to the client properly, which I'll investigate as a seperate issue.

Thanks again!
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you get continual lockouts after changing your Active Directory password, there are several possible reasons.  Two of the most common are using other devices to access your email and stored passwords in the credential manager of windows.
OfficeMate Freezes on login or does not load after login credentials are input.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…

722 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question