Re: DESPERATE HELP: VPN Client cannot access internal resources

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello,

Have you checked out the following article?

http://support.microsoft.com/default.aspx?scid=kb;en-us;838245


and

VPN clients can no longer access internal resources after you install
Windows
Server 2003 Service Pack 1 on a computer that is running ISA Server 2000
http://support.microsoft.com/?id=897651


regards,

Henk

"Bruno" <Bruno@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5859405D-7034-44BD-9DB4-FD175B517AEE@xxxxxxxxxxxxxxxx
Hi Everyone,



I'm with a very critical problem.

Recently I have to rebuild my ISA2004 SP2 server which is member of a
domain. I decided not to export and import the old configuration, and
otherwise, start it all over.

Well, after setting up the rules, everythin is working fine, except for
VPN
client with PPTP. I can connect and authenticate VPN Clients with no
problem.
But now come my problem: when I have connected and been validated I can
not
access anything on the internal network (even using IP address). I've
created
rules there allow anything from ALL USERS from VPN Clients to the Internal
network and Local host, but it seems like my traffic is disappearing. The
users can get connected, get an IP-address (which is static), validate in
AD,
and, one thing important: THEY CAN ACCESS ISA SERVER (ping, RDP, etc), but
not access internal servers and resources. When I get monitoring the
trafic
in ISA Server for VPN Clients, nothing is shown to Internal Network. YES,
there's nothing in monitoring logging.

But here is the setup:

ISA 2004 with SP2 which is member of the domain.
Public interface is setup with public IP address and default gateway on
the
same subnet obviously

Internal interface:
IP 192.168.0.1/24

VPN Clients Static Pool

192.168.100.10 to 192.168.100.20



The ISA server can ping and make nslookup on all the infrastructure
internal
servers.

If any one has a suggestion what I might need to set or how I can
troubleshoot it, I would be very gratefull.

I've been through the guides on this forum, the books, MS VPN deployment
guide, and MS Premier Support Site. And I can't find the error.

Thanks in advance for any suggestion there can point me in the right
direction.
If you miss any information about the setup, ask and I will try to give
it.

Best Regards, Bruno.



.

Relevant Pages

  • RE: DHCP and VPN
    ... in this range means that the computer cannot see the network. ... A computer using DHCP needs to have an external server tell it what IP ... I think the VPN clients unable get IP from DHCP on SBS. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN client cannot ping SBS 2003 server
    ... I understand that the remote VPN clients can ... Windows Server 2003 Service Pack 1 on a computer that is running ISA Server ... apply the hotfix on the SBS Server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Network Connection
    ... Does this occur just while on the network or remote VPN clients as well (if ... Connection to Microsoft Exchange has been lost. ... Connection to Microsoft Exchange has been restored. ... The Security System could not establish a secured connection with the server ...
    (microsoft.public.windows.server.networking)
  • Re: Static addresses
    ... Do I need to enable it on the ISA server? ... Jens Baier wrote: ... I'm trying to enable VPN access through ISA 2006 but when I try add a static range of addresses to apportion to the VPN clients it gives me an error message regarding overlapping range of addresses. ...
    (microsoft.public.isa.vpn)
  • RE: SQL Developer Remote Access
    ... I am not sure where the CD that contains ISA Server ... You said you run the SBS 2003 premium. ... deny rules in my previous reply, all VPN clients could only access SQL ...
    (microsoft.public.windows.server.sbs)