unable to start RPC

March 19, 2012 at 21:56:48
Specs: Windows XP
How do you enable Window XP RPC
Had W32Blaster.worm and cleaned system, however Internet will not load lack of RPC
Message; no or low connectivity.

See More: unable to start RPC

Report •

#1
March 20, 2012 at 07:13:07
Check in "Services" to ensure the RPC service is set to start automatically.

Services can be found in Administrative Tools.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
March 20, 2012 at 13:40:43
RPC is set to auto
PC will not retrieve an IP

Report •

#3
March 20, 2012 at 14:40:46
I guess I should have asked you what makes you think there's a problem with RPC (Remote Procedure Call)?

Are you getting some sort of error message and if yes, you need to research (ie: google) the error message. If you can't find any help on the error message then you come in here, state what's going on, supply any/all error messages you're getting and tell us what troubleshooting steps you've already taken so we don't waste time duplicating effort.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Related Solutions

#4
March 20, 2012 at 15:18:39
OK, Cleaned up W32Blaster. 1; pc will not connect to the internet. 2; Checked network 3; checked RPC set to auto and started. 5; tried to repair said cant renew IP
6; tools-network diagnostics scan 7; cmd, ipconfig /all, ipconfig /release, ipconfig /renew.
Error message; "error occurred while renewing interface local area connection: The RCP server is unavailable. 8; regedit - Hkey_local_machines\software\microsoft\RPC all looks fine, so dose \currentControlSet\services\rcpss.
cmd nbtstat -n Message " Can't access netbt drive. May not be installed
I also updated there XP w/sp2 to sp3
I also failed to mention if i manually input the IP it will connect to the internet
Not sure where to go from here

Report •

#5
March 21, 2012 at 08:16:34
From the sounds of it, you're having an issue with the TCP/IP stack.

At this point in time I would suggest you uninstall the TCP/IP stack, reboot, then reinstall the TCP/IP stack on the interface.

If that doesn't fix the issue it may be necessary to uninstall the interface from Device Manager, then reboot and reinstall it.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#6
March 21, 2012 at 12:31:52
OK, would the TCP/IP stack be the problem if as i mentioned "if I manually input a static IP address" it will connect to the Internet??
It is when set to auto it will not get an IP address.

Report •

#7
March 21, 2012 at 15:05:02
No, it couldn't be the TCP/IP stack, I threw that in to confuse you. That's what we're here for right, to make things worse, not help.

Sarcasm aside.......

The reason I mentioned the TCP/IP stack is because I suspect that might be the issue based on the the description you provided of what is happening.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#8
March 21, 2012 at 20:20:57
Of cores with sarcasm aside, the question is still unanswered; would imputing a static IP manually still work if the TCP/IP stack was bad?
Any way on the other hand I have reset both "cmd- intsh int and winsock catalog.
This has not solved the problem.
I ran SFC /scannow, it paused at several things, however, I do not have any of the original CD's to insert.

Report •

#9
March 22, 2012 at 07:41:24
What part of "The reason I mentioned the TCP/IP stack is because I suspect that might be the issue based on the the description you provided of what is happening." are you not understanding??????????

Any way on the other hand I have reset both "cmd- intsh int and winsock catalog.

Good for you. However, that's not what I told you to do is it.

This has not solved the problem.

I'm not surprised and I could have told you neither would work which is why I didn't mention doing that.

I ran SFC /scannow, it paused at several things, however, I do not have any of the original CD's to insert.

Again, good for you. However, SFC is not going to fix the issue. You'll notice I didn't mention running SFC in any of my responses either. There's a reason for it. That reason being, I know it won't fix your issue.

Now, whether or not you understand my plain English answer to your repeated question about the TCP/IP stack, try doing what I said. I'm going to repeat myself (which I hate) and this is the very last time I'm going to attempt to help you since your obtuseness is frustrating me and I'm finished with you as of completing this response:

1) Uninstall the TCP/IP stack, reboot your computer, reinstall the TCP/IP stack and reboot if necessary. Test DHCP

2) If #1 does not fix the issue, go into Device Manager and uninstall the network interface, reboot and reinstall the interface. After reinstalling it, ensure you have the most recent and up-to-date drivers for the device.

Goodbye.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Ask Question