VPN Connects, but no Internal IP or network resources.

Hi!

I am having a heck of a time getting VPN to work. I have followed the guides
posted here and at MS. I have also read the forum, searched the MS site, and
bought the Configuring ISA Server 2004 book to no avail. My problem, I am
afraid, is very simple but I am too dumb to figure it out. Here is what
happens:

1) I can connect via PPTP to the ISA Server, no problem. On the Details tab
of the Connection icon in the system tray, it matches the screenshots posted
here and elsewhere -- which signify a successful connection.

2) I cannot get an internal IP (192.168.1.X) to save my life (unless I do it
through a statically assigned address pool). I only get a 169.254.X.X address.

3) I also cannot ping any internal network resources including the server
(either its internal or external NIC). They cannot ping me either.

4) The server is called "Server" and then I do Start -- Run -- "\\Server", I
get a message that says it is not found.

5) I also cannot browse for network resources.

I have set up the DHCP scope to go from 192.168.1.0 - 192.168.1.254. I have
set up the internal network to go from 192.168.1.1 - 192.168.1.99. I have
also set up exclusions for external NIC (192.168.10.100) and the internal NIC
(192.168.1.50).

The client computer is running Win XP Pro SP2.

I have no idea if this makes a difference, but when (under ISA Server) I go
to Configuration - Networks - Double Click on Interal (which shows the
192.168.1.0 - 192.168.1.255), select Addresses, then Add Adapter, I notice 2
things:

1) There is a "new" RAS Server (Dial-in) Interface. It states in the info
box beneath it:

Name: WAN (PPP/SLIP) Interface
IP Addresses: 169.254.45.252
Route Information: 169.254.45.252 - 169.254.45.25

2) On the external NIC, it states:
Name: U.S. Robotics 10/100 PCI NIC TX - Packet Scheduler Miniport
IP Addresses: 192.168.10.100
Route Information:
0.0.0.1 - 126.255.255.255,
128.0.0.0 - 169.254.45.251,
169.254.45.253 - 192.168.0.255,
192.168.2.0 - 223.255.255.255,
240.0.0.0 - 255.255.255.254

PLEASE PLEASE PLEASE HELP ME. At this point, I about to start forcing my
users to use carrier pidgeons for remote access.

Cheers,
rolf
.

Relevant Pages

  • RE: ISA server configuration with multiple internals network.
    ... Have you configured all internal VLANs as internal network within ISA? ... the correct interface ID and the correct VLAN details? ... The external interface has the default gateway. ... 2---A trunk link is attached to a GiG interface to the ISA server, ...
    (microsoft.public.isa.enterprise)
  • Re: isa on a single subnet
    ... configure an external ISA server interface in accordance to the upstream link requirements. ... Take a look how the DLink's WAN port configured and perform similar configuration with the ISA's external interface. ... After you perform all the ISA configuration and tests, you have two options of moving all the clients to the newly deployed internet gateway: ... Right after that you can settle back, relax and have a fun with secure internet browsing through the ISA server. ...
    (microsoft.public.isa)
  • Ping from Outside on the internal IP Interface
    ... we are using a network analyzing programm spectrum. ... the internal IP interface from the ISA Server or a node in the ... LAN the ping doesn't work. ...
    (microsoft.public.isaserver)
  • RE: Checkpoint Front End server - ISA Back End server - OWA Setup
    ... As your figure 1 there is no bypass for ISA server. ... ISA's external interface. ... Is the ISA's external interface Internet? ... looking to use owa with an ISA Server used as a back end firewall. ...
    (microsoft.public.isa)
  • RE: Confused!!!!
    ... the isa server needs to consider the hardware firewall as a ... so the ISA server considers the 212.135.x.x subnet to be the internet, ... the DMZ interface is 212.135.x.x/26 so i have a bunch of public IP's ... you will need 2 distinct networks because ISA needs to consider on of its ...
    (microsoft.public.isa.configuration)
Loading