Networking Forums

Networking Forums > Computer Networking > Windows Networking > vpn connection ok but cant find terminal server ?

Reply
Thread Tools Display Modes

vpn connection ok but cant find terminal server ?

 
 
scott
Guest
Posts: n/a

 
      03-21-2006, 04:00 PM
Hi,

I have a remote user connecting to LAN using PPTP from WinXP home.
Connection established ok and they are allocated an IP on my subnet. Server
hosting RAS is 2003 standard.

User then launches remote desktop over 3389 to connect to terminal server
using IP address but can never find host (server too busy or not found type
error etc ... )

my testing:
- as suggested above user is allocated correct IP and is connected ok (i can
see in RAS)
- user's "default gateway on remote network ticked" on pptp adapter
- user cannot ping terminal server ip once conneted over pptp
- user cannot "telnet ip 3389" (normally get listening port)
- user cannot ping / telnet on 3389 on any terminal servers on LAN
- deleted MSlicencing key in registry but its not that
- i can connect using users credentials to pptp and terminal server
internally
- externally i can connect no problem as well (from an adsl connection to my
hosting server)
- windows firewall (sp2) disabled on users machine

I dont know what else to test, works fine me me using users settings from
external source. It like something else is blocking but PPTP works fine.

Any ideas ?

Thanks for your time.
Scott


 
Reply With Quote
 
 
 
 
Robert L [MS-MVP]
Guest
Posts: n/a

 
      03-21-2006, 04:41 PM
Can't ping TS by IP that is the problem. Have you enable IP routing on the RRAS? Is the RRAS multihomed computer? Or use tracert command to see where the traffic go.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"scott" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Hi,

I have a remote user connecting to LAN using PPTP from WinXP home.
Connection established ok and they are allocated an IP on my subnet. Server
hosting RAS is 2003 standard.

User then launches remote desktop over 3389 to connect to terminal server
using IP address but can never find host (server too busy or not found type
error etc ... )

my testing:
- as suggested above user is allocated correct IP and is connected ok (i can
see in RAS)
- user's "default gateway on remote network ticked" on pptp adapter
- user cannot ping terminal server ip once conneted over pptp
- user cannot "telnet ip 3389" (normally get listening port)
- user cannot ping / telnet on 3389 on any terminal servers on LAN
- deleted MSlicencing key in registry but its not that
- i can connect using users credentials to pptp and terminal server
internally
- externally i can connect no problem as well (from an adsl connection to my
hosting server)
- windows firewall (sp2) disabled on users machine

I dont know what else to test, works fine me me using users settings from
external source. It like something else is blocking but PPTP works fine.

Any ideas ?

Thanks for your time.
Scott


 
Reply With Quote
 
scott
Guest
Posts: n/a

 
      03-22-2006, 08:50 AM
Thanks for reply

"Can't ping TS by IP that is the problem. Have you enable IP routing on the RRAS? "

IP routing is enabled. This system work fine for this problem user a few weeks ago. Works fine for myself and other users to date. Works fine when i use problematic users login credentials. Just appears to be be from 1 users machine.

"Is the RRAS multihomed computer? Or use tracert command to see where the traffic go."

RRAS host is not at a multihomed computer. I have not trid tracert yet (will give it a go asap).

I get the feeling that this is a problem with users machine, but dont know what.

Thanks for your time
Scott


"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Can't ping TS by IP that is the problem. Have you enable IP routing on the RRAS? Is the RRAS multihomed computer? Or use tracert command to see where the traffic go.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"scott" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Hi,

I have a remote user connecting to LAN using PPTP from WinXP home.
Connection established ok and they are allocated an IP on my subnet. Server
hosting RAS is 2003 standard.

User then launches remote desktop over 3389 to connect to terminal server
using IP address but can never find host (server too busy or not found type
error etc ... )

my testing:
- as suggested above user is allocated correct IP and is connected ok (i can
see in RAS)
- user's "default gateway on remote network ticked" on pptp adapter
- user cannot ping terminal server ip once conneted over pptp
- user cannot "telnet ip 3389" (normally get listening port)
- user cannot ping / telnet on 3389 on any terminal servers on LAN
- deleted MSlicencing key in registry but its not that
- i can connect using users credentials to pptp and terminal server
internally
- externally i can connect no problem as well (from an adsl connection to my
hosting server)
- windows firewall (sp2) disabled on users machine

I dont know what else to test, works fine me me using users settings from
external source. It like something else is blocking but PPTP works fine.

Any ideas ?

Thanks for your time.
Scott


 
Reply With Quote
 
scott
Guest
Posts: n/a

 
      03-24-2006, 04:24 PM
its a miracle ... "it sorted itself" exclaimed my user sheepishly.

sorry to have bothered you

scott
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows 2003/ terminal server: only RDP connection are not possibl Martin Schweizer Windows Networking 4 10-18-2008 02:01 PM
Cant find server although internet connection ok Jack D Wireless Networks 5 12-12-2007 05:00 AM
Slow connection to Terminal Server Pierrot Robert Windows Networking 3 11-02-2005 02:39 AM
Desktop Connection to Terminal Server 2000 antonio Windows Networking 1 09-05-2004 11:29 PM
Terminal server web connection (2003) Med Windows Networking 3 02-16-2004 03:20 PM



1 2 3 4 5 6 7 8 9 10 11