Re: Problem accessing PCs when connected using VPN

Richard Kimberley wrote:
"Ian" <gruntyonline@xxxxxxxxxxx> wrote in message news:%230WyKUfvFHA.2568@xxxxxxxxxxxxxxxxxxxxxxx

Richard Kimberley wrote:

"Ian" <gruntyonline@xxxxxxxxxxx> wrote in message news:eyCmCxVvFHA.3740@xxxxxxxxxxxxxxxxxxxxxxx


Richard Kimberley wrote:


"Ian" <gruntyonline@xxxxxxxxxxx> wrote in message news:OubafNVvFHA.3688@xxxxxxxxxxxxxxxxxxxxxxx



Richard Kimberley wrote:



The situation now is that I can access the shared folders on the VPN server and I can ping the VPN server's IP and hostname.

I can't however access or ping any other computer on the LAN other than the server. Any ideas?

Thanks,

Rich.


"Ian" <gruntyonline@xxxxxxxxxxx> wrote in message news:O5pQDhGvFHA.2064@xxxxxxxxxxxxxxxxxxxxxxx




Richard Kimberley wrote:




We currently have two servers, each running Windows 2003 Small Business Server. Both servers are for different domains at the moment as we eventually want to move everything to the second server.

The setup is as follows:

SERVER01    -    domain1.local
SERVER02    -    domain2.local

All client computers are running Windows XP Pro and are on the SERVER01 domain. The SERVER02 machine is sitting doing nothing at present, it simply has a shared folder on it which is accessable

from the XP client machines.

All this works fine and th shared folder on SERVER02 does what it's intended which is simple file sharing.

The problem arises when a workstation connected to SERVER01 via a VPN connection tries to access the shared folder on SERVER02. The error is simply that SERVER02 cannot be found. Yet when the same client connects using the LAN directly, it can access the same shard folder on SERVER02 perfectly well.

Also, the client connected via VPN can communicate with all the Win XP client PCs on the LAN. Yet it sees SERVER02 as non existant! SERVER02's IP address can be pinged ok from the client connected using VPN.

Has anyone got any ideas of how to solve this problem?

Any help would be eternally appreciated!

Thanks,

Richard.

Can you open the server whilst connected using the VPN by using the IP Address rather than the name?

Are the 2 domain's in different Subnets?

Are you using WINS?



Are you using RRAS? Have you enabled routing between the 2 subnets? or do you have another device routing between the subnets?

Can you ping server02 from server01? Is server01 your RRAS Server?

Have you setup any routes to go between these subnets?


Yes I'm using RRAS. I haven't enabled routing between the two subnets (I assume we re talking about the VPN subnet and the LAN subnet?)

Server02 can be ping's from Server01, yes. Server01 is the RRAS server.

I don't know how to seyup routes between the subnets. Very new to all this! Any help would be very much appreciated.

Thanks,
Rich.


What device is in the "VPN Subnet"?, Is one of your server's multihomed?

Whatever device is in the VPN Subnet answering VPN Calls needs to have an ip route to the Lan Subnet in order for traffic to flow. 


Hi Ian,

Bear with me on this one, I'm not familiar with the terms used.

The LAN is using IP address range 192.168.0.x on subnet 255.255.255.0

Server01 is 192.168.0.2 (only one network card present)
Server02 is 192.168.0.3
LAN clients are 192.168.0.5x
The ADSL router is 192.168.0.254 (also the DHCP server)

The VPN connection is to the Server01 and the DLink ADSL Modem/router has the IP routing set up to forward incoming VPN connections to Server01.

The VPN subnet appears to be 255.255.255.255.

Does this help at all? How do I provide VPN calls a route to te LAN subnet?

Sorry to be a pain on this one, it's all totally new to me :)

Cheers,

Rich.




Hi Rich,

Just read this post from the beginning again as i think we have missed a few steps.

When connected using the VPN Connection - can you contact the other XP desktops by using IP address other than the computer name?

If so - there is a setting in Routing and Remote Access to enable Broadcast Name Resolution (Right Click the server object, goto properties, select IP, Broadcast name resolution box is at the bottom of the screen). - Only do this if you can ping the IP addresses of the xp desktops from the VPN Client.

Ian 


Hi Ian,

Many thanks for your help mate.

Right, the VPN client cannot ping any other XP machine on the LAN. The VPN client can ping the VPN server's LAN IP.
Broadcast Name Resolution is ticked.

So basicaly, I am unable to ping any other PC on the LAN from the VPN client by IP (and of course by name).

Any thoughts?

Thanks,

Rich. 


No Worries,

Is enable IP Routing enabled (Same screen as broadcast name resolution - at the top)

What IP Address is being issued to your vpn clients

Ian
.

Relevant Pages

  • Re: vpn access from hotel room
    ... If you have a dedicated workstation on the LAN (or just access to any LAN ... users to keep all their data on the server so it's ... A VPN requires significantly more bandwidth ... If you're laptop has been joined to the SBS domain, ...
    (microsoft.public.windows.server.sbs)
  • Re: Routes
    ... succeed with the original requirements because it won't limit LAN access to the ... access to only the Terminal Server by using something like ISA,...once the user ... I will allow full network access to the VPN clients. ... terminate at the servers and no further into the LAN. ...
    (microsoft.public.windows.server.networking)
  • Re: Horrible VPN Performance
    ... Comment vis a vis running websites on SBS. ... VPN implementation in Microsoft software and talk to the ... > server database to scrap. ... which uses a workstation on the LAN running ...
    (microsoft.public.windows.server.sbs)
  • Re: ICS quandary
    ... and RRAS allows interfaces to be created as ... i.e. a demand dial vpn. ... my LAN (3 XP pro, a 2k server domain controller, and a redhat 9). ...
    (microsoft.public.win2000.ras_routing)
  • Re: ICS quandary
    ... and RRAS allows interfaces to be created as ... i.e. a demand dial vpn. ... my LAN (3 XP pro, a 2k server domain controller, and a redhat 9). ...
    (microsoft.public.win2000.networking)
Loading