• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 323
  • Last Modified:

Microsoft Internet Acceleration Server Setup problem HELP!?

Hi All, I am setting this up on a w2k machine that has 2 network adapters installed.  When I use the set up wizard and get to the page where I am entering an ip address range that spans the internal network address space, I am getting an error after entering 192.168.241.0-192.168.241.255.  The error says:

"The local address table must contain at least one of the ISA Server IP Addresses"

Adapter #1 has internet access and an appropriate address.  Adapter #2 has an address of 192.168.241.90.  It is configured but not hooked into the network yet.  As you can see, the wizard SHOULD be recognizing the address to be within range.  I am not sure why it does not.  Please help.  Thanks.

p.s.  The dns server should be which IP or adapter?  Thanks.
0
Sp0cky
Asked:
Sp0cky
1 Solution
 
What90Commented:
The NIC's network connection must be up (i.e. plugged in to another port) or ISA won't see it!

Plug the NIC into a spare hub/switch or use a cross over cable to plug in both cards.


Ps.
You should never put in the external address of the ISA server in the the local address table (LAT). Only the internal range should be on the LAT. ISA normally does this for you.


The two cards you have the internal one (one connected to the LAN) should be a non routable address i.e 10.x.x.x 172.16.x.x or 192.168.x..x

The Public one (one connected to the external network) should have a public address for external networks.

DNS should be the ip address.

Top site for all ISA problems:
http://isaserver.org/
0
 
Sp0ckyAuthor Commented:
Thank you What90.  Exceptional response!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simple Misconfiguration =Network Vulnerability

In this technical webinar, AlgoSec will present several examples of common misconfigurations; including a basic device change, business application connectivity changes, and data center migrations. Learn best practices to protect your business from attack.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now