RPC Locator needed for PPTP-VPN for reliable UNC resource access?

[Guest JCB]

I use a WinXPSP2 remote host to connect to my home office via a PPTP-VPN

connection to a Win2003SP2 RRAS server that is behind my firewall. Both the

server and remote host use a virtual WAN adapter, configured via the RRAS

service, instead of separate physical adapters.

 

Occasionally, once the connection is established, I cannot reliably access

network resources via a UNC path (\\server\share). I receive a network path

error. However, if I terminal in to the target server (also by name, not IP)

via mstsc.exe (RDP 5.2), I can connect just fine.

 

Must the RPC Locator service be running on the remote host to ensure UNC

access reliability?

 

 

 

--

JCB\1059

[Guest Robert L [MVP - Networking]]

Re: RPC Locator needed for PPTP-VPN for reliable UNC resource access?

 

It could be the name resolution issue. This troubleshooting may help,

 

Name resolution on VPNThat reason is that VPN server is a Virtual Multihomed Server. The resolution is to disable NetBIOS Over TCP/IP and DNS register on all interfaces including ...

http://www.chicagotech.net/nameresolutionpnvpn.htm

 

 

Bob Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net

How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com

"JCB" <JCB@discussions.microsoft.com> wrote in message news:2B58969C-4B62-45F9-9448-491BD4C7C10F@microsoft.com...

I use a WinXPSP2 remote host to connect to my home office via a PPTP-VPN

connection to a Win2003SP2 RRAS server that is behind my firewall. Both the

server and remote host use a virtual WAN adapter, configured via the RRAS

service, instead of separate physical adapters.

 

Occasionally, once the connection is established, I cannot reliably access

network resources via a UNC path (\\server\share). I receive a network path

error. However, if I terminal in to the target server (also by name, not IP)

via mstsc.exe (RDP 5.2), I can connect just fine.

 

Must the RPC Locator service be running on the remote host to ensure UNC

access reliability?

 

 

 

--

JCB\1059

[Guest JCB]

Re: RPC Locator needed for PPTP-VPN for reliable UNC resource acce

 

Re: RPC Locator needed for PPTP-VPN for reliable UNC resource acce

 

Thank you.

 

I have NetBIOS over TCP/IP disabled on all network adapters already. The

problem is intermittent anyway...any further thoughts?

--

JCB\1059

 

 

"Robert L [MVP - Networking]" wrote:

> It could be the name resolution issue. This troubleshooting may help,

>

> Name resolution on VPNThat reason is that VPN server is a Virtual Multihomed Server. The resolution is to disable NetBIOS Over TCP/IP and DNS register on all interfaces including ...

> http://www.chicagotech.net/nameresolutionpnvpn.htm

>

>

> Bob Lin, MS-MVP, MCSE & CNE

> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net

> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com

> "JCB" <JCB@discussions.microsoft.com> wrote in message news:2B58969C-4B62-45F9-9448-491BD4C7C10F@microsoft.com...

> I use a WinXPSP2 remote host to connect to my home office via a PPTP-VPN

> connection to a Win2003SP2 RRAS server that is behind my firewall. Both the

> server and remote host use a virtual WAN adapter, configured via the RRAS

> service, instead of separate physical adapters.

>

> Occasionally, once the connection is established, I cannot reliably access

> network resources via a UNC path (\\server\share). I receive a network path

> error. However, if I terminal in to the target server (also by name, not IP)

> via mstsc.exe (RDP 5.2), I can connect just fine.

>

> Must the RPC Locator service be running on the remote host to ensure UNC

> access reliability?

>

>

>

> --

> JCB\1059