VPN/RRAS

[SS]

I have a problem with a single Win2K server. It is everything in a small
company. They recently added broadband, and wanted a VPN setup (basic
PPTP). We ran into an issue with the router to begin with. It didn't like
192.168.0.x addresses, where 192.168.0.1 was the server's IP. I added
x.x.1.1 and it routed fine. So I removed the x.x.0.1 and updated the DHCP,
etc. After getting the AD working again I again tried to setup the VPN/RRAS
using essentially the defaults. The first try, I couldn't select the single
NIC as the internet interface (where I've set it up a number of times with
just one NIC). It kept telling me that it needed two interfaces.

the routes it has are:

Interface List
0x1 ........................... MS TCP Loopback interface
0x1000002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x1000003 ...00 c0 9f 34 6a 14 ...... Intel(R) PRO/1000 MT Network
Connection
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.25 192.168.1.1 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.1 192.168.1.1 1
192.168.1.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.64 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.1 192.168.1.1 1
224.0.0.0 224.0.0.0 192.168.1.1 192.168.1.1 1
255.255.255.255 255.255.255.255 192.168.1.1 192.168.1.1 1
Default Gateway: 192.168.1.25
===========================================================================
Persistent Routes:
None


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The routes from a server that are working perfectly are:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x1000003 ...00 07 e9 b4 77 56 ...... Intel(R) PRO Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.7 10.0.0.20 1
10.0.0.0 255.255.255.0 10.0.0.20 10.0.0.20 1
10.0.0.20 255.255.255.255 127.0.0.1 127.0.0.1 1
10.0.0.29 255.255.255.255 127.0.0.1 127.0.0.1 1
10.0.0.201 255.255.255.255 10.0.0.210 10.0.0.210 1
10.0.0.208 255.255.255.255 10.0.0.210 10.0.0.210 1
10.0.0.210 255.255.255.255 127.0.0.1 127.0.0.1 1
10.0.0.254 255.255.255.255 10.0.0.210 10.0.0.210 1
10.255.255.255 255.255.255.255 10.0.0.20 10.0.0.20 1
24.24.43.181 255.255.255.255 10.0.0.7 10.0.0.20 1
66.67.120.55 255.255.255.255 10.0.0.7 10.0.0.20 1
67.50.33.92 255.255.255.255 10.0.0.7 10.0.0.20 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 224.0.0.0 10.0.0.20 10.0.0.20 1
255.255.255.255 255.255.255.255 10.0.0.20 10.0.0.20 1
Default Gateway: 10.0.0.7
===========================================================================
Persistent Routes:
None
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Whether I try to VPN from outside or from inside it gets to the point where
it's "verifying username and password" and then just times out. The event
logs on client and server show nothing. But the RRAS log shows the
connection attempt.

Help!!!

Stephen

p.s. I finally installed it as a Dial up server, and it took 3 or 4 times
of uninstall and install before the WAN/Dial-in interface was created and
appeared and actually had an address.

 

[Alex]

I'm having the exact same problem with two of my servers.
If have an interface called internal it will show up as
not available under the ip routing in the RAS snap in, but
if you look at it's status in the routing interfaces
dialouge it says the interface is working just fine. And
if you use the dos command netsh to show the ip routing
interfaces it too says the internal interface is up, which
it isn't. This is a known problem to microsoft and they
have yet to fix it, i have bee three stright days trying
to figure this out. I have formatted this computer six
times and reinstalled windows and still nothing. Sorry i
couldn't be much help, but i figured you would find it
comforting to know that other people are just as ready to
shoot the vpn service as you are. Let me know if you
figure anything out.

 

[SS]

Thanks, it's nice to know I'm not crazy. If I find anything I'll be sure to
let you know.