Re: Need help with VPN

From: brad (anonymous_at_discussions.microsoft.com)
Date: 10/05/04


Date: Tue, 5 Oct 2004 11:22:21 -0700

Reading through some older posts I came upon a similar
situation. Does the Client VPN Network Adapter need to
have it's DNS point to the server, or does it need to be
the External Network Adapter need to have its DNS point to
the server. If its the VPN Connection, how would I change
this. Thanks.

>-----Original Message-----
>I did use the wizard to create it, but started messing
>around with the NAT/Firewall (created a connection under
>Routing and remote access module), but then deleted it. I
>can rerun the wizard and start over. As for the server, I
>had set the IP to a static 192.168.0.99. it is using 1
nic.
>
>
>>-----Original Message-----
>>Did you use the Remote Access Wizard to setup the VPN
(on
>the To Do List,
>>right below the CEICW)? It doesn't look like you did. I
>suggest you start by
>>runing it.
>>
>>Anayway, the reason I asked to repost that is because
I'm
>seeing some weird
>>IPs on it and I thought it might have changed since you
>posted it. Is the IP
>>of the server 192.168.0.99? and you are using 1 NIC
right?
>>
>>--
>>Javier [SBS MVP]
>>
>><< SBS ROCKS!!! >>
>>
>>"brad" <anonymous@discussions.microsoft.com> wrote in
>message
>>news:37f301c4aaf3$e90dff40$a301280a@phx.gbl...
>>>I am at work right now and do not have access to the
>>> server or the client pc to login via VPN. However, at
>the
>>> bottom of this post you will see my ipconfig /all from
>>> yesterday. Does that help or will you need to see it
>from
>>> the server as well?
>>>
>>>
>>>>-----Original Message-----
>>>>Sorry... I meant only the internet access portion. I'm
>>> not sure why Network
>>>>Neighborhood or drive mapping doesn't work. Can you
>>> repost the IPConfig /all
>>>>for the workstation when its connected to the VPN (and
>>> from the server just
>>>>for completeness).
>>>>
>>>>--
>>>>Javier [SBS MVP]
>>>>
>>>><< SBS ROCKS!!! >>
>>>>
>>>>"brad" <anonymous@discussions.microsoft.com> wrote in
>>> message
>>>>news:378601c4aaee$6e36a5b0$a301280a@phx.gbl...
>>>>> So are you saying that all 3 of my issues, internet
>>>>> access, share drive mapping and network neighborhood
>are
>>>>> not usable by design? If so, then what is the point
of
>>>>> using the VPN? Sorry, I just don't have any
experience
>>>>> with VPN.
>>>>>
>>>>>>-----Original Message-----
>>>>>>That is correct. The solution would be to configure
>the
>>>>> PC to use the SBS
>>>>>>for the internet connection... any other solution
>(like
>>>>> disabling "Use
>>>>>>default gateway on remote network") will be a
>potential
>>>>> security risk.
>>>>>>
>>>>>>--
>>>>>>Javier [SBS MVP]
>>>>>>
>>>>>><< SBS ROCKS!!! >>
>>>>>>
>>>>>>"grep" <grep@grep.com> wrote in message
>>>>>>news:uya5HiuqEHA.2424@TK2MSFTNGP10.phx.gbl...
>>>>>>> I'm not sure, but that may be a feature, not a bug.
>>>>> Most VPN solutions do
>>>>>>> that for security reasons. The VPN client will
>>>>> typically *only* speak to
>>>>>>> the VPN while it's connected so that there's less
>>>>> chance of someone else
>>>>>>> piggybacking their way into the protected network.
>>>>>>>
>>>>>>> grep
>>>>>>>
>>>>>>> Brad wrote:
>>>>>>>
>>>>>>>> Alright, i have changed the client router to be
in
>a
>>>>> different scope
>>>>>>>> 192.168.2.x so now I can ping the server using
the
>ip
>>>>> address and
>>>>>>>> server.com.local. However, I can't access the
>>> internet
>>>>> while vpn'd in, I
>>>>>>>> tried the net use \\server\test (shared folder on
>f:
>>>>> drive) but it
>>>>>>>> wouldn't map the folder and I can not use the
>network
>>>>> neighboor hood, it
>>>>>>>> just locks up. What am I doing wrong. Thanks.
>>>>>>>>
>>>>>>>>
>>>>>>>>>-----Original Message-----
>>>>>>>>
>>>>>>>>>>From your output, it appears that the client
>machine
>>>>> has
>>>>>>>> the following IP
>>>>>>>>>address assigned to his physical NIC
>>>>>>>>>192.168.0.2
>>>>>>>>>
>>>>>>>>>The server Internal IP address appears to be
>>>>> 192.168.0.99
>>>>>>>>>
>>>>>>>>>If this is the case, then it explains the problem.
>>>>>>>>>
>>>>>>>>>The client NIC and the server NIC are on the same
>>>>> network.
>>>>>>>>>
>>>>>>>>>When the client sends a request to the server the
>>>>> request
>>>>>>>>
>>>>>>>> with go out the
>>>>>>>>>local NIC instead of through the VPN tunnel.
>>>>>>>>>
>>>>>>>>>You need to change the IP address of the client so
>>> that
>>>>>>>>
>>>>>>>> it is in a
>>>>>>>>>different network.
>>>>>>>>>
>>>>>>>>>His address would need to be something like
>>> 192.168.2.2
>>>>>>>>
>>>>>>>> and his router
>>>>>>>>>would need to be changed as well.
>>>>>>>>>
>>>>>>>>>Or as an alternative, you can change the IP
address
>>> on
>>>>>>>>
>>>>>>>> the server.
>>>>>>>>
>>>>>>>>>Best Regards,
>>>>>>>>>
>>>>>>>>>John Bay, MCSE 2003
>>>>>>>>>Microsoft Support Engineer
>>>>>>>>>
>>>>>>>>>This posting is provided "AS IS" with no
>warranties,
>>>>> and
>>>>>>>>
>>>>>>>> confers no rights.
>>>>>>>>
>>>>>>>>>-----Original Message-----
>>>>>>>>>Hello,
>>>>>>>>>
>>>>>>>>>I am able to login into the SBS2003 using VPN
>>>>>>>>>connection. However, I am not
>>>>>>>>>able to use any resources on it such
>>>>>>>>>as Internet access, network neighborhood or share
>>>>>>>>>drives. I try to do a
>>>>>>>>>search for the server by name and it won't come.
>>>>>>>>>I try to ping the server by name or IP address
and
>it
>>>>>>>>>times out. The IP
>>>>>>>>>range on the SBS2003s router is 192.168.0.1
>to .100,
>>>>>>>>>so I made the range for the VPN client to receive
>>>>>>>>>192.168.0.101 to .50.
>>>>>>>>>Besides runnnig CECIW, do I need to do anything
>under
>>>>>>>>>the Remote and routing
>>>>>>>>>Access module? here
>>>>>>>>>is the ipconfig /all info. Also, I have tried
this
>on
>>>>> my
>>>>>>>>>Win2k Laptop and my
>>>>>>>>>XP Pro SP2 desktop and both are able to login
>>>>>>>>>but can not go any further than that.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Windows IP Configuration
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Host Name . . . . . . . . . . . . : amd220
>>>>>>>>>
>>>>>>>>> Primary Dns Suffix . . . . . . . :
>>>>>>>>>
>>>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>>>>
>>>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>>>>
>>>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>>>
>>>>>>>>> DNS Suffix Search List. . . . . . :
>>>>>>>>>MMRXRAY.com.local
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Ethernet adapter Local Area Connection:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Connection-specific DNS Suffix . :
>>>>>>>>>
>>>>>>>>> Description . . . . . . . . . . . : Realtek
>>>>>>>>>RTL8139/810x Family Fast
>>>>>>>>>Ethernet NIC
>>>>>>>>>
>>>>>>>>> Physical Address. . . . . . . . . : 00-0D-
>61-
>>> 57-
>>>>>>>>>41-D9
>>>>>>>>>
>>>>>>>>> Dhcp Enabled. . . . . . . . . . . : Yes
>>>>>>>>>
>>>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>>>>
>>>>>>>>> IP Address. . . . . . . . . . . . :
>>> 192.168.0.2
>>>>>>>>>
>>>>>>>>> Subnet Mask . . . . . . . . . . . :
>>>>> 255.255.255.0
>>>>>>>>>
>>>>>>>>> Default Gateway . . . . . . . . . :
>>> 192.168.0.1
>>>>>>>>>
>>>>>>>>> DHCP Server . . . . . . . . . . . :
>>> 192.168.0.1
>>>>>>>>>
>>>>>>>>> DNS Servers . . . . . . . . . . . :
>>> 216.68.4.10
>>>>>>>>>
>>>>>>>>>
>>> 216.68.5.10
>>>>>>>>>
>>>>>>>>> Lease Obtained. . . . . . . . . . : Sunday,
>>>>>>>>>October 03, 2004
>>>>>>>>>11:38:49 AM
>>>>>>>>>
>>>>>>>>> Lease Expires . . . . . . . . . . : Sunday,
>>>>>>>>>October 10, 2004
>>>>>>>>>11:38:49 AM
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>PPP adapter Connect to Small Business Server:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Connection-specific DNS Suffix . :
>>>>>>>>>MMRXRAY.com.local
>>>>>>>>>
>>>>>>>>> Description . . . . . . . . . . . : WAN
>>>>>>>>>(PPP/SLIP) Interface
>>>>>>>>>
>>>>>>>>> Physical Address. . . . . . . . . : 00-53-
>45-
>>> 00-
>>>>>>>>>00-00
>>>>>>>>>
>>>>>>>>> Dhcp Enabled. . . . . . . . . . . : No
>>>>>>>>>
>>>>>>>>> IP Address. . . . . . . . . . . . :
>>>>> 192.168.1.105
>>>>>>>>>
>>>>>>>>> Subnet Mask . . . . . . . . . . . :
>>>>>>>>>255.255.255.255
>>>>>>>>>
>>>>>>>>> Default Gateway . . . . . . . . . :
>>>>> 192.168.1.105
>>>>>>>>>
>>>>>>>>> DNS Servers . . . . . . . . . . . :
>>> 192.168.0.99
>>>>>>>>>
>>>>>>>>> Primary WINS Server . . . . . . . :
>>> 192.168.0.99
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>.
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>.
>>>>>>
>>>>
>>>>
>>>>.
>>>>
>>
>>
>>.
>>
>.
>



Relevant Pages

  • Re: feeling dizzy about setting up a small remote office.
    ... | dcpromo a new server ... | - installed dns, killed the dns wizard ... | the remote end of the vpn tunnel. ... |> of the VPN router to its public IP address, ...
    (microsoft.public.windows.server.active_directory)
  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: feeling dizzy about setting up a small remote office.
    ... dcpromo a new server ... - installed dns, killed the dns wizard ... the remote end of the vpn tunnel. ... > of the VPN router to its public IP address, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Error: cant find _ldap._tcp.dc._msdc.
    ... domain over a VPN? ... The DNS server name as listed in the DNS manager is cda.cdaxxxx.org.uk ... VPN connection to the top of the connections list. ...
    (microsoft.public.windows.server.dns)
  • Re: How to configure for Two different IP subnets
    ... Active Directory will go haywire in a setup like that. ... AD integrates with the local DNS, so you cannot use the DNS at your ISP ... With Server 2003 Standard ... for its internal interface (ie the VPN endpoint). ...
    (microsoft.public.windows.server.networking)