Welcome to ISAserver.org

ISA 2006 and Routing and Remote Access Woes

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 General] >> General >> ISA 2006 and Routing and Remote Access Woes

Page: [1]

Message

<< Older Topic Newer Topic >>

ISA 2006 and Routing and Remote Access Woes - 31.Oct.2007 5:03:30 PM

MPDano

Posts: 1
Joined: 31.Oct.2007
Status: offline

I followed your instructions on set up as I am new to this. I am stuck on why my vpn clients are getting a 169 address. I think I narrowed it down to Routing and remote access, but I think I messed that up now. I am no longer able to get an address on the internal. Under General, Internal shows IP address not available and unkown status. Do you have any suggestions?

< Message edited by MPDano -- 31.Oct.2007 5:04:36 PM >

Post #: 1

Featured Links*

RE: ISA 2006 and Routing and Remote Access Woes - 31.Oct.2007 6:33:29 PM

AHIT

Posts: 1561
Joined: 22.Jul.2002
From: Sydney, Australia
Status: offline

When obtaining a 169.x.x.x IP address (APIA - Automatic Private IP Address) this generally means a configuration issue - ie: Either the DHCP server on your network isn't working, has assigned all its available addresses, or you don't have a static IP range assigned for RRAS to use.
See this article http://support.microsoft.com/kb/326155#tocHeadRef for some assistance. Whilst it referes to web pages no tloading, the trouble shooting process is much the same.

Of interest, when you try and connect a VPN client, if you go into the RRAS admin console on the server, you shoul dbe able to see the logged in user.. and their assigned IP address. As I said tho - my vote goes towards DHCP issues, either in the DHCP server itself or perhaps RRAS has the wrong network card assigned to look for the DHCP server.

Oh, in regards to " followed your instructions on set up ", can you post the link to the instructions you follwed?

Let us know how you go..

_____________________________

http://www.ahit.com.au/isa
(Previous nick: Tolk)

(in reply to MPDano)

Post #: 2