Problems adding a new computer to existing network

  • Thread starter Thread starter Guest
  • Start date Start date
Chuck said:
David,

Let's start by finding what the status of the RPC Server is. In a command
window, enter "sc query rpcss". What do you get for State?
Click to expand...

Chuck:

The "sc query rpcss" command generates the following result:

TYPE: 20 WIN32_SHARE_PROCESS
STATE: 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE: 0 (0X0)
SERVICE_EXIT_CODE:0 (0X0)
CHECKPOINT: 0X0
WAIT_HINT:0X0
 
Chuck:

The "sc query rpcss" command generates the following result:

TYPE: 20 WIN32_SHARE_PROCESS
STATE: 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE: 0 (0X0)
SERVICE_EXIT_CODE:0 (0X0)
CHECKPOINT: 0X0
WAIT_HINT:0X0
Click to expand...

David,

Good. We got that out of the way. Knowing that RPC is running means we don't
have to try to make it run.

So what is our symptom?

I went to the link that you provided, and first ran the "netsh winsock reset
catalog". I got the following message:

"WARNING: Could not obtain host information from machine: [Computer]. Some
commands may not be available. The RPC server is unavailable.
Successfully reset the Winsock Catalog.
You must restart the machine in order to complete the reset."

When I restarted the machine, nothing had changed.

Then I ran the program "WinsockxpFix" which is linked on that page, and
again, no luck.

Then I tried to reset TC/IP with the command "netsh int ip reset
c:\resetlog.txt", and again got the message :"WARNING: Could not obtain host
information from machine: [Computer]. Some commands may not be available.
The RPC server is unavailable.", although it did generate the file
"resetlog.txt"; however, the problem still remains.

Finally, I reinstalled the network adapters. Again, no luck.

So, you tried WinsockXPFix and "netsh winsock reset catalog". There are also
LSP-Fix and WinsockFix. It's a slim chance, but I have seen others here try
each one, and only the last one fixes the problem. Try the other two please.

If no results then, we'll start with more general repairs.
 
Chuck:

The "sc query rpcss" command generates the following result:

TYPE: 20 WIN32_SHARE_PROCESS
STATE: 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE: 0 (0X0)
SERVICE_EXIT_CODE:0 (0X0)
CHECKPOINT: 0X0
WAIT_HINT:0X0
Click to expand...

David,

Good. We got that out of the way. Knowing that RPC is running means we don't
have to try to make it run.

So what is our symptom? You earlier posted:
I went to the link that you provided, and first ran the "netsh winsock reset
catalog". I got the following message:
Click to expand...
"WARNING: Could not obtain host information from machine: [Computer]. Some
commands may not be available. The RPC server is unavailable.
Successfully reset the Winsock Catalog.
You must restart the machine in order to complete the reset."
Click to expand...
When I restarted the machine, nothing had changed.
Click to expand...
Then I ran the program "WinsockxpFix" which is linked on that page, and
again, no luck.
Click to expand...
Then I tried to reset TC/IP with the command "netsh int ip reset
c:\resetlog.txt", and again got the message :"WARNING: Could not obtain host
information from machine: [Computer]. Some commands may not be available.
The RPC server is unavailable.", although it did generate the file
"resetlog.txt"; however, the problem still remains.
Click to expand...
Finally, I reinstalled the network adapters. Again, no luck.
Click to expand...

So, you tried WinsockXPFix and "netsh winsock reset catalog". There are also
LSP-Fix and WinsockFix. It's a slim chance, but I have seen others here try
each one, and only the last one fixes the problem. Try the other two please.

If no results then, we'll start with more general repairs.
 
:

So, you tried WinsockXPFix and "netsh winsock reset catalog". There are also
LSP-Fix and WinsockFix. It's a slim chance, but I have seen others here try
each one, and only the last one fixes the problem. Try the other two please.

If no results then, we'll start with more general repairs.
Click to expand...

OK, ran LSPfix and Winsockfix without success.

David
 
Back
Top