VPN doesn't provide "naming" and "browsing". Those are done with a
combination of WINS and enabling "Netbios over TCP/IP" on all involved
machines. However to see machines in Net'Hood you also must have the
workgroup the same as the Domain name on your client machine.
Also keep in mind the the credentials you used to create the VPN Connection
do only that,...they create the VPN Connection. They do not log you into the
domain. They also do not log your machie into the domain assuming that the
machine is even a domain member to start with.
Bottom line,...When using VPN,...don't expect the use Network Neighborhood
and don't expect your machine to behave just like it was on the LAN locally.
Another thing to consider,...if you want to actually log into the domain
then when you are still sitting at the Crtl-Alt-Del prompt, you must check
the box that mentions logging in using a particular dial-up connection.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Hank" <(E-Mail Removed)> wrote in message
news:8d4d01c432c9$18544e10$(E-Mail Removed)...
> I am attemting to attach to my office network from a
> remote site via a VPN. The office is networked via a SOHO
> Watchguard router. I have successfullly established the
> VPN tunnel from the remote site to the SOHO box using
> Watchguard MUVPN remote user VPN software and am able to
> ping the server sucessfully. I am not able to see the
> shared resources of the server via Windows explorer from
> the remote site. Any input as to where I look for my
> errors. thank you
Similar Threads
Linear Mode
