Discussion Locked

Demand-Dial Routing not connecting

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

Ok, I have a small test network, so this isn't immensely important... BUT it is driving me crazy. I have checked settings and rechecked and poked around and nothing makes sense.

1 2k server and an NT client.
I have been trying to get NAT to work correctly with a demand dial route to my ISP.
Problem is that until I physically go into the RRAS MMC and right-click the demand dial interface and connect the interface, it won't demand dial. After that, it works fine. I can disconnect it and then a half an hour or 2 days later open up IE, wait for it to connect and hit refresh and the connection is live. However, if I reboot, I have to physically connect it again before it works.
The troubleshooting I have done seems to narrow down to the routing table interfaces. My modem does not show an interface until after the first connection. So the only interfaces I have are loopback and my network adapter. Once I connect and even after disconnecting there is an additional interface - a WAN/PPP adapter.
This is the only change I can find. The actual routing table is unchanged from pre-connect state to after the disconnect.
It's an old Supra 28.8 modem. Other than that, the settings are pretty standard.
Any guesses would be appreciated or if anyone has heard of this type of problem with Demand-dial
Thanks
Eric

4 replies

by fenaikh

HI
pls read this part of this article and the other articles.
there has been changes the way to deal with this from win/nt to win2k.
Good Luck.

Mohamed
-----------------------------------------
Article ID: Q256644
Description of Remote Access Wizards
URL:
http://support.microsoft.com/support/kb/articles/Q256/6/44.ASP

Internet Connection Server:

Filters: None.
Router: LAN routing only. Demand-dial routing is turned on
if you select the option to create a new demand-dialinterface
rather than selecting an Internet network adapter.
Remote Access Server: Disabled with NAT, enabled with Internet Connection Sharing.
VPN ports: None. The server does not accept VPN connections.
---------------------------------------------
Article ID: Q254245
Demand Dial Filters Do Not Work When Network Address Translation Is Installed
URL:
http://support.microsoft.com/support/kb/articles/Q254/2/45.ASP
-----------------------------------------
Article ID: Q254231
Change inRemote Access Route Behavior with Windows 2000
URL:
http://support.microsoft.com/support/kb/articles/Q254/2/31.ASP
-----------------------------------------
Article ID: Q241540
OSPF over RRAS Dial-on-Demand and VPN Connections in Windows 2000
URL:
http://support.microsoft.com/support/kb/articles/Q241/5/40.ASP
-----------------------------------------
Article ID: Q247171
Computer Must Be Restarted for DOD Interface to Reconnect if RRAS Terminated
URL:
http://support.microsoft.com/support/kb/articles/Q247/1/71.ASP
---------------------------------------------

by eprehn

I looked through all the the articles, but unfortunately nothing helped as far as getting the DOD interface to work correctly.

by rickmother

Have you checked the service to see if it is set to start automatically? It may be set to manual and that's why you have to go into the MMC and start it and that might also explain why it doesn't work after a reboot.

by eprehn

I thought you were on to something here... I checked services to see what wasn't starting that should have been, but didn't find anything that worked out.

This discussion is closed to new replies.