RPC failed


G

Guest

I have a very simple network set up where I use a USB PC-link to connect a laptop running Windows 2k Pro and a desktop running Windows XP Home

The XP system can see and access the 2k Pro shares. The 2k Pro system can see but not access the XP system, it gets the error message "XP system is not accessible. The remote procedure call failed."

Each can ping the other with success. Accounts, passwords, and permissions are set up properly on each system

What might be the problem? I would really appreciate any help.
 
Ad

Advertisements

S

Steven L Umbach

Check that the built in XP firewall is disabled as it will block attempts to
shared resources. --- Steve

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

Matthew said:
I have a very simple network set up where I use a USB PC-link to connect a
laptop running Windows 2k Pro and a desktop running Windows XP Home.
The XP system can see and access the 2k Pro shares. The 2k Pro system can
see but not access the XP system, it gets the error message "XP system is
not accessible. The remote procedure call failed."
Each can ping the other with success. Accounts, passwords, and
permissions are set up properly on each system.
 
G

Guest

Thank you for responding!

I tried disabling XP's firewall, but it didn't help. Actually there was one time when this network did work and the following is how it was setup, in retrospect I don't know why it worked. Neither computer had accounts for the other, internet connection sharing and firewall was enabled on XP system's connection to the Internet. The Win2k Pro system was able to use the shared Internet connection and was able to access shares on the XP's system. Then I started setting up passwords on non password accounts and setting each system up with appropriate accounts to enable access from the other computer. Soon after this is when I had the RPC failed problem only from Win2kPro to XP and not the other way around

Therefore, in troubleshooting I systematically backtracked trying to undo changes to get back to the state I was in when the entire system was working. Well, the little backtracking didn't work, so I started taking bigger steps. I restored my XP system to a point before the USB PC link was installed and I unistalled the USB PC link virtual network adapter on the Win2kPro system via device manager. After reinstalling the software on each system and being at a point (unless I missed something) where I was when the network did work, I thought it would work. Well it didn't and I still get the same RPC failed

I'm at a loss....any suggestions????
 
S

Steven Umbach

Well the problem could be on the W2K machine. One the XP machine run ipconfig
/all and net config server to see if those commands run OK. On the W2K machine
run ipconfig /all and net config workstation seeing if they run OK. Check the
ipconfig /all results on both to make sure they are on the same network
address - usually the first three octets of the IP address needs to be the same
assuming the class C network. The subnet masks need to be the same also. Another
thing to try is booting into safemode with networking on first the W2K machine
and then the XP Pro machine if that does not help. Verify network connectivity
in safe mode with networking by using ping before trying share access. If safe
mode works then it could be a conflict with a startup program/service that you
could troubleshoot using msconfig on the XP box that you could also copy to the
\winnt\system32 folder on the W2K box to do the same. Other options include
repairing or reinstalling tcp/ip as shown in links below. Do not rule out a
virus either and do appropriate scans for such.--- Steve

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

Matthew said:
Thank you for responding!

I tried disabling XP's firewall, but it didn't help. Actually there was one
time when this network did work and the following is how it was setup, in
retrospect I don't know why it worked. Neither computer had accounts for the
other, internet connection sharing and firewall was enabled on XP system's
connection to the Internet. The Win2k Pro system was able to use the shared
Internet connection and was able to access shares on the XP's system. Then I
started setting up passwords on non password accounts and setting each system up
with appropriate accounts to enable access from the other computer. Soon after
this is when I had the RPC failed problem only from Win2kPro to XP and not the
other way around.
Therefore, in troubleshooting I systematically backtracked trying to undo
changes to get back to the state I was in when the entire system was working.
Well, the little backtracking didn't work, so I started taking bigger steps. I
restored my XP system to a point before the USB PC link was installed and I
unistalled the USB PC link virtual network adapter on the Win2kPro system via
device manager. After reinstalling the software on each system and being at a
point (unless I missed something) where I was when the network did work, I
thought it would work. Well it didn't and I still get the same RPC failed.
 
G

Guest

I tried all the network commands and pings you mentioned and they all were successful under normal and safe mode booting. My network ips, subnets all are fine.

I did have limited success with Safe mode. If BOTH computers were safe mode booted, I could as before access the W2K system fully from XP system. From the W2K system I could go a step further this time and see not only the XP computer but go one level down to seeing its shares. Upon trying to access files inside the shared folders I got this error: “The specified network name is no longer availableâ€.

I’m not sure if this is unique to Safe Mode (or has any relevance to my overall problem) but while in it, I shared another folder on the XP system, now when I return to the W2K system and tried to access the XP computer I get the “remote procedure call failed†again and am not allowed to see ANY of its shares, including the previously visible. Unsharing this new folder then puts me back to the state of being able to see the XP shares as described in the first paragraph.

I will try reinstalling TCP/IP as suggested as well. I will try the virus scans as well (I know a virus could strike at any time even with protection but both OSes are 2 weeks old after partitions were deleted and fresh OSes installed). I may just “delpart.exe†my W2K system and start over since I don’t have any data on it yet and my partitioning was not well thought out the first time.

What do think of the new error I got? and, respectfully and out of curiosity, what is the likelihood of a virus causing these types of network problems? --Matt
 
S

Steven Umbach

What happens if you boot just the XP machine into safe mode with networking? Can
the W2K machine then at least see the shares? If it can see them but still gets
the name is no longer available message try to access the shares via unc using
the ip address of the XP machine. In the run box enter
\\xxx.xxx.xxx.xxx\sharename where xxx.xxx.xxx.xxx would be the ip address of the
XP machine. If that works then you have a name resolution problem, if not you
have a deeper problem. Always check Event Viewer for any error events when you
are having problems with a computer. Also try running netdiag on at leas the W2K
machine - I don't know if it is available for XP home. Netdiag will run a bunch
of tests and failed tests can help pinpoint the problem. Look on the install
disk for each operating system and in the tools/support folder run the setup
program there which will install utilities including netdiag. Check the
properties of your network adapters and if you see that they are set to "auto"
for network speed try setting them to the same value such as 100.
http://support.microsoft.com/default.aspx?scid=kb;en-us;321708

I don't necessarily think you have a virus problem, but it is always a good idea
to scan for such any time you are having problems. If you are using a firewall,
an antivirus program that is up to date and scans all emails, and are keeping
current with all of your critical updates at Windows Update, then your chance of
having a virus drops dramatically. Another concern is parasites and other
malware from internet browsing that are not classified viruses or worms but can
cause system problems. See the link below and scan your computer with something
like AdAware or SpyBot if you have never done such.
http://www.mvps.org/winhelp2002/unwanted.htm

I have seen network problems also occur from flaky nics or flaky drivers. Check
the manufacture's websites for your nics and see if you are using the latest
drivers. You might also try a new nic card. I have had good luck with D-Link pci
nics and they are cheap. Sometimes I just throw my hands up in the air and
reinstall if nothing else works. The good news is that an upgrade install
usually fixes most problems and leaves data and applications in place, however
first a service pack and then all critical updates need to be installed [no more
than five at a time] after an upgrade install and the computer should not be
connected to the internet unless a firewall is protecting it such as a cable/dsl
nat router or a personal firewall. An upgrade install is done by running the
install disk while you are running the operating system and selecting "upgrade"
when asked for installation type. --- Steve

Matthew said:
I tried all the network commands and pings you mentioned and they all were
successful under normal and safe mode booting. My network ips, subnets all are
fine.
I did have limited success with Safe mode. If BOTH computers were safe mode
booted, I could as before access the W2K system fully from XP system. From the
W2K system I could go a step further this time and see not only the XP computer
but go one level down to seeing its shares. Upon trying to access files inside
the shared folders I got this error: "The specified network name is no longer
available".
I'm not sure if this is unique to Safe Mode (or has any relevance to my
overall problem) but while in it, I shared another folder on the XP system, now
when I return to the W2K system and tried to access the XP computer I get the
"remote procedure call failed" again and am not allowed to see ANY of its
shares, including the previously visible. Unsharing this new folder then puts
me back to the state of being able to see the XP shares as described in the
first paragraph.
I will try reinstalling TCP/IP as suggested as well. I will try the virus
scans as well (I know a virus could strike at any time even with protection but
both OSes are 2 weeks old after partitions were deleted and fresh OSes
installed). I may just "delpart.exe" my W2K system and start over since I don't
have any data on it yet and my partitioning was not well thought out the first
time.
What do think of the new error I got? and, respectfully and out of curiosity,
what is the likelihood of a virus causing these types of network
roblems? --Matt
 
Ad

Advertisements

G

Guest

I ran a full virus scan on my XP system, actually I first updated the virus definitions, and the system was clean. I reinstalled TCP/IP on XP system. I completely repartitioned, reformatted, and reinstalled W2K on the other system. Still the same RPC failed. I booted only the XP machine into safe mode and then booted the W2K system in normal mode as you suggested. I could see the shares on XP from W2K, but still get the name is no longer available when attempting access inside the shares. Substituting the XP ip address did not work in accessing the shares. It seemed pretty obvious it was not a name resolution problem, because after I had typed in the XP ip address in the “Run†box but before the actual share name was typed, the system recognized the address and automatically gave me a total list of shares on XP in the drop down box as if I had requested the information previously.

I did run netdiag on the W2K (couldn’t locate anything for XP home) and checked out the Event Viewer. I am not 100% sure of how to interpret the results with enough confidence to make an informed change of anything on my system, so I include the results later in this reply. The results came after booting XP system in safe mode and then booting W2K in normal mode

I also checked the network speed of my adapters, the only configurable option I saw for the adapters was to switch the device from High Speed Mode to Compatible Mode. This did not solve the problem

Overall, if I can ping with these virtual network adapters and their associated drivers and USB PC-link cables does that exonerate them? If not I really think I’m going to just return the hardware and try something different

Anyways here is the output from 2 Event Viewer errors I found on the W2K system after booting….
Event Type: Erro
Event Source: Serve
Event Category: Non
Event ID: 250
Date: 19-Feb-0
Time: 19:25:2
User: N/
Computer: USHI
Description
The server could not bind to the transport \Device\NetBT_Tcpip_{68F91CCE-97ED-4687-BF9D-4D49AFEEC466} because another computer on the network has the same name. The server could not start.
Data
0000: 34 00 00 00 4...


Event Type: Erro
Event Source: Serve
Event Category: Non
Event ID: 250
Date: 19-Feb-0
Time: 19:25:2
User: N/
Computer: USHI
Description
The server could not bind to the transport \Device\NetbiosSmb because another computer on the network has the same name. The server could not start.
Data
0000: 34 00 00 00 4...

And here is the output of netdiag from the W2K system…

Computer Name: USHI
DNS Host Name: ushi
System info : Windows 2000 Professional (Build 2195
Processor : x86 Family 5 Model 8 Stepping 1, GenuineInte
List of installed hotfixes :
Q14722

Netcard queries test . . . . . . . : Passe
[WARNING] The net card 'USB Virtual Network Adapter #2' may not be working because it has not received any packets

Per interface results
Adapter : Local Area Connectio
Netcard queries test . . . : Passe

Host Name. . . . . . . . . : ushi
IP Address . . . . . . . . : 192.168.0.
Subnet Mask. . . . . . . . : 255.255.255.
Default Gateway. . . . . . :
Dns Servers. . . . . . . . :

AutoConfiguration results. . . . . . : Passe

Default gateway test . . . : Skippe
[WARNING] No gateways defined for this adapter

NetBT name test. . . . . . : Passe
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing
No remote names have been found

WINS service test. . . . . : Skippe
There are no WINS servers configured for this interface

Adapter : IPX Internal Interfac

Netcard queries test . . . : Passe
Ipx configratio
Network Number . . . . : 0000000
Node . . . . . . . . . : 00000000000
Frame type . . . . . . : Ethernet I

Adapter : IpxLoopbackAdapte

Netcard queries test . . . : Passe
Ipx configration
Network Number . . . . : 1234cdef
Node . . . . . . . . . : 000000000002
Frame type . . . . . . : 802.2

Adapter : NDISWANIPX

Netcard queries test . . . : Passed
Ipx configration
Network Number . . . . : 00000000
Node . . . . . . . . . : d60120524153
Frame type . . . . . . : Ethernet II
Global results:

Domain membership test . . . . . . : Passed
Dns domain name is not specified.
Dns forest name is not specified.

NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{68F91CCE-97ED-4687-BF9D-4D49AFEEC466}
1 NetBt transport currently configured.

Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Failed

[FATAL] NO GATEWAYS ARE REACHABLE.
You have no connectivity to other network segments.
If you configured the IP protocol manually then
you need to add at least one valid gateway.

NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed

DNS test . . . . . . . . . . . . . : Failed
[FATAL] Cannot get the DNS Adapter Information from the registry, error 0x267c DNS_ERROR_NO_DNS_SERVERS

Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{68F91CCE-97ED-4687-BF9D-4D49AFEEC466}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{68F91CCE-97ED-4687-BF9D-4D49AFEEC466}
The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Skipped
DC list test . . . . . . . . . . . : Skipped
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Skipped
LDAP test. . . . . . . . . . . . . : Skipped
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
Netware configuration
You are not logged in to your preferred server .
Netware User Name. . . . . . . :
Netware Server Name. . . . . . :
Netware Tree Name. . . . . . . :
Netware Workstation Context. . :
IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.

The command completed successfully

I could surmise a few things from the errors/results but I’m sure you would know a lot better.---Matt
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top