Establishing Terminal Server session

40 pts.
Tags:
Microsoft Windows Server 2003
Terminal Server
Terminal Services
VPN
Windows 2003 Terminal Server
Dear readers, The following scenario is at hand: A client uses a Nokia 6300 to establish a connection to the Internet. Then he uses a Cisco VPN client (5.0) to establish a connection to the workplace and so far it all works fine. However on trying to establish a Terminal Server session with the Windows 2003 Terminal Server something goes horribly wrong. It looks as if there is no network traffic being generated whatsoever on the active connection. Making a connection with the Termserv works just fine when the machine is hooked up to the local LAN and other machines have no problem connecting via either the Internet or on the local network. I've already figured out that it is NOT a licensing issue, since rebooting the Terminal Server to free up the licenses has no effect at all. For making an Internet connection the N6300 is used via bluetooth and Nokia PC Suite (latest version). I hope someone has some great idea. Thanks in advance.
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

Maybe this is a firewall issue. Typically VPN clients have a different source IP address than when they are on the LAN. Check to see if there is a firewall on the client device or terminal server (or between them) blocking terminal server access by VPN clients.

Discuss This Question: 7  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Kevin Beaver
    It does sound like a firewall issue. May be worth placing a call into Nokia if you can to confirm everything's setup right.
    27,485 pointsBadges:
    report
  • Queryous
    Thanks to both Labnuke99 and KevinBeaver, I will look further into the firewall issue. I believe the client machine is running AVG, so this could be the problem, though in my experience AVG pops up to warn you about such activities and asking whether you want to allow or denie such actions. I'll look into it in more detail and let you know what I find. Thanks so far anyway.
    40 pointsBadges:
    report
  • Queryous
    To everyone still tuned in to this question, I have ruled out that a firewall is the issue. As it turns out the session times out when trying to connect. Incidentally, I was able to initiate a terminal session when the machine was connected directly to the network and not working via an Internet connection using the mobile phone. The user is also unable to connect when using the DSL connection from home (using the same computer). But since it does work when directly plugged into the network, I think I can rule out any firewall issues, since neither the phone nor the DSL modem incorporates any (I've checked this). Rather it seems, upon trying to connect, there is no network traffic at all (little screens near the clock in system tray don't blink). This would explain the timeout, but how can I tell the terminal server client to use a specific connection, or maybe even try all of them, or at least the active one? Hope someone has some good ideas.
    40 pointsBadges:
    report
  • Kevin Beaver
    Thanks for the update. This is interesting...Did you find out anything else regarding any personal firewall on the server? It sounds like you need to connect a network analyzer between the firewall and the server to see specific details (the blinking lights may not be telling the entire story).
    27,485 pointsBadges:
    report
  • CRagsdale32
    Curios if possibly the time to terminate (may be called something else to others) is set wrong. IE: when client connects, the network connection thinks it's already timed out and denies access almost immediately. Making it appear there is no connection. Or did I miss some of the discussion where the client can actually log onto the network and there is no traffic? But if you can actually log on, there would be traffic since there would have to be a handshake to establish the user verification.
    755 pointsBadges:
    report
  • Troy Tate
    Could also be a potential routing issue. The client may not know how to get to the terminal server once the VPN session is established. You will need to use something like Wireshark or Microsoft Network Monitor to capture packets at both ends to see if there is any traffic and/or if the connection is built and then torn down.
    0 pointsBadges:
    report
  • mshen
    Check the Access Lists on your Cisco VPN. If the user can't connect remotely using a DLS connection, thats the first place to check.
    27,385 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: