VPN Sub Nets

Discussion in 'Windows Networking' started by Clarkclan, Oct 11, 2004.

  1. Clarkclan

    Clarkclan Guest

    I have just upgraded from Windows 98 fo XP Pro and I am
    having a problem with
    my VPN.

    I can connect to the network but I cannot see any
    workstations on the
    network. If I know the name of a workstation I can enter
    it but I am trying
    to make a new network connection and cannot.

    When I connect via the VPN I get an automatic address
    which fits in with the
    sequence but the Sub net Mask is different and although I
    can put in a manual
    IP address I cannot seem to change the Subnet Mask.
     
    Clarkclan, Oct 11, 2004
    #1
    1. Advertisements

  2. On a point to point connection, your subnet mask should be 255.255.255.255.

    Try changing the properties on the VPN client to clear the check box for
    "use default gateway on remote network."

    Doug Sherman
    MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
     
    Doug Sherman [MVP], Oct 11, 2004
    #2
    1. Advertisements

  3. Define "see".
    VPN doesn't provide "naming" nor does it provide "network browing" (Net
    Neighborhood). Naming must be provided either via WINS or LMHosts files.

    Network "browsing" is provided by Master Browsers that maintain a "browse
    list" and is very difficult to get working over a slow VPN Link,...it was
    designed for LAN speeds not slow link speeds. It isn't worth fighting with.
    That is normal and correct,..don't bother it.
     
    Phillip Windell, Oct 12, 2004
    #3
  4. I have had the same problem over VPN connections. I have found that I am
    always able to browse the network with NetBIOS names if I am connected to the
    VPN with a machine that is already a part of the domain that I am connecting
    to. If I try from my home machine i can never browse the network but can
    only map things using IP addresses. So there is no real way around this?
     
    =?Utf-8?B?TWFydHkgUw==?=, Feb 21, 2005
    #4
  5. this is the nameresolution issue. Do your VPN server assign DNS and/or WINS to the VPN client? this VPN Name resolution may help, http://www.chicagotech.net/nameresolutionpnvpn.htm

    Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

    Bob Lin, MS-MVP, MCSE & CNE
    How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
    Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
    This posting is provided "AS IS" with no warranties.
    I recommend Brinkster for web hosting!

    I have had the same problem over VPN connections. I have found that I am
    always able to browse the network with NetBIOS names if I am connected to the
    VPN with a machine that is already a part of the domain that I am connecting
    to. If I try from my home machine i can never browse the network but can
    only map things using IP addresses. So there is no real way around this?
     
    Robert L [MS-MVP], Feb 21, 2005
    #5
  6. Yes the RRAS server is handing out IP, DNS and WINS.
     
    =?Utf-8?B?TWFydHkgUw==?=, Feb 21, 2005
    #6
  7. Clarkclan

    Todd J Heron Guest

    If I try from my home machine i can never browse the network but can only
    There is a way around this for you, since you stated:

    "I have found that I am always able to browse the network with NetBIOS names
    if I am connected to the VPN with a machine that is already a part of the
    domain that I am connecting to."

    Since your IP routing device (the VPN hardware) is not blocking NetBIOS
    broadcasts, then:

    1) Join your home computer to the corporate domain :)
    2) If you don't like #1 give your home computer the same workgroup name as
    the corporate domain

    A machine's workgroup or domain membership will effect how the Microsoft
    Windows Network is displayed in Network Places. In a workgroup or domain,
    the browse list in Network Places appears the same for all machines (as it
    is assumed they will share resources).
     
    Todd J Heron, Feb 21, 2005
    #7
  8. Clarkclan

    Bill Grant Guest

    What Todd has said is pretty much the hub of the problem. The vital
    element is that the client must know the name of the remote domain.

    Because the link doesn't carry broadcasts, you have to rely on WINS to
    find a browse master for you. The client doesn't seem to be able to do this
    for anything except the domain master browser.

    If you monitor the network traffic, you will see that the client tries
    to get a browse list by sending a request to WINS for the special Netbios
    name <domainname 1B> (which is the DMB). If the client has the correct
    name for the remote domain, this works and you get the domain browse list
    from the DMB.

    If the client doesn't have the correct name for the remote domain, it
    just sits there resending its request until it times out, because WINS can't
    resolve the name it sends.
     
    Bill Grant, Feb 21, 2005
    #8
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.