Hi all,

We are having a very strange prtoblem.

We cannot RDP from a Vista machine to a Vista machine. This is happening to some machines on the network. The network is flat. One subnet. Machine are all Vista either with SP1 or SP2. This is what I’ve already tried;

  • Cannot telnet to port 3389
  • Netstat -ano shows port 3389 listening
  • RDP settings still the same
  • restarted all remote services
  • • Mcafee uninstalled
    • Firewall disabled
    • HIPS uninstalled.
    • I can ping DNS name + IP works
    • NSlookup PC also works
    • Outbound RDP works fine
    • Inbound RDP does not work
    • I enabled Firewall and set the exception port to 3389, did not work
    • The Radmin tool we usually use for remote access does not work either.
    • Remote admin works for a few minutes, just before the windows completely starts
    • I checked and restarted the remote and TS services
    • When using IPSCAN, PC’s that show computer name we can access, we cannot access the ones that do not show computer name even if the IP shows alive.

Anyone have anyother suggestions?

Thanks

3 Spice ups

Silly question, but it’s always best to check the easy ones first:

Remote Desktop has been enabled, right?

1 Spice up

What level of authentication is enabled?

Remote Desktop is disabled by default in Windows 7 or Vista, but it’s easy enough to turn it back on. If you need to access your Vista PC from another box, it’s an essential thing to turn on.

Important note: Remote desktop is only included in the Professional, Business, or Ultimate versions of Windows. Home editions do not have remote desktop.

To get to the configuration page, you can either right-click the Computer icon and choose properties, or you can type in system into the start menu search box, and then find the entry for System.

Click the “Remote Settings” link on the left hand side

Now you can finally turn it on (see attached image)

To connect from another Vista / Win7 PC on the same network, click the bottom radio button. If you need to connect from an XP/2k machine, click the “Allow connections from computers running any version of Remote Desktop” radio button.

Don’t worry about setting up firewall rules, Vista or Windows 7 does that for you automatically.

Note: This should work for both Windows 7 and Vista.

1 Spice up

It sounds to me as if your TCP/IP listening port has been changed from the default. Check your registry and see if the port has been changed.

Open your registry editor and look here:

HKEY_LOCAL_MACHINE / SYSTEM / CurrentControlSet / Control / Terminal Server / WinStations / RDP-Tcp

Locate the DWORD named “PortNumber”.

Open this DWORD, change the value from Hexadecimal to Decimal and see what the listening port is set to.

Safe mode or go to msconfig and disable all unnecessary stuff until you find the culprit

Yes :slight_smile:

Ask anything you can think of this always help

MickeyHr wrote:

Safe mode or go to msconfig and disable all unnecessary stuff until you find the culprit

Tried this only enabeling Remote services. Did not help

Big Sarge wrote:

It sounds to me as if your TCP/IP listening port has been changed from the default. Check your registry and see if the port has been changed.

Open your registry editor and look here:

HKEY_LOCAL_MACHINE / SYSTEM / CurrentControlSet / Control / Terminal Server / WinStations / RDP-Tcp

Locate the DWORD named “PortNumber”.

Open this DWORD, change the value from Hexadecimal to Decimal and see what the listening port is set to.

Nope, not it.

Port number is still 3389.

Good suggestion, did not think of this one

Alan Cross wrote:

What level of authentication is enabled?

Second choice

Less secure

You said some of your machines don’t work so I assume that most of them you can RDP to. So it would seem that there is some common with ones that don’t work and that is the key to the issue. Do the event logs of each machine involved show anything at the time of failure?

As a side question why all the RDP?

Try running the “un-official” Mcafee removal tool since it can still leave traces that could cause issues;

Hey Deborah,

Even with firewall off. Did you check to if rdp inbound rules in advance settings of Windows Firewall. See Attachment.

What version of Vista are you on? only business and Ultimate version support RDP as I remember it on top of my head.

Josh_Cunning wrote:

You said some of your machines don’t work so I assume that most of them you can RDP to. So it would seem that there is some common with ones that don’t work and that is the key to the issue. Do the event logs of each machine involved show anything at the time of failure?

As a side question why all the RDP?

We have 2 offices, one we give remote support to with either RDP or RAdmin. None of these 2 apps works anymore. That is why this urgent, else we have to hop in a plane. That is not doable everytimes we need to give support.

Not all PC’s have this issue. We thought this happened after SP2 updates, but some SP1 also show same issue.

Mike8990 wrote:

What version of Vista are you on? only business and Ultimate version support RDP as I remember it on top of my head.

Enterprise, RPD works in this version

JoshWheeler wrote:

Try running the “un-official” Mcafee removal tool since it can still leave traces that could cause issues;

Download McAfee Removal Tool (mcpr)

We are running Mcafee Enterprise Workstation, with ePO v4.5 and HIPS.

All this has been uninstalled from the laptop for testing

Can you view the remote computer event logs? If so does it show up at all the failure to connect or maybe you see if some other things are failing.

Another thought is it possible one computer vs. another hasn’t be restarted in a long time so that maybe some OS or policy is change is only effecting some of them.

Also I would find out if someone maybe plugged in a hub or switch at the site. Something had to change to break it right?

try this from cmd:

netsh winsock reset

I want to thank all of you for all the suggestions.

The problem is resolved. The issue was the Mcafee. Seems even if you uninstall it somethings keep running in the background. What we did to make sure it was the Mcafee causing this was follow the instructions to manually remove Macfee from the machine and the RDP worked OOnce we determined that it was Mcafee, we went in ePO and disabled two rules and reapplied the policy to all machines.

The weird thing that thru us off was we have ePO running but not all machines were affected, and the ePO policy is the same configuration that we have in another remote site. Further the ePo was not modified. Now we are going to check those 2 rules what’s in them.

Thanks again