Routing and Remote Access - Error 678

G

Guest

Servers: NT 4, 2000, 20003
Clients: 2000, XP

Hi All!

We recently upgraded our domain to AD by adding a new 2003 domain
controller, and removing the old PDC. The domain is currently in mixed mode,
with several old NT 4 DCs still online.

One of the (NT 4) DCs also serves as RAS, and we would like to replace it
next.

We installed 2003, SP1 and Routing and Remote Access (dial-up) on a new
machine, and attached one USR modem, but for some reason it is not accepting
any connections from clients. The error is

Dialing 555.555.5555 …
Error 678: There was no answer.

This connection works with the existing NT 4 RAS, and the modem and phone
line are fine.

Thanks in advance for your help!

John
 
B

Bill Grant

The error message is pretty specific. The server isn't detecting any
attempt to connect. I would check the RRAS config. It is worth noting that
the remote access policies in W2k3 are very different from NT4. Try setting
the default policy to enable and setting the client account to use remote
access policy rather than dialup access permission.
 

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

Similar Threads

Error 678 when Server at Logon Screen 2
Cannot Dial into 2000 or 2003 servers on 2003 Interim AD Domain 1
Migrating RAS on from an NT4 domain to 2003 AD 2
Connectivity stops between servers when RAS is started 6
RAS in NT but User in AD 2
RAS, Lan Routing, and Demand-dial routing. 1
Routing and remote access - allow rdp only 4
DUN Error 777 1

Top