RPC Failed

Hi

I have a LAN to LAN VPN setup between our two offices and everytime I try to
access my remote LAN, using the Windows Explorer interface or navigating to
the Start run interface and type the remote IP address or DNS name I am
receiving the error "Remote Procedure called failed, \\192.168.x.x is not
accessible". Why am I constantly receiving this error and what can I do to
get rid of it. I am trying to access a Windows 2000 Server on the remote
LAN.

I have tried stopping and restarting the RPC service. What else can I do.

Thanks

Is the RPC service stopped on the computer? If so, I know there are some
viruses that cause RPC to crash (gaobot being the one we had here).




"Hot Gal" <(E-Mail Removed)> wrote in message
news:O$(E-Mail Removed)...
> Hi
>
> I have a LAN to LAN VPN setup between our two offices and everytime I try
to
> access my remote LAN, using the Windows Explorer interface or navigating
to
> the Start run interface and type the remote IP address or DNS name I am
> receiving the error "Remote Procedure called failed, \\192.168.x.x is not
> accessible". Why am I constantly receiving this error and what can I do to
> get rid of it. I am trying to access a Windows 2000 Server on the remote
> LAN.
>
> I have tried stopping and restarting the RPC service. What else can I do.
>
> Thanks
>
>
>

the rpc service is running


"Jonathan French" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Is the RPC service stopped on the computer? If so, I know there are some
> viruses that cause RPC to crash (gaobot being the one we had here).
>
>
>
>
> "Hot Gal" <(E-Mail Removed)> wrote in message
> news:O$(E-Mail Removed)...
> > Hi
> >
> > I have a LAN to LAN VPN setup between our two offices and everytime I
try
> to
> > access my remote LAN, using the Windows Explorer interface or navigating
> to
> > the Start run interface and type the remote IP address or DNS name I am
> > receiving the error "Remote Procedure called failed, \\192.168.x.x is
not
> > accessible". Why am I constantly receiving this error and what can I do
to
> > get rid of it. I am trying to access a Windows 2000 Server on the remote
> > LAN.
> >
> > I have tried stopping and restarting the RPC service. What else can I
do.
> >
> > Thanks
> >
> >
> >
>
>

There are several different problems which can arise. The first is
connectivity. Can you ping the machine by IP? The next is name resolution.
Can you ping it by name?

If you can ping by name, try net view \\servername . If this works, try
net use \\servername\sharename . If it doesn't like your credentials, try
the /user option in net use .

"Hot Gal" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> the rpc service is running
>
>
> "Jonathan French" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > Is the RPC service stopped on the computer? If so, I know there are
some
> > viruses that cause RPC to crash (gaobot being the one we had here).
> >
> >
> >
> >
> > "Hot Gal" <(E-Mail Removed)> wrote in message
> > news:O$(E-Mail Removed)...
> > > Hi
> > >
> > > I have a LAN to LAN VPN setup between our two offices and everytime I
> try
> > to
> > > access my remote LAN, using the Windows Explorer interface or
navigating
> > to
> > > the Start run interface and type the remote IP address or DNS name I
am
> > > receiving the error "Remote Procedure called failed, \\192.168.x.x is
> not
> > > accessible". Why am I constantly receiving this error and what can I
do
> to
> > > get rid of it. I am trying to access a Windows 2000 Server on the
remote
> > > LAN.
> > >
> > > I have tried stopping and restarting the RPC service. What else can I
> do.
> > >
> > > Thanks
> > >
> > >
> > >
> >
> >
>
>

I can post by name and IP successfully.
thanks

"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
> There are several different problems which can arise. The first is
> connectivity. Can you ping the machine by IP? The next is name resolution.
> Can you ping it by name?
>
> If you can ping by name, try net view \\servername . If this works,
try
> net use \\servername\sharename . If it doesn't like your credentials, try
> the /user option in net use .
>
> "Hot Gal" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > the rpc service is running
> >
> >
> > "Jonathan French" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> > > Is the RPC service stopped on the computer? If so, I know there are
> some
> > > viruses that cause RPC to crash (gaobot being the one we had here).
> > >
> > >
> > >
> > >
> > > "Hot Gal" <(E-Mail Removed)> wrote in message
> > > news:O$(E-Mail Removed)...
> > > > Hi
> > > >
> > > > I have a LAN to LAN VPN setup between our two offices and everytime
I
> > try
> > > to
> > > > access my remote LAN, using the Windows Explorer interface or
> navigating
> > > to
> > > > the Start run interface and type the remote IP address or DNS name I
> am
> > > > receiving the error "Remote Procedure called failed, \\192.168.x.x
is
> > not
> > > > accessible". Why am I constantly receiving this error and what can I
> do
> > to
> > > > get rid of it. I am trying to access a Windows 2000 Server on the
> remote
> > > > LAN.
> > > >
> > > > I have tried stopping and restarting the RPC service. What else can
I
> > do.
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>