Re: VPN clients unable to connect to other resources.
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 3 Mar 2008 11:48:23 -0500
After you connect the VPN to the SBS as expected, can you please describe what you're trying to do that's failing, and how you're trying to do it? Please post back what's failing, and the specific error message (if there is one).
For example, if you have a share on a desktop PC that you're trying to access, what happens if on the remote client, you go to Start -> Run and type in \\hostname\sharename? And if that fails, what happens when you try to do it from another machine on the SBS LAN?
I wouldn't worry about ping except in the absence of the ability to actually connect. For example, your SonicWall is probably configured to ignore pings. I would start by seeing if you can connect to a resource from within the LAN, and if not, look at the firewall settings and the remote access permissions on that machine. Besides networking, which appears to be working properly, you could be running up against the local machine's firewall settings, NTFS permissions, etc.
One thing to check - if you're having trouble connecting to an XP box, go to CP -> Windows Firewall and make sure it's set to use the domain settings (it'll tell at the bottom of the first page in the firewall properties). If it's set to non-domain, set the Network Location Awareness service to automatic startup, and either reboot or do a gpupdate /force. In the non-domain configuration, remote access is blocked, and so is ping.
"J Smith" <JSmith@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D8F9B880-7B16-49F0-9A73-1EF4D0A395C5@xxxxxxxxxxxxxxxx
The XP Pro clients are connecting to the SBS 2003 server. I did use the
wizard to setup remote access. The clients connect to the server and can
access the server shares and so forth. The IP of clients when they connect
is 192.168.2.XXX matches the subnet of the 2003 server. I find it strange
that the IP and Gateway match the on the network IP given by the DHCP server.
I need the VPN because we have a sonicwall device that will backup client
laptops on the network via VPN access. I can't ping the sonicwall device nor
the gateway. I need the VPN to work for the device to pick-up the CDP data
protection for the remote clients this rules out the RWW.
"Dave Nickason [SBS MVP]" wrote:
Are you using the SBS as the VPN end point? If your SBS and your local
client PCs are on 192.168.2.x, your remote clients should be getting an IP
address from the DHCP server on the SBS that's in the 192.168.2.x subnet.
If you haven't already, I'd go to the Server Mgmt Console, Internet page,
and run the Configure Remote Access wizard. Not sure that'll fix this, but
it's a start.
Do you need VPN for some reason? If not, why not use RWW instead?
"J Smith" <JSmith@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9606D119-6C75-4A7C-B5F2-FCF5ABBC1E75@xxxxxxxxxxxxxxxx
> XP Client machines that can successfully connect to the SBS 2003 server
> via
> VPN cannot access other shares or network resources outside of the SBS
> 2003
> server. After connecting to the VPN server the IP assigned from the
> server
> matches the gateway on the DHCP assigned address from the server.
>
> IP 192.168.2.57
> Gateway 192.168.2.57
>
> I can ping and connect to the server 192.168.2.25 but I can not ping > the
> true gateway 192.168.2.1 nor ping any other machine on the subnet. The > IP
> scheme of the XP Client machines are 192.168.1.XXX so I'm pretty sure > this
> is
> not an issue. I think there is a route problem or misconfiguration on > the
> VPN
> server. I'm wanting to be able to let the XP client access other shares > on
> a
> couple different locations 192.168.2.250 and 192.168.2.225. Thanks for
> your
> feedback and assistance.
>
> J Smith
.
- Follow-Ups:
- Re: VPN clients unable to connect to other resources.
- From: J Smith
- Re: VPN clients unable to connect to other resources.
- References:
- Re: VPN clients unable to connect to other resources.
- From: Dave Nickason [SBS MVP]
- Re: VPN clients unable to connect to other resources.
- From: J Smith
- Re: VPN clients unable to connect to other resources.
- Prev by Date: Re: NTBackup requires 18-23 hours to complete.
- Next by Date: Re: NTBackup requires 18-23 hours to complete.
- Previous by thread: Re: VPN clients unable to connect to other resources.
- Next by thread: Re: VPN clients unable to connect to other resources.
- Index(es):
Relevant Pages
|
Loading