Re: Desperate Housewife Win 2000 Server vpn mess !

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Bill, thank you so much for your reply and interest. OK I want to follow this
slowly if you do not mind. I can remove the 2nd line from Active Routes
(.254) The NIC1 (internet) can remain as Static 81.138.119.225 with gateway
81.138.119.230 (Router IP). The NIC2 (lan) can remain as 192.168.1.10 with
gateway blank. DHCP server remain as 192.168.1.254 (Router) which is where
the vpn clients receive their IP I presume. I haven't tried to make a vpn
connection from local Lan client but will do so asap. I am out of the office
for 3 days so there may be a delay for another post. I hope you can follow my
progress. Thanks again Debora x.

"Bill Grant" wrote:

> Your routing table shows two default routes with the same metric.
> (These are the first two entries starting with 0.0.0.0 ). This will confuse
> RRAS. You need to get rid of the one to 192.168.1.254 . The only default
> route should be out through the public IP interface (81.138.119.225 ). The
> extra route is caused by the default gateway setting of 192.168.1.254, which
> shouldn't be there.
>
> Can you make a VPN connection to the server from a local LAN client?
> (Use the server's LAN IP address). VPN will work over the LAN and this will
> let you check the server setup locally. Make sure this all works before you
> try a remote connection.
>
> Debora wrote:
> > Bob, thanks for the tips.
> > All, I do not have any previous knowledge of Server admin or setup. I
> > may need to further explain myself. Win Server 2000 NIC1(Internet)
> > has static public IP 81.138.119.225 with Gateway as 192.168.1.254 (I
> > thought), NIC2 (lan) IP 192.168.1.10 static from Router DHCP without
> > Gateway entered (I read to do that). Vpn client is receiving same IP
> > as NIC3 (ppp adapter) 192.168.1.73. When 1 Vpn client connects all
> > other Vpn clients receive error. I hope I have followed correct way
> > to ask for further help.
> > Question. Can someone expand on Bob's tips especially the Gateway
> > issue and explain how to fix the IP and vpn setup mess. Thanks again
> > in advance of help. Debora x.
> >
> > "Robert L [MS-MVP]" wrote:
> >
> >> there are some issues on the settings. assuming you don't have a
> >> firewall or router and you enable the NAT, you should not setup two
> >> gateways on the server. also the vpn client and server should not
> >> use the same ip range.
> >>
> >> 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, VPN & 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.
> >>
> >> "Debora" <Debora@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:7924FC6B-1F62-49F8-8BD5-0A4D99BCDC4C@xxxxxxxxxxxxxxxx Hi
> >> everyone (apologies for subject line), This is my first post EVER
> >> and I'm slightly nervous. I have read many posts/solutions and
> >> tried them on our server. I am now desperate for help and looking
> >> for a saviour. I hope someone can guide or advise me. --
> >> I have inherited a task to setup vpn on above server (access only
> >> needed to server), which I have attempted to do via approp.wizard.
> >> Our system is Server with 2 NIC's, DHCP via Router, DHCP disabled
> >> on Server. Vpn connections are pptp(10 ports) only. Router is
> >> configured to allow vpn traffic. I have connected from my home
> >> WinXP machine via vpn connection but cannot see or use any files
> >> on the vpn server. Other connections fail when I'm connected and
> >> internet access doesn't work for other lan clients. I have 'route
> >> print' info which is below. Hope this posting is not too long!
> >> Debora x.
> >>
> >> Questions. Can someone advise if my vpn setup is correct and offer
> >> any help please?
> >> ---
> >> Server data
> >>
> >> Microsoft Windows 2000 [Version 5.00.2195]
> >>
> >> C:\Documents and Settings\administrator.WOTNOT-UK>route print
> >> =====================================================Interface List
> >> 0x1 ........................... MS TCP Loopback interface
> >> 0x1000002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> >> 0x1000003 ...00 30 bd b5 fb 08 ...... NDIS 5.0 driver
> >>
> >> 0x1000004 ...00 10 5c bd 31 33 ...... SiS NIC SISNIC
> >> =====================================================Active Routes:
> >> Network Destination Netmask Gateway
> >> Interface Metric
> >> 0.0.0.0 0.0.0.0 81.138.119.230
> >> 81.138.119.225 1
> >> 0.0.0.0 0.0.0.0 192.168.1.254
> >> 192.168.1.10 1
> >> 81.138.119.224 255.255.255.248 81.138.119.225
> >> 81.138.119.225 1
> >> 81.138.119.225 255.255.255.255 127.0.0.1
> >> 127.0.0.1 1
> >> 81.255.255.255 255.255.255.255 81.138.119.225
> >> 81.138.119.225 1 127.0.0.0 255.0.0.0
> >> 127.0.0.1 127.0.0.1 1 192.168.1.0
> >> 255.255.255.0 192.168.1.10 192.168.1.10 1
> >> 192.168.1.10 255.255.255.255 127.0.0.1
> >> 127.0.0.1 1 192.168.1.73 255.255.255.255
> >> 127.0.0.1 127.0.0.1 1 192.168.1.255
> >> 255.255.255.255 192.168.1.10 192.168.1.10 1
> >> 195.137.116.49 255.255.255.255 81.138.119.230
> >> 81.138.119.225 1 224.0.0.0 224.0.0.0
> >> 81.138.119.225 81.138.119.225 1 224.0.0.0 224.0.0.0
> >> 192.168.1.10 192.168.1.10 1 255.255.255.255
> >> 255.255.255.255 192.168.1.10 192.168.1.10 1 Default
> >> Gateway: 192.168.1.254
> >> =====================================================Persistent
> >> Routes: None --- --- --- --- --- --- --- --- C:\Documents and
> >> Settings\administrator.WOTNOT-UK>ipconfig /all Windows 2000 IP
> >> Configuration
> >>
> >> Host Name . . . . . . . . . . . . : Lds
> >> Primary DNS Suffix . . . . . . . : watnot.co.uk
> >> Node Type . . . . . . . . . . . . : Hybrid
> >> IP Routing Enabled. . . . . . . . : Yes
> >> WINS Proxy Enabled. . . . . . . . : No
> >> DNS Suffix Search List. . . . . . : watnot.co.uk
> >> co.uk
> >>
> >> Ethernet adapter Realtek NIC-lan:
> >>
> >> Connection-specific DNS Suffix . :
> >> Description . . . . . . . . . . . : Realtek
> >> RTL8139(A)-based PCI Fast Et
> >> hernet Adapter
> >> Physical Address. . . . . . . . . : 00-30-BD-B5-FB-08
> >> DHCP Enabled. . . . . . . . . . . : No
> >> IP Address. . . . . . . . . . . . : 192.168.1.10
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >> Default Gateway . . . . . . . . . : 192.168.1.254
> >> DNS Servers . . . . . . . . . . . : 192.168.1.254
> >> 192.168.1.254
> >>
> >> Ethernet adapter SiS 900 NIC-internet:
> >>
> >> Connection-specific DNS Suffix . :
> >> Description . . . . . . . . . . . : SiS 900 PCI Fast
> >> Ethernet Adapter Physical Address. . . . . . . . . :
> >> 00-10-5C-BD-31-33 DHCP Enabled. . . . . . . . . . . : No
> >> IP Address. . . . . . . . . . . . : 81.138.119.225
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.248
> >> Default Gateway . . . . . . . . . : 81.138.119.230
> >> DNS Servers . . . . . . . . . . . : 192.168.1.254
> >> NetBIOS over Tcpip. . . . . . . . : Disabled
> >>
> >> PPP adapter RAS Server (Dial In) Interface:
> >>
> >> Connection-specific DNS Suffix . :
> >> Description . . . . . . . . . . . : WAN (PPP/SLIP)
> >> Interface Physical Address. . . . . . . . . :
> >> 00-53-45-00-00-00 DHCP Enabled. . . . . . . . . . . : No
> >> IP Address. . . . . . . . . . . . : 192.168.1.73
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> >> Default Gateway . . . . . . . . . :
> >> DNS Servers . . . . . . . . . . . : 127.0.0.1
> >> ---
> >> Windows XP client data
> >> ======================
> >> Interface List
> >> 0x1 ........................... MS TCP Loopback interface
> >> 0x2 ...00 11 11 df dd c7 ...... Intel(R) PRO/100 VE Network
> >> Connection - Packet
> >> Scheduler Miniport
> >> 0x80004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> >> ======================
> >> Active Routes:
> >> Network Destination Netmask Gateway
> >> Interface Metric
> >> 0.0.0.0 0.0.0.0 192.168.1.1
> >> 192.168.1.3 20
> >> 81.138.119.225 255.255.255.255 192.168.1.1
> >> 192.168.1.3 20 127.0.0.0 255.0.0.0
> >> 127.0.0.1 127.0.0.1 1 192.168.1.0
> >> 255.255.255.0 192.168.1.3 192.168.1.3 20
> >> 192.168.1.0 255.255.255.0 192.168.1.73
> >> 192.168.1.73 1 192.168.1.3 255.255.255.255
> >> 127.0.0.1 127.0.0.1 20 192.168.1.73
> >> 255.255.255.255 127.0.0.1 127.0.0.1 50
> >> 192.168.1.255 255.255.255.255 192.168.1.3
> >> 192.168.1.3 20 192.168.1.255 255.255.255.255
> >> 192.168.1.73 192.168.1.73 50 224.0.0.0 240.0.0.0
> >> 192.168.1.3 192.168.1.3 20 224.0.0.0 240.0.0.0
> >> 192.168.1.73 192.168.1.73 50 255.255.255.255
> >> 255.255.255.255 192.168.1.3 192.168.1.3 1
> >> 255.255.255.255 255.255.255.255 192.168.1.73 192.168.1.73
> >> 1 Default Gateway: 192.168.1.1 ======================
> >> Persistent Routes: None
> >>
> >> Windows IP Configuration
> >> Host Name . . . . . . . . . . . . : dell-pc
> >> Primary Dns Suffix . . . . . . . :
> >> Node Type . . . . . . . . . . . . : Broadcast
> >> IP Routing Enabled. . . . . . . . : No
> >> WINS Proxy Enabled. . . . . . . . : No
> >>
> >> Ethernet adapter Local Area Connection:
> >>
> >> Connection-specific DNS Suffix . :
> >> Description . . . . . . . . . . . : Intel(R) PRO/100 VE
> >> Network Connecti
> >> on
> >> Physical Address. . . . . . . . . : 00-11-11-DF-DD-C7
> >> Dhcp Enabled. . . . . . . . . . . : Yes
> >> Autoconfiguration Enabled . . . . : Yes
> >> IP Address. . . . . . . . . . . . : 192.168.1.3
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >> Default Gateway . . . . . . . . . : 192.168.1.1
> >> DHCP Server . . . . . . . . . . . : 192.168.1.1
> >> DNS Servers . . . . . . . . . . . : 192.168.1.1
> >> Lease Obtained. . . . . . . . . . : 17 June 2005 11:07:11
> >> Lease Expires . . . . . . . . . . : 24 June 2005 11:07:11
> >>
> >> PPP adapter Lds:
> >>
> >> Connection-specific DNS Suffix . :
> >> Description . . . . . . . . . . . : WAN (PPP/SLIP)
> >> Interface Physical Address. . . . . . . . . :
> >> 00-53-45-00-00-00 Dhcp Enabled. . . . . . . . . . . : No
> >> IP Address. . . . . . . . . . . . : 192.168.1.73
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> >> Default Gateway . . . . . . . . . :
> >> DNS Servers . . . . . . . . . . . : 192.168.1
>
>
>
.

Relevant Pages

  • RE: VPN issue on SBS2003
    ... I understand that you encountered VPN connection issue when you use VPN to ... Internet clients or VPN to external VPN Server from SBS Client computers? ... Configure E-mail and Internet Connection Wizard ... Total GRE packets sent = 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: PPTP VPN connection problems
    ... The problem is that the VPN does not disconnect. ... However after some idle period I can not send packets across the connection. ... A ping to the server would result in "Request timed out". ... If I connect with the VPN client locally to the internet ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Ports to Open
    ... the VPN connection after you change the firewall before SBS. ... On the server, please stop the Routing and Remote Access service. ... Total GRE packets sent = 1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2003 VPN Default Gateway Issues
    ... Ethernet adapter Local Area Connection: ... If the VPN server is configured to use a static IP address ... the default gateway on the client is not the problem. ...
    (microsoft.public.windows.server.networking)
  • RE: VPN Connectivity issues through LAN
    ... I understand that you cannot ping SBS after ... you can establish VPN connection from the remote LAN. ... You have to rerun the CEICW to make sure your SBS 2003 server have right ...
    (microsoft.public.windows.server.sbs)