VPN working, terminal services client immediately ends session

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I can get onto the server over VPN but only have acess to shared folders. When I try to get on with Terminal Services Client, it immediately ends the connection. This appears to be a licensing issue but I have only set this up today and there is a 90 day free trial period. The server end says the license is working - again, set up today. The server is using a static IP within the range available from the router, this is a workgroup as opposed to domain since there are only three computers with two more trying to connect from the outside, the VPN software is built into the router (Netgear FVS318), Windows 2000 Server is running as terminal server in application serving mode. Don't know what to do.
 
If this were a licensing problem, you'd see eventlog
entries that would indicate so. Do you see this?

Just offhand, can the client ping the terminal server and
telnet to port 3389 (telnet <ip_address> 3389)?

-M
-----Original Message-----
I can get onto the server over VPN but only have acess to
Click to expand...
shared folders. When I try to get on with Terminal
Services Client, it immediately ends the connection. This
appears to be a licensing issue but I have only set this
up today and there is a 90 day free trial period. The
server end says the license is working - again, set up
today. The server is using a static IP within the range
available from the router, this is a workgroup as opposed
to domain since there are only three computers with two
more trying to connect from the outside, the VPN software
is built into the router (Netgear FVS318), Windows 2000
Server is running as terminal server in application
serving mode. Don't know what to do.
 
I can ping the terminal server (the workstation it is set up on), but I cannot get through on the telnet. But When I ping the server, I first have to ping the lan address of the router (192.168.0.1) which launches NetScreen VPN software, which makes a conection. Then I can ping the server. This may be interfering with the telnet?
 
Yeah, it sounds like your RDP packets to port 3389 aren't
going through properly. I'm no VPN expert, but I do know
that you'll need to configure your VPNH or VPN client to
allow port 3389 packets through.

-M
-----Original Message-----
I can ping the terminal server (the workstation it is set
Click to expand...
up on), but I cannot get through on the telnet. But When I
ping the server, I first have to ping the lan address of
the router (192.168.0.1) which launches NetScreen VPN
software, which makes a conection. Then I can ping the
server. This may be interfering with the telnet?
 
Back
Top