G
Guest
Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Greetings,
I have a puzzling scenario here with one of my clients who uses RDP
regularly. Up until recently, everything worked like a charm. We're trying
to figure out when something went wrong. No settings have been intentionally
changed. The laptop used can connect to other RDP connections just fine.
Client uses an XP Pro laptop to connect to this XP Pro desktop. Desktop is
behind a NAT router which has been configured for port forwarding for port
3389 to the static 192.168.x.x address of the desktop. WIndows Firewall has
also been configured to allow Remote Desktop connections. Remote Desktop has
been enabled in the Properties area of My Computer and the admin-level
account (with password) is added to the Remote Desktop user list.
The desktop is on an automatic update schedule for critical updates and so
has SP2 as well as whatever other critical updates have been released since
then. There is no other firewall software installed. The only software which
was installed between the last time RDP worked and now was Norton
SystemWorks Professional 2005 and Microsoft Antispyware. This is an
exceptionally well-maintained computer, so I don't suspect any security
threats.
Here are the things I've tried so far - none of them yielded any different
result:
1. Turned off Windows Firewall
2. Placed desktop in DMZ of router
3. Released and renewed IP of cable modem, then power cycled it
4. Rebooted router
5. Uninstalled Norton SystemWorks & Microsoft AntiSpyware, rebooted
6. Used msconfig to disable all Startup items & rebooted
7. Verified IP/gateway/DNS assignment on desktop's NIC
I'm left wondering if there might have been a critical update which has
wreaked havoc with RDP. I wonder if anyone else is suddenly having
difficulty with RDP? My client estimates it's been less than a month since
it was last working right.
Many thanks for any suggestions.
Greetings,
I have a puzzling scenario here with one of my clients who uses RDP
regularly. Up until recently, everything worked like a charm. We're trying
to figure out when something went wrong. No settings have been intentionally
changed. The laptop used can connect to other RDP connections just fine.
Client uses an XP Pro laptop to connect to this XP Pro desktop. Desktop is
behind a NAT router which has been configured for port forwarding for port
3389 to the static 192.168.x.x address of the desktop. WIndows Firewall has
also been configured to allow Remote Desktop connections. Remote Desktop has
been enabled in the Properties area of My Computer and the admin-level
account (with password) is added to the Remote Desktop user list.
The desktop is on an automatic update schedule for critical updates and so
has SP2 as well as whatever other critical updates have been released since
then. There is no other firewall software installed. The only software which
was installed between the last time RDP worked and now was Norton
SystemWorks Professional 2005 and Microsoft Antispyware. This is an
exceptionally well-maintained computer, so I don't suspect any security
threats.
Here are the things I've tried so far - none of them yielded any different
result:
1. Turned off Windows Firewall
2. Placed desktop in DMZ of router
3. Released and renewed IP of cable modem, then power cycled it
4. Rebooted router
5. Uninstalled Norton SystemWorks & Microsoft AntiSpyware, rebooted
6. Used msconfig to disable all Startup items & rebooted
7. Verified IP/gateway/DNS assignment on desktop's NIC
I'm left wondering if there might have been a critical update which has
wreaked havoc with RDP. I wonder if anyone else is suddenly having
difficulty with RDP? My client estimates it's been less than a month since
it was last working right.
Many thanks for any suggestions.