Windows Server 2003 and simple VPN pass thru

Hi all...

I have just managed to setup a very simple vpn pass thru connection to
a Windows Server 2003 computer in our office. I can connect from home
by the vpn connection I created in Network Connections. Once the
connection has been made and I have logged on etc, I am able to open a
remote desktop connection to the server.

However, What I can't seem to do, is use Windows Explorer or the 'My
Network Places' to connect to any of the other servers (even though my
logon has permissions to see them, and can see them when in the
office).

What do I need to do to Windows Server 2003 to enable office internal
network routing?

IE: I'm sat at home, connected via vpn connection to vpn server
192.168.1.10 (office local network ip) and want to get files from
office file server 192.168.1.20 (again, office local network ip).

Thanks

It probably isn't a routing problem. If you can ping 192.168.1.20 from
your remote client, routing is working. Name resolution is a bit harder, and
browsing (which is what you see in "My network Places") even harder.

On a LAN, name resolution and browsing work using broadcasts. Routers
and remote access servers usually block broadcasts, so this method fails.

Have you tried enabling the option to allow broadcasts in the RRAS
console? This was added in Server 2003 and might solve your problem.

"Karl Rhodes" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Hi all...
>
> I have just managed to setup a very simple vpn pass thru connection to
> a Windows Server 2003 computer in our office. I can connect from home
> by the vpn connection I created in Network Connections. Once the
> connection has been made and I have logged on etc, I am able to open a
> remote desktop connection to the server.
>
> However, What I can't seem to do, is use Windows Explorer or the 'My
> Network Places' to connect to any of the other servers (even though my
> logon has permissions to see them, and can see them when in the
> office).
>
> What do I need to do to Windows Server 2003 to enable office internal
> network routing?
>
> IE: I'm sat at home, connected via vpn connection to vpn server
> 192.168.1.10 (office local network ip) and want to get files from
> office file server 192.168.1.20 (again, office local network ip).
>
> Thanks
>

Browsing over the VPN is not easy. It is better to setup WINS server. This search result may help,

Browsing over VPN Q: Browsing over VPN So far, so good. Now I am connected to the VPN and can surf at the same time. So now, how do I go about browsing my remote network? ...
www.chicagotech.net/Q&A/vpn27.htm


vpnbrowsing issues Browsing Over VPN Issues. Can access to the mail system but not share How to browse via incoming connection Unable to access the resources on the network ...
www.chicagotech.net/vpnbrowsingissues.htm


Troubleshooting Computer Browsing over WAN Troubleshooting Computer Browsing over WAN. Situation: You just connected two offices located in the different cities. There is one domain controller with ...
http://www.chicagotech.net/troublesh...rowsingwan.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
"Karl Rhodes" <(E-Mail Removed)> wrote in message news:(E-Mail Removed) oups.com...
Hi all...

I have just managed to setup a very simple vpn pass thru connection to
a Windows Server 2003 computer in our office. I can connect from home
by the vpn connection I created in Network Connections. Once the
connection has been made and I have logged on etc, I am able to open a
remote desktop connection to the server.

However, What I can't seem to do, is use Windows Explorer or the 'My
Network Places' to connect to any of the other servers (even though my
logon has permissions to see them, and can see them when in the
office).

What do I need to do to Windows Server 2003 to enable office internal
network routing?

IE: I'm sat at home, connected via vpn connection to vpn server
192.168.1.10 (office local network ip) and want to get files from
office file server 192.168.1.20 (again, office local network ip).

Thanks

If name resolution is the problem, would entries in the hosts file fix
this problem?
A cheap fix I know, but if it works...

Karl

Bill Grant wrote:
> It probably isn't a routing problem. If you can ping 192.168.1.20 from
> your remote client, routing is working. Name resolution is a bit harder, and
> browsing (which is what you see in "My network Places") even harder.
>
> On a LAN, name resolution and browsing work using broadcasts. Routers
> and remote access servers usually block broadcasts, so this method fails.
>
> Have you tried enabling the option to allow broadcasts in the RRAS
> console? This was added in Server 2003 and might solve your problem.
>
> "Karl Rhodes" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) oups.com...
> > Hi all...
> >
> > I have just managed to setup a very simple vpn pass thru connection to
> > a Windows Server 2003 computer in our office. I can connect from home
> > by the vpn connection I created in Network Connections. Once the
> > connection has been made and I have logged on etc, I am able to open a
> > remote desktop connection to the server.
> >
> > However, What I can't seem to do, is use Windows Explorer or the 'My
> > Network Places' to connect to any of the other servers (even though my
> > logon has permissions to see them, and can see them when in the
> > office).
> >
> > What do I need to do to Windows Server 2003 to enable office internal
> > network routing?
> >
> > IE: I'm sat at home, connected via vpn connection to vpn server
> > 192.168.1.10 (office local network ip) and want to get files from
> > office file server 192.168.1.20 (again, office local network ip).
> >
> > Thanks
> >