Computer name hidden when using VPN?

When I connect to my corporate VPN from my home PC (using a Cisco VPN client, over a WIFI network through a cable modem/router setup), it appears my computer name is being obscured from the server, which is preventing access to some resources (such as CVS). When I try to ping my machine (the "client" IP address as reported by the VPN client) from a work server, it pings successfully, but does not report the computer name. I thought maybe my router was doing some filtering, so I configured my LAN IP to be on the DMZ (direct internet access), and enabled PPTP and WAN pass-through access. But still, no luck. Any ideas? Thanks!

Answer Wiki

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

What kind of router do you have? What kind of wireless adapter? Have you tried connecting the PC directly to the modem to determine if the router is the source of the trouble? What OS? What version of Cisco VPN?

Discuss This Question: 3  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.
  • Douger
    Hey snag, A couple of thoughts. Do you know which protocol carries the computer name? I couldn't find it in a quick search but I believe that used to be netbios only. I think tcp/ip carries it as well now. If it is not tcp/ip it won't cross the vpn boundary. Are you filtering any traffic at the firewall coming through on the vpn, or is it all allowed? If there are any filters that might be the problem. Also, a quick fix would be to edit the hosts file on the server you are trying to connect to, and put in the ip address and name of your home machine. The server will look there to build it's dns list. For this to be a permanent fix you are going to need a static ip for your vpn connection. Good luck, Doug
    0 pointsBadges:
  • Howard2nd
    Douger has it right. Pings apply to IP addresses and it the internal routing table (hosts & lmhosts) or DNS know the name then it resolves to an IP address and can be pinged. Name resolution is NetBIOS / Computer Browser in DOS/95/98/ME and deliberately deprecated in 2000/XP. A - be sure NetBIOS over TCP is enabled on the system initiating the VPN session so the name is passed to the network. If the machines at work are 'browsable' then the service (NetBios over TCP) is enabled thru the router. B - Do you get the same IP address on EVERY vpn session? If so the the hosts/lmhosts tables will work. If it changes then a static record does you no good. C - Windows offers two mechanisms for dealing with 'dynamic' addresses. WINS which has flaws and is NOT recommended and DNS (Domain Name Service). DNS is the preferred method of attaching Name ot IP address. Set your system to register in the network configuration. That said - why do you NEED a system connecting thru VPN from 'HOME' to be browsable by systems on the network. Last point - you connect thru a WiFi to cable modem/router. Have you ever attached a second system to the WAP to see if the 'Name' gets that far? Or attached to the router to see if it is visible? Some wireless connections deprecate 'names' to protect systems from drive-by browsing.
    30 pointsBadges:
  • Snagiel
    Thanks for your replies; I've learned some interesting points about networking. It turns out my issues (about using CVS) were not tied to the client name of my computer, but rather the username I was logged in as in XP, which was inconsistent with the username of my machine at work. Using the VPN client's IP (which is dynamic on every session) is sufficient to authenticate me on the server, but does require me to update the etc/hosts file every time (since we're using server authentication). Thanks again.
    0 pointsBadges:

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.


Share this item with your network: