Remote Desktop through PPTP

V

vagabond

Hi all

I am having trouble connecting to client's SBS server using Terminal Services over VPN from an XP pro box.

I'm pretty sure that this used to work from the XP box. I can successfully establish a VPN session to their network, ping their machines by IP or NetBIOS name, browse shares / admin shares, connect to the remote server's event viewer/compmgmt/etc snapins but I cannot connect directly to the server by RDP.

I can connect from any of my W2K servers, though.

When accessing those services that I am able to there is plenty of activity / bytes sent & received over the vpn session but when I use RDP the activity is over the LAN connection only.

The only thing that has changed recently is the install of Virtual PC (which adds a protocol to the LAN connection) but disabling this doesn't help.

I had also installed the updated RDP client but it makes no odds whether I use the mstsc.exe in program files (new) or system32 (original).

In fact, I've just tested this to other clients' servers, all over VPN, and the results are the same.

RDP to clients directly (where 3389 is forwarded) works fine, as do RDP sessions locally.

Any ideas...? It's not desperate but I'd like to get to the bottom of this.

Thanks

john
 
V

vagabond

Copied and pasted:

---------------------------
Remote Desktop Disconnected
---------------------------
The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to accept new connections.
It is also possible that network problems are preventing your connection.

Please try connecting again later. If the problem continues to occur, contact your administrator.
---------------------------
OK Help
---------------------------

Sorry - I should have included this originally. The problem appears to be a routing issue, however the routing tables, after connecting by vpn, are the same on XP and W2K. Just that XP doesn't send a single byte over the vpn link when running teh RDP client. Makes no difference whether I use hostname, IP or full domain name.


john
 
J

Jeffrey Randow (MVP)

How many routes are made to the remote network? If you are getting no
traffic over the VPN link when trying to access a resource that is on
the remote network, then it definately is a routing problem..

One point to consider, though - are the two networks (your network and
the remote network) on the same IP address space (i.e., 192.168.1.x)?
If so, this is probably the cause of your problem...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
V

vagabond

Hi

Remote network is 192.168.0.0/24 and I'm 192.168.200.0/24.

It's definitely this mschine - an XP laptop connects without a hitch.

All traffic except RDP travels over the VPN link.

Routing table is:

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.110 192.168.0.110 1
0.0.0.0 0.0.0.0 192.168.200.1 192.168.200.50 21
xx.xx.18.58 255.255.255.255 192.168.200.1 192.168.200.50 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.110 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.0.255 255.255.255.255 192.168.0.110 192.168.0.110 50
192.168.200.0 255.255.255.0 192.168.200.50 192.168.200.50 20
192.168.200.50 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.200.255 255.255.255.255 192.168.200.50 192.168.200.50 20
224.0.0.0 240.0.0.0 192.168.200.50 192.168.200.50 20
224.0.0.0 240.0.0.0 192.168.0.110 192.168.0.110 1
255.255.255.255 255.255.255.255 192.168.200.50 192.168.200.50 1
Default Gateway: 192.168.0.110
===========================================================================
Persistent Routes:
None

Ping by host name works:

Pinging bfpw2k [192.168.0.30] with 32 bytes of data:

Reply from 192.168.0.30: bytes=32 time=63ms TTL=128
Reply from 192.168.0.30: bytes=32 time=66ms TTL=128
Reply from 192.168.0.30: bytes=32 time=71ms TTL=128
Reply from 192.168.0.30: bytes=32 time=63ms TTL=128

Just RDP which bombs.

Thanks

john
 
J

Jeffrey Randow (MVP)

What happens if you run "telnet bfpw2k 3389" from a command prompt?

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

Hi

Remote network is 192.168.0.0/24 and I'm 192.168.200.0/24.

It's definitely this mschine - an XP laptop connects without a hitch.

All traffic except RDP travels over the VPN link.

Routing table is:

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.110 192.168.0.110 1
0.0.0.0 0.0.0.0 192.168.200.1 192.168.200.50 21
xx.xx.18.58 255.255.255.255 192.168.200.1 192.168.200.50 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.110 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.0.255 255.255.255.255 192.168.0.110 192.168.0.110 50
192.168.200.0 255.255.255.0 192.168.200.50 192.168.200.50 20
192.168.200.50 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.200.255 255.255.255.255 192.168.200.50 192.168.200.50 20
224.0.0.0 240.0.0.0 192.168.200.50 192.168.200.50 20
224.0.0.0 240.0.0.0 192.168.0.110 192.168.0.110 1
255.255.255.255 255.255.255.255 192.168.200.50 192.168.200.50 1
Default Gateway: 192.168.0.110
===========================================================================
Persistent Routes:
None

Ping by host name works:

Pinging bfpw2k [192.168.0.30] with 32 bytes of data:

Reply from 192.168.0.30: bytes=32 time=63ms TTL=128
Reply from 192.168.0.30: bytes=32 time=66ms TTL=128
Reply from 192.168.0.30: bytes=32 time=71ms TTL=128
Reply from 192.168.0.30: bytes=32 time=63ms TTL=128

Just RDP which bombs.

Thanks

john


Jeffrey Randow (MVP) said:
How many routes are made to the remote network? If you are getting no
traffic over the VPN link when trying to access a resource that is on
the remote network, then it definately is a routing problem..

One point to consider, though - are the two networks (your network and
the remote network) on the same IP address space (i.e., 192.168.1.x)?
If so, this is probably the cause of your problem...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
Click to expand...
Click to expand...
 
V

vagabond

Nothing - just hangs for a while with "connecting to bfpw2k..."

john

Jeffrey Randow (MVP) said:
What happens if you run "telnet bfpw2k 3389" from a command prompt?

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

Hi

Remote network is 192.168.0.0/24 and I'm 192.168.200.0/24.

It's definitely this mschine - an XP laptop connects without a hitch.

All traffic except RDP travels over the VPN link.

Routing table is:

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.110 192.168.0.110 1
0.0.0.0 0.0.0.0 192.168.200.1 192.168.200.50 21
xx.xx.18.58 255.255.255.255 192.168.200.1 192.168.200.50 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.110 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.0.255 255.255.255.255 192.168.0.110 192.168.0.110 50
192.168.200.0 255.255.255.0 192.168.200.50 192.168.200.50 20
192.168.200.50 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.200.255 255.255.255.255 192.168.200.50 192.168.200.50 20
224.0.0.0 240.0.0.0 192.168.200.50 192.168.200.50 20
224.0.0.0 240.0.0.0 192.168.0.110 192.168.0.110 1
255.255.255.255 255.255.255.255 192.168.200.50 192.168.200.50 1
Default Gateway: 192.168.0.110
===========================================================================
Persistent Routes:
None

Ping by host name works:

Pinging bfpw2k [192.168.0.30] with 32 bytes of data:

Reply from 192.168.0.30: bytes=32 time=63ms TTL=128
Reply from 192.168.0.30: bytes=32 time=66ms TTL=128
Reply from 192.168.0.30: bytes=32 time=71ms TTL=128
Reply from 192.168.0.30: bytes=32 time=63ms TTL=128

Just RDP which bombs.

Thanks

john


How many routes are made to the remote network? If you are getting no
traffic over the VPN link when trying to access a resource that is on
the remote network, then it definately is a routing problem..

One point to consider, though - are the two networks (your network and
the remote network) on the same IP address space (i.e., 192.168.1.x)?
If so, this is probably the cause of your problem...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

Copied and pasted:

---------------------------
Remote Desktop Disconnected
---------------------------
The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to accept new connections.
It is also possible that network problems are preventing your connection.

Please try connecting again later. If the problem continues to occur, contact your administrator.
Click to expand...
Click to expand...
Click to expand...
to be a routing issue, however the routing tables, after connecting by vpn,
are the same on XP and W2K. Just that XP doesn't send a single byte over
the vpn link when running teh RDP client. Makes no difference whether I use
hostname, IP or full domain name.successfully establish a VPN session to their network, ping their machines
by IP or NetBIOS name, browse shares / admin shares, connect to the remote
server's event viewer/compmgmt/etc snapins but I cannot connect directly to
the server by RDP.activity / bytes sent & received over the vpn session but when I use RDP the
activity is over the LAN connection only.PC (which adds a protocol to the LAN connection) but disabling this doesn't
help.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

RDP Win7, what files are stored locally? 3
remote to desktop not working- 2
Remote desktop hangs intermittently over VPN connection 1
Remote Desktop not working 3
Remote Desktop over VPN Not Working 8
Dialup inside a Remote Desktop Session 1
Remote desktop within a VPN 3
Losing connection with VPN Cisco client 5

Top