Demand Dial connection is not connecting

E

Ethan

I am attempting to use RRAS to dial up a connection to an ISP. The WIN2k
server I have this running on has the latest patches installed and RRAS up
and running. The Demand Dial connection is "listening" but will not initiate
a dial out connection when any of the machines on the LAN launch a browser
window. This includes the machine with WIN2k on it. If I manually initiate
the connection none of the machines on the network can browse. Any thoughts?

Ethan
 
T

Terry Liu [MSFT]

Hi Ethan,

As I understand, on demand dial connection doesn't occur automatically.
RRAS is usually used for client computers to dial in to his network, not
for computers to dial-out to ISP.

I. If you want to share the connections, you can create a dial-up
connection to your ISP and share it using Internet Connection Sharing (ICS).
II. If you are using DOD connection with his ISP, please let me how you set
it up on both your side and ISP's side.

Please first clarify the followings:

1. Please let us know the network topology.
2. Please check whether static routes have been added to rigger a DOD.
3. Check event log for more information.
4. Restart remoteaccess by follow the steps below to check the issue again:
You can also restart RRAS from the command line:
C:\> net stop remoteaccess
C:\> net start remoteaccess
5. Did you receive any error message?

Next, I suggest you enable RRAS and DUN logging. Certain registry keys to
enable RRAS and DUN logging are not present in the registry immediately
after you perform a "clean" installation of Windows 2000. These keys are
not added because there is not yet a connection that will use them.

Some of these keys are: BAP, IPBOOTP, PPP, RASIPCP, RASCHAP, RASPAP,
RASSPAP, and so on.

To make these keys appear, create a DUN connection:

1. Click Start, point to Settings, and then click "Network and Dial-up
Connections".
2. Click Make New Connection.
3. Follow the instructions in the "Network Connection wizard" to create a
new dial-up connection. Creating a new connection creates the registry keys
listed above.

The keys are created in the registry under the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing

Certain other components in the Windows 2000 Server products add additional
options to the Tracing key. Items such as routing protocols (RIP and OSPF),
Dial-on-Demand connections, and the Internet Authentication Service (IAS)
have several components for which logging may be enabled.

In addition, I would like to let you know that it is necessary to add
static routes in the route table to trigger a DOD interface to make a
connection. This is the opposite of how RIP and OSPF operate, because RIP
and OSPF do not require static routes to operate. In fact, RIP and OSPF are
designed to prevent an administrator from having to add static routes to a
route table. RIP and OSPF simply listen for dynamic route updates and add
new routes to the route table as appropriate.

For detailed information, please refer to this Knowledge Base article:
235492 RIP and OSPF Do Not Start Dial On Demand Connections --
http://support.microsoft.com/?id=235492

For your reference: 178993 How to Use Static Routes with Routing and Remote
Access Service -- http://support.microsoft.com/?id=178993

Hope this address your concern.

Best regards,

Terry Liu
MCSE 2K MCSA MCDBA CCNA
Microsoft Online Support Engineer

Get Secure! - <www.microsoft.com/security>
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
P

pdbasham

Ethan

A outbound demand dial NAT server will work, (sorry
Terry), mine works fine. When I was having similar
problems to you (ie. demand dial did not work) my clients
could connect if I manually dialed the connection, this
was due to a missing static route. Yours cannot connect at
all.

Ensure:
1.As Terry correctly states, a static route must exist.
2.Ensure clients have the default gateway of your INTERNAL
interface.
3.Ensure Internet explorer connection settings are correct
ie no proxy, do not detect settings automatically, and
never dial a connection.

Hope this helps
Paul
 
T

Terry Liu [MSFT]

Hi Paul,

Thank you for your add in!

Best regards,

Terry Liu
MCSE 2K MCSA MCDBA CCNA
Microsoft Online Support Engineer

Get Secure! - <www.microsoft.com/security>
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top