Incomming connections on 2000 pro problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm fairly new to RAS, and haven't had a lot of knowledge or training in it so ... This is probably an easy fix that I'm just can't see. But either way, any help would be appreciated.

Work has a different set up for RAS than most documented sources. The way it's set up is the main office has a server set up that dials into a lot of the smaller branches collecting text files. Everything is done through modems using Netbeui. This process is automated with custom built software. The Server is using Win NT Server 4.0, while the workstations are being replaced with 2000 professional. I had set up one machine, and the main office connected to it with no problems. However, I need to change the computer name to a number associated with the branch. And this is where the problem lies. Once I change the computer name, the main office can't connect to the PC anymore. the connection drops right away.

When I look at event viewer it says "The user Administrator failed on authetication due to the following reason. The current configuration only supports local accounts". How do I get around this? When I switch the Computer name back, it works fine again. Unfortunetly I can't keep the name with the way the PC is set up as. And I don't have time to reinstall windows on every machine with the correct pc name.

Thanks for the help.

Ray
 
Looks like your credentials are not matching the domain.
You should have the below

Username: local user
Domain: New name of the machine

and its password.

I guess the old domain is being provided to the RRAS Server still from the
client.

--
- Manjari
This posting is provided "AS IS" with no warranties, and confers no rights.
Æon Flux said:
I'm fairly new to RAS, and haven't had a lot of knowledge or training in
Click to expand...
it so ... This is probably an easy fix that I'm just can't see. But either
way, any help would be appreciated.
Work has a different set up for RAS than most documented sources. The way
Click to expand...
it's set up is the main office has a server set up that dials into a lot of
the smaller branches collecting text files. Everything is done through
modems using Netbeui. This process is automated with custom built software.
The Server is using Win NT Server 4.0, while the workstations are being
replaced with 2000 professional. I had set up one machine, and the main
office connected to it with no problems. However, I need to change the
computer name to a number associated with the branch. And this is where the
problem lies. Once I change the computer name, the main office can't
connect to the PC anymore. the connection drops right away.
When I look at event viewer it says "The user Administrator failed on
Click to expand...
authetication due to the following reason. The current configuration only
supports local accounts". How do I get around this? When I switch the
Computer name back, it works fine again. Unfortunetly I can't keep the name
with the way the PC is set up as. And I don't have time to reinstall
windows on every machine with the correct pc name.
 
Thanks Manjari for the Reply.

It was the credentials, and we have it working now. Things are rather confusing with this network due to it's backwards design, but it does work.

Thanks again for the help.

Ray
 
Back
Top