Re: Baffling VPN Problem

From: Tom Schmidt <tjsnews_at_tnospamschmidt.com>
Date: Sat, 17 Feb 2001 02:14:00 GMT

"Anna" <anromero_at_bellatlantic.net> wrote in message news:3uij6.554$lx.584856_at_typhoon2.ba-dsg.net...
> Hi All,
>
> I've got a real brain-teaser on my hands, and I need your help - any
advice
> you have is greatly welcome.
>
> Here's the problem:
> VPN was working just fine one day. The next day, it wasn't. Poof. Nothing
> changed on either the client side nor the server side. It just stopped. It
> appears to be creating the tunnel successfully. I can ping any IP on the
> remote LAN, I can remotely access the firewall settings. I can see the
> shared folders on the server. My problem is that I cannot open any of the
> files anymore. I can upload files to the shared folder, but I cannot open
> them remotely nor can I copy remote files to my local machine.
>
> Here's the basic configuration (if you need more info, just ask):
> The server is a Win NT 4.5 SBS with a Sonicwall SOHO (5.1.1 firmware) that
> is NAT-enabled.
> The client is a Win 98 SE behind a LinkSys BEFSR11 (1.37 firmware with
IPSec
> passthrough and PPTP enabled) and Verizon ADSL. The client is using
Sonic's
> VPN client software. Authentication is via manual key.
>
> Here's a speculation: During the time that the VPN first exhibited this
> problem, Verizon was upgrading software on their backbone (and several
> routers). Could it be that that's where the problem is?
>
> The reason I'm suspicious is that the only other person that is having
this
> problem is also on Verizon behind a LinkSys. However, I've reached the
limit
> of my tech experience. I can't get Verizon to admit anything, LinkSys is
not
> calling me back, and SonicSys still has me at level 1 tech support (Yes, I
> checked that the cables are hooked up properly:)).
>
>
> Any suggestions?
>
> Thanks,
>
> Anna
>
>
>
>
>
>
>

It sounds like the VPN is working, or you wouldn't be able to even see the shares.

Are you sure this is not an access rights problem? Is it possible that your administrator might have changed access policy and the Verizon stuff is just a coincidence?

The other possibility, I assume you are running private IP addresses behind your router. If your office is also using private addresses make sure you home and office are using separate blocks. Received on Fri Feb 16 2001 - 18:16:02 PST

Report this message as spam or inappropriate.