RPC Server Unavailable / unable to access resources

[Greg Saunders]

We have an NT4.0 domain with 1 PDC and a couple of BDC's on other subnets.
We have several Windows 2000 member servers.
One of these member servers is a Terminal Server which happens to be the
one experiencing a couple of problems.

The main problem deals with not being able to access resources such as
mapping printers or drives to another Windows 2000 server.

Basically on a fresh boot all is well. Everything may be fine for several
days and then all of a sudden I will get a call about the Windows 2000
Terminal Server not mapping drives or printers to a serverX where serverX
is one of several Windows 2000 servers.

I will get errors like this in the event log:

Event ID: 1114
Date: 10/10/2005
Time: 12:44:36 PM
Description:
Could not add printer connection to printer (\\GJHNAS\GJHSRVHP4000N), for
user (GJHSMS). Error condition is: (The RPC server is unavailable.
).

And then shortly thereafter we start seeing:

Event ID: 1114
Date: 10/10/2005
Time: 1:28:29 PM
Description:
Could not add printer connection to printer (\\GJHNAS\GJHESTHP4000N), for
user (ScottS). Error condition is: (The printer name is invalid.
).


I have also found another interesting piece of information.

Normally we map our drives using \\servername1\share and in this case this
is how it is failing. However if I do the following
\\servername.domain.com\share it works. We never access anything using
this method, but it is strange that it will work this way, but not the
other.

This 2000 TS Server currently cannot access \\servername1\share, but can
get to it via \\servername1.domain.com\share. I am not certain why the one
would work, but not the other since it should all resolve to the same
place.

The TS 2000 Server and the other servers that it periodically does this
with are all on the same subnet and switch. The only server that EVER has
a problem getting to another server is the TS 2000 Server and a simple
reboot will clear it up.


So... how does one get it to re-establish communications without
rebooting. All other servers in this last example can contact the one in
the error, and the GJHNAS server can access a printer and mapping
resources back on the TS 2000 server. It seems only the TS 2000 server
cannot access a resource to the GJHNAS server.

Thanks for your help and time.

 

[Greg Saunders]

We have an NT4.0 domain with 1 PDC and a couple of BDC's on other subnets.
We have several Windows 2000 member servers.
One of these member servers is a Terminal Server which happens to be the
one experiencing a couple of problems.

The main problem deals with not being able to access resources such as
mapping printers or drives to another Windows 2000 server.

Basically on a fresh boot all is well. Everything may be fine for several
days and then all of a sudden I will get a call about the Windows 2000
Terminal Server not mapping drives or printers to a serverX where serverX
is one of several Windows 2000 servers.

I will get errors like this in the event log:

Event ID: 1114
Date: 10/10/2005
Time: 12:44:36 PM
Description:
Could not add printer connection to printer (\\GJHNAS\GJHSRVHP4000N), for
user (GJHSMS). Error condition is: (The RPC server is unavailable.
).

And then shortly thereafter we start seeing:

Event ID: 1114
Date: 10/10/2005
Time: 1:28:29 PM
Description:
Could not add printer connection to printer (\\GJHNAS\GJHESTHP4000N), for
user (ScottS). Error condition is: (The printer name is invalid.
).


I have also found another interesting piece of information.

Normally we map our drives using \\servername1\share and in this case this
is how it is failing. However if I do the following
\\servername.domain.com\share it works. We never access anything using
this method, but it is strange that it will work this way, but not the
other.

This 2000 TS Server currently cannot access \\servername1\share, but can
get to it via \\servername1.domain.com\share. I am not certain why the one
would work, but not the other since it should all resolve to the same
place.

The TS 2000 Server and the other servers that it periodically does this
with are all on the same subnet and switch. The only server that EVER has
a problem getting to another server is the TS 2000 Server and a simple

Now there is someone out there that must have some experience with this!
When I can't get to a resource via the \\servername\share which uses
WINS/NETBIOS even though I can ping the server and all other servers can
see it AND a simple reboot of the server that can't get to the resource
fixes it... is there a way to get it communicating again WITHOUT having to
reboot. Ultimately I want it fixed, but for now I would settle for a
temporary fix allowing me to get it reset and communicating without
rebooting.

Also remember I can get to the remote resource via \\servername.domain.com
\share, but that is relying on DNS and not WINS.

Depsarate for assistance.

Thank you.