dutch686
asked on
No logon servers are available
I am part of a large project involving transferring large amounts of data from a legacy network to an new network. Each legacy server has a set of groups added to its various security groups to allow reachback from the new network to the legacy network. I just got finished working with a legacy system administrator adding these groups to 5 different servers. All were setup the same way. One server is denying access to the accounts contained in the security group. The message is Access Denied, there are no logon servers available. I get this when I try to access the server with \\server\sharename. I am really stumped by this. The other servers associated with the same domain controller allow access using the same method. Can anybody throw out some possiblities to look for?
Our hardware engineers told me that the switches aren't smart enough to generate messages like that so they think that the request for access is making it to the server. I think they are correct, but if not please tell me.
Oh, most of the data is being moved from an NT 4 NTFS network to a W2K NTFS network.
Our hardware engineers told me that the switches aren't smart enough to generate messages like that so they think that the request for access is making it to the server. I think they are correct, but if not please tell me.
Oh, most of the data is being moved from an NT 4 NTFS network to a W2K NTFS network.
ASKER
This is a domain account which I should have pointed out. To add the security groups from the new network I am using newdomain\adminaccountname
net use \\w2kserver\ipc$ /adminaccountname:newdomai
net use \\w2kserver\ipc$ /adminaccountname:newdomai
no...
net use \\w2kserver\ipc$ /user:newdomain\adminaccou
You can place the password there at the end- or wait (hit enter) and it will prompt you...
net use \\w2kserver\ipc$ /user:newdomain\adminaccou
You can place the password there at the end- or wait (hit enter) and it will prompt you...
ASKER
Thank you by the way for making your suggestions.
Returned error is System 1311 has occured. There are no logon servers to service your request.
This network is setup with a one way trust so that the new network can reachback to the legacy servers, but the legacy user cannot access the new network. Trying the net use command from the legacy side would not work.
Returned error is System 1311 has occured. There are no logon servers to service your request.
This network is setup with a one way trust so that the new network can reachback to the legacy servers, but the legacy user cannot access the new network. Trying the net use command from the legacy side would not work.
Now I'm confused...the above command would be run from the nt4 server-side...connecting to the 2k box.
If there's no trust, then you'd have to initiate it in the opposite direction, correct?
If there's no trust, then you'd have to initiate it in the opposite direction, correct?
ASKER
Oh man sorry for the confusion. I used the command from the new network which is w2k to connect to the legacy network which is nt 4. If I get the wording correct the legacy network is trusted by the w2k network. The w2k network is not trusted by the nt4 network. In simple terms, I can reach back to the nt4 network for data, but the nt4 network cannot reach the w2k network.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It is a member server, and I just reran the command. Came back with password or user name is invalid for \\server\ipc$
I entered the password at the next prompt, and received Logon failure: unknown user name or bad password.
I entered the password at the next prompt, and received Logon failure: unknown user name or bad password.
So, given nt4server is the member server's name...the above command (server specified twice) is invalid?
Hmmm...can you browse to it? Can you see it in network neighborhood?
Hmmm...can you browse to it? Can you see it in network neighborhood?
You need to install the latest service packs. There are several issues, similar to the ones below, where this is a bug in the upgrade process, sometimes you have to set a registry entry, or change it, others, an SP upgrade solves it.
http://labmice.techtarget.com/windows2000/install/winntupgrd.htm
http://support.microsoft.com/?kbid=243997
http://labmice.techtarget.com/windows2000/install/winntupgrd.htm
http://support.microsoft.com/?kbid=243997
What account are you using to connect?
If it's an administrative account - is it local or a domain account?
Try Start->Run->CMD
NET USE \\W2kServer\ipc$ /user:administrator password
if it's a domain account then use:
NET USE \\W2kServer\ipc$ /user:domain\administrator
Where domain is the domain,
Administrator is the administrator account
and password is the password...
if that connects successfully, then net use * \\W2kServer\Share should work fine...
On the opposite - try this from the W2k system...
NET USE \\NT4Server\ipc$ /user:administrator password
if it's a domain account then use:
NET USE \\NT4Server\ipc$ /user:domain\administrator
Where domain is the domain,
Administrator is the administrator account
and password is the password...
if that connects successfully, then net use * \\NT4Server\Share should work fine...