Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. VPN Trouble

VPN Trouble

Scheduled Pinned Locked Moved IT & Infrastructure
sysadminquestion
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    Paul Unsworth
    wrote on last edited by
    #1

    Hey there everyone. Does anyone know much about VPN with Windows 2k3? I set up my server as a VPN server. Set up the users and granted them remote access etc. I have tested the connection from within my own network which works fine. I was under the impression that once a VPN connection is established, all network traffic to and from the client maching is forced through said connection unless a split connection is established, which is not, and all worked fine. I then got somebody outside the network to connect, they were authenticated ok etc, they still had internet access, however, they could not actually see any machines on my network. Not even the VPN server that they were connected too... I've tinkered with the settings on the server trying to get this to work, but I feel it may be client side, but I do not have access to the client machine. Summary: Clients can log onto the network via VPN, they get assigned an IP, but cannot see or be seen by any machines on the network. Does anyone know what could be causing this? It's rather annoying me. Thank you guys. :-D

    oooo, the Jedi's will feel this one....

    E 1 Reply Last reply
    0
    • P Paul Unsworth

      Hey there everyone. Does anyone know much about VPN with Windows 2k3? I set up my server as a VPN server. Set up the users and granted them remote access etc. I have tested the connection from within my own network which works fine. I was under the impression that once a VPN connection is established, all network traffic to and from the client maching is forced through said connection unless a split connection is established, which is not, and all worked fine. I then got somebody outside the network to connect, they were authenticated ok etc, they still had internet access, however, they could not actually see any machines on my network. Not even the VPN server that they were connected too... I've tinkered with the settings on the server trying to get this to work, but I feel it may be client side, but I do not have access to the client machine. Summary: Clients can log onto the network via VPN, they get assigned an IP, but cannot see or be seen by any machines on the network. Does anyone know what could be causing this? It's rather annoying me. Thank you guys. :-D

      oooo, the Jedi's will feel this one....

      E Offline
      E Offline
      Expert Coming
      wrote on last edited by
      #2

      This is usually caused by a DNS issue. A quick way to test if it is, ping the IP Address(the internal one) of a computer on the back end of the VPN connection. I would try a few of the machines on the back end, but if it works, DNS is the culprit.

      The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo

      P 1 Reply Last reply
      0
      • E Expert Coming

        This is usually caused by a DNS issue. A quick way to test if it is, ping the IP Address(the internal one) of a computer on the back end of the VPN connection. I would try a few of the machines on the back end, but if it works, DNS is the culprit.

        The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo

        P Offline
        P Offline
        Paul Unsworth
        wrote on last edited by
        #3

        It sure looks like DNS is the culprit on this. IP addresses can be pinged. Thank you for your help. Because the network is so small (5 machines), and my router, rather than my server handles DNS, I'll just give the clients a new Hosts file as a lazy work around. Thank you. :-D

        oooo, the Jedi's will feel this one....

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups