RE: Help! Firewall stops working after adding more IP's to NIC
- From: "Jim Harrison" <jim@xxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Sat, 11 Jan 2003 14:11:46 -0800
No, he doesn't; the error code ends in "1200.50".
That's the version of ISA that's running.
Jim Harrison
MCP(NT4, W2K), A+, Network+, PCG
http://isaserver.org/pages/author_index.asp?aut=3
http://isatools.org
Read the help / books / articles!
----- Original Message -----
From: "Thomas W Shinder" <tshinder@xxxxxxxxxxxxxxxxxx>
To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
Sent: Saturday, January 11, 2003 12:02
Subject: [isalist] RE: Help! Firewall stops working after adding more IP's
to NIC
http://www.ISAserver.org
Hi Michael,
Do you have SP1 installed on the ISA Server?
Thanks!
Tom
www.isaserver.org/shinder
-----Original Message-----
From: Michael Anderson [mailto:mike@xxxxxxxxxxxxxxxx]
Sent: Saturday, January 11, 2003 8:05 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Help! Firewall stops working after adding more IP's
to NIC
http://www.ISAserver.org
Hello,
We are running ISA Server w/Windows 2000 Server SP3.
We have business class RoadRunner (Cable Service) for our Internet
Access,
and as of yesterday, we just upgraded to 13 IP's versus the single
Static
that we had.
After changing the primary IP of the NIC card to the first number in the
new
block, the server came up just fine and all was well. Then after
feeling
confident that the new configuration was working properly, I decided to
bind
the remaining 12 IP Addresses, so we could start using our new numbers
(for
Server publishing).
After I do that, the Firewall Service no longer wants to start. I keep
getting Event log messages of the following:
"Microsoft Firewall failed. The failure occurred during
Initialization
of Network Address Translation (NAT) because the system call InitNAT
failed.
Use the source location 308.1113.3.0.1200.50 to report the failure. The
error code in the Data area of the event properties indicates the cause
of
the failure. For more information about this event, see ISA Server Help.
The
error description is: A device attached to the system is not
functioning."
I checked the Support site at MS, in addition to the help files, and it
came
up with nothing that was of any help.
How could adding more IP's to the External NIC Card cause all these
problems? Is it because ISA is confused as to which IP address it's
supposed to NOW use (due to multiple IP's being bound to the card), when
doing NAT? I thought the first number in the list would be considered
the
default number.
Could someone point me in the right direction as to how to fix this?
Thank you all very much in advance for anything you can throw my way.
Mike
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Exchange Server Resource Site: http://www.msexchange.org/
Windows Security Resource Site: http://www.windowsecurity.com/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
tshinder@xxxxxxxxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Exchange Server Resource Site: http://www.msexchange.org/
Windows Security Resource Site: http://www.windowsecurity.com/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jim@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
