Re: bad VPN client addresses from ISA
- From: "B Squared"
- Date: Fri, 01 Sep 2006 09:56:21 -0700
with the range of addresses you want the VPN clients to have. I've done this, but ISA still hands out addresses in 169.524.x.x, which, in our network, are useless. I'm sure there's just something I'm missing.
this is a APIPA address ranges. It seems to be that your VPN client cannot find or conenct to the DHCP Server. Are you using a DHCP Server? where? You can also set a static address pool in the VPN configuration of ISA!
Right now I want to create a static address pool. Later, after we are using the VPN regularly, I might have to use DHCP. -- I thought what I was doing with the:
"Documents and Settings\All Users\Application Data\Microsoft\
Firewall Client 2004\Locallat.txt"
was setting up a static address pool.
Can you give me a pointer to setting up the pool? And possibly pointing
the ISA server to our DHCP server later on? A reference to documentation would be sufficent.
Thanks alot.
B Squared
_____________________________________________________________________
You can't run away forever, but there's nothing wrong with getting a good head start. -- Meatloaf
.
- References:
- bad VPN client addresses from ISA
- From: B Squared
- bad VPN client addresses from ISA
- Prev by Date: bad VPN client addresses from ISA
- Next by Date: Re: Caching the Site with Authentication
- Previous by thread: bad VPN client addresses from ISA
- Next by thread: Re: Caching the Site with Authentication
- Index(es):
Relevant Pages
|
Loading
