WAN Dropout with RRAS

I have a RRAS VPN server whose WAN connection occasionally stops working.
The internal network continues to function including DHCP and DNS but I
cannot reach the outside and all VPN connections drop. Disabling and
re-enabling the WAN connection fixes the issue, but I would like to prevent
it from occuring in the first place.

However, the server logs I've examined don't indicate any problem. It may
be the ISP but I don't know how to narrow it down. Are there specific server
logs I can check for further information? Are there any other
troubleshooting techniques I can try that have worked well for others?
Thanks.

We need more information to help you. Is the RRAS also DC? Posting the
result of ipconfig /all may help.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"JxD" <(E-Mail Removed)> wrote in message
news:BA3E884E-7EF0-4AEE-8207-(E-Mail Removed)...
>I have a RRAS VPN server whose WAN connection occasionally stops working.
> The internal network continues to function including DHCP and DNS but I
> cannot reach the outside and all VPN connections drop. Disabling and
> re-enabling the WAN connection fixes the issue, but I would like to
> prevent
> it from occuring in the first place.
>
> However, the server logs I've examined don't indicate any problem. It may
> be the ISP but I don't know how to narrow it down. Are there specific
> server
> logs I can check for further information? Are there any other
> troubleshooting techniques I can try that have worked well for others?
> Thanks.

The RRAS is also a DC. Here is the ipconfig /all output. Thanks for your
help.

Windows IP Configuration

Host Name . . . . . . . . . . . . : pdcserver
Primary Dns Suffix . . . . . . . : dombeck.dombeckweb.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : dombeck.dombeckweb.com
wi.rr.com

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.189
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

Ethernet adapter LAN Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : AE-F0-F1-89-17-78
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.154
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1

Ethernet adapter WAN Connection:

Connection-specific DNS Suffix . : wi.rr.com
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection #2
Physical Address. . . . . . . . . : 56-93-0A-1A-C5-88
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 69.76.94.55
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 69.76.88.1
DHCP Server . . . . . . . . . . . : 76.37.144.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
Lease Obtained. . . . . . . . . . : Friday, January 18, 2008 1:29:38 AM
Lease Expires . . . . . . . . . . : Saturday, January 19, 2008 1:29:38 AM

"Robert L. (MS-MVP)" wrote:

> We need more information to help you. Is the RRAS also DC? Posting the
> result of ipconfig /all may help.
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
>
>
> "JxD" <(E-Mail Removed)> wrote in message
> news:BA3E884E-7EF0-4AEE-8207-(E-Mail Removed)...
> >I have a RRAS VPN server whose WAN connection occasionally stops working.
> > The internal network continues to function including DHCP and DNS but I
> > cannot reach the outside and all VPN connections drop. Disabling and
> > re-enabling the WAN connection fixes the issue, but I would like to
> > prevent
> > it from occuring in the first place.
> >
> > However, the server logs I've examined don't indicate any problem. It may
> > be the ISP but I don't know how to narrow it down. Are there specific
> > server
> > logs I can check for further information? Are there any other
> > troubleshooting techniques I can try that have worked well for others?
> > Thanks.
>
>

We have some issues with this server. 1. the DNS is 127.0.0.1. 2. It is not
recommended to enable RRAS on a DC. If you do, you may have some name
resolution and connectivity issues. This link will give more details.

Name resolution on VPN
Can't ping VPN client by name Connection issues on DC,
ISA, DNS and WINS server as VPN server DNS and Split Tunneling for VPN? How
to assign DNS and WINS on ...
www.chicagotech.net/nameresolutionpnvpn.htm

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"JxD" <(E-Mail Removed)> wrote in message
news:26422D77-A7A1-4BE9-8014-(E-Mail Removed)...
> The RRAS is also a DC. Here is the ipconfig /all output. Thanks for your
> help.
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : pdcserver
> Primary Dns Suffix . . . . . . . : dombeck.dombeckweb.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
> DNS Suffix Search List. . . . . . : dombeck.dombeckweb.com
> wi.rr.com
>
> 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.189
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
>
> Ethernet adapter LAN Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection
> Physical Address. . . . . . . . . : AE-F0-F1-89-17-78
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.154
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 127.0.0.1
>
> Ethernet adapter WAN Connection:
>
> Connection-specific DNS Suffix . : wi.rr.com
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection #2
> Physical Address. . . . . . . . . : 56-93-0A-1A-C5-88
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 69.76.94.55
> Subnet Mask . . . . . . . . . . . : 255.255.248.0
> Default Gateway . . . . . . . . . : 69.76.88.1
> DHCP Server . . . . . . . . . . . : 76.37.144.1
> DNS Servers . . . . . . . . . . . : 127.0.0.1
> Lease Obtained. . . . . . . . . . : Friday, January 18, 2008 1:29:38 AM
> Lease Expires . . . . . . . . . . : Saturday, January 19, 2008 1:29:38
> AM
>
> "Robert L. (MS-MVP)" wrote:
>
>> We need more information to help you. Is the RRAS also DC? Posting the
>> result of ipconfig /all may help.
>>
>> --
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>>
>>
>> "JxD" <(E-Mail Removed)> wrote in message
>> news:BA3E884E-7EF0-4AEE-8207-(E-Mail Removed)...
>> >I have a RRAS VPN server whose WAN connection occasionally stops
>> >working.
>> > The internal network continues to function including DHCP and DNS but I
>> > cannot reach the outside and all VPN connections drop. Disabling and
>> > re-enabling the WAN connection fixes the issue, but I would like to
>> > prevent
>> > it from occuring in the first place.
>> >
>> > However, the server logs I've examined don't indicate any problem. It
>> > may
>> > be the ISP but I don't know how to narrow it down. Are there specific
>> > server
>> > logs I can check for further information? Are there any other
>> > troubleshooting techniques I can try that have worked well for others?
>> > Thanks.
>>
>>