Windows Forum

Ask something
Discussion Locked

NAT Continually Redailing

0 helpful
5 replies

by russell.purdy

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have set up NAT on a W2K server OK. Clients can connect OK and initiate the demand dial connection (when the problem BELOW hasnt already connected).

The problem is that although I have set it to only demand dial, it (on the majority of occasions) dials my ISP as soon as I plug the modem into the phone line!
If I disconnect it using the routing & remote access mmc /routing interfaces/modem, it immediatly dials out
again.
It disconnects after periods of inactivity
set in mmc/routing interfaces/modem-properties/options
(set to Demand Dial-Idle Time 1 Min &Redial attempts1-
Average Redial interval 1 Min). But then immediately dials out again!
Any Ideas?

.

5 replies

by shanghai sam

open DNS console,open up properties of your server,under monitoring uncheck (automatic testing at the following interval)and allow for only manual query agains local or external DNS server.

post back on how you get on!

by shanghai sam

Checked the test interval setting but it is not ticked.
I did try ticking it and setting its interval at 5 Hrs to see if this would prevent it dialing but it did not.
I believe this answer is along the right lines, ie somthing asking for access for a specific reason but in this case it is not the answer. Thanks.

by khuffmanjr

hi,

many programs will check for internet connectivity repeatedly by default. upon doing this, NAT initiates the demand dial connection. there's really no way to keep this from happening (it's the "demand" part that does it...).

i have foundthat disabling Automatic Windows Update on all NAT clients will reduce the frequency of this occurence. also, check some others apps on your net, such as Adobe Acrobat, and Acrobat Reader. they check for connectivity when they start.

hope this helps

K

by russell.purdy

Found the following (part of the full answer)in the Help files>>>>>>

This was the problem!!!

Demand-dial routing updates While demand-dial routing can save connection costs, typical routing protocols rely on a periodic advertising process to communicate routing information. For example, RIP for IP advertises the contents of its routing table every 30 seconds on all interfaces. This behavior is not a problem for permanently connected LAN or WAN lines. For usage-sensitive dial-up WAN lines, this type of periodic behavior could cause the router to call another router every 30 seconds, which may result in an undesirable phone bill. Therefore, you should not run routing protocols across temporary dial-up WAN lines.

This discussion is closed to new replies.