Network authetication for incomming connection problems

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

Guest

I am currently having a problem with login authetication for some incoming connection. Please bear with my description of our setup. I have this posted under the RAS newsgroup but don't seem to be getting any replies. Plus this seems more like an authetication problem than a RAS problem. But anyways, I'd appreciate any suggestions or help that you may be able to provide.

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 (incomming connections) using Netbeui. This process is automated with custom built software. The Server is using Win NT Server 4.0, while the workstations are about to be 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 (for software reasons). 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 (and with the way things are run we can't do that anyways).

Thanks for any help you might be able to provide.

Ray
 
If the Windows 2000 Pro machine is joined to an NT4.0 domain, you will need
to join a workgroup, change the name, and then rejoin the domain - see:

http://support.microsoft.com/default.aspx?scid=kb;en-us;244478

Also, check to see if the domain admins group is a member of the local
administrators group.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

Æon Flux said:
I am currently having a problem with login authetication for some incoming
Click to expand...
connection. Please bear with my description of our setup. I have this
posted under the RAS newsgroup but don't seem to be getting any replies.
Plus this seems more like an authetication problem than a RAS problem. But
anyways, I'd appreciate any suggestions or help that you may be able to
provide.
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 (incomming connections) using Netbeui. This process is automated
with custom built software. The Server is using Win NT Server 4.0, while
the workstations are about to be 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 (for software reasons). 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 (and with the way things
are run we can't do that anyways).
 
Thanks.

I really appreciate your reply. We got things working now. things are just confusing cause this is the most backwards network that I've ever had the misfortune of dealing with, lol. But it does work.

Thanks again.

Ray
 
Back
Top