NT 4.0 to Win2k Pro RAS problem

[Graeme Byrne]

I have set up an incoming connection item on my Win2k box
at work. Its TCP/IP properties are

Allow callers to access my local area network - Yes
Specify TCP/IP Addresses (range specified)
Allow calling computer to specify its own IP address - Yes

My home machine is running NT 4.0 (SP 6a) is set up to
dial in specifying its own IP.

I get connected can ping some machines on the work
intranet (unix boxes) but cannot ping any windows machines
on the intranet or extrenal addresses. Also browsing the
internet is a problem.

When the work machine was NT4 everything worked fine.

The only clue as to the problem is the following Event
message.

Event Type: Warning
Event Source: RemoteAccess
Event Category: None
Event ID: 20187
Date: 7/11/2001
Time: 10:19:18 AM
User: N/A
Computer: BYRNE
Description:
The user \g.byrne failed an authentication attempt due to
the following reason: The current configuration only
supports local user accounts.

Any help appreciated.

[John Spradlin]

IS the RAS server a domain controller, member server or a standalone?
"Graeme Byrne" <g.b...@bendigo.latrobe.edu.au> wrote in message
news:48a601c109d2$b8a09b80$19ef2ecf@tkmsftngxa01...

[Graeme Byrne]

The RAS server is a standalone.

>.
>

[Graeme Byrne]

The problem is now solved. My home machine used to be my
work machine and the NIC was still physically present and
setup. Uninsatlling the NIC on the NT 4.0 home machine
solved the problem. I had changed the NIC IP on the home
machine to one that the RAS server allocates. This must
have been sending conflicting info to the network causing
the problems.

Thanks

>.
>