[isalist] Re: ISA 2004 Issues
- From: "Ellis, John P." <johnellis@xxxxxxxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Fri, 10 May 2013 10:17:03 +0100
Looks like one of the load balanced NICs isn't a happy bunny and ceasing
to respond. So I am going to attempt to setup the spare NIC on the
server for NLB.
John
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Jim Harrison
Sent: 09 May 2013 16:07
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: ISA 2004 Issues
John,
99 times out of 10, this combination generally points toward a NIC
driver problem.
Have you checked for updates to these?
Sent from my mangophone
________________________________
From: Ellis, John P.
Sent: 2013-05-09 6:35
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] ISA 2004 Issues
We have a pair of ISA 2004 Enterprise servers NLB'd and publishing a
good selection of services/websites
Recently we have been having issues whereby, connections from outside to
one website in particular fails and the error shown in the browser is
The server is too busy. Please try it again later
Yet, internally the website works OK.
Rebooting both ISA servers tends to resolve the issue, yet the last time
I did this the website started working and then stopped.
Next morning I checked the website externally and it worked. ...Odd.
With it working I left it be.
A couple of days later(while I was off) the same website dropped out
again, with the same error. This time rebooting the servers didn't fix
it.
A fix was done on the f/w to bypass ISA and go direct to the website,
this worked instantly. I suspect ISA was/is at fault.
At the same time, a couple of other sites published via ISA also stopped
working, but the reboot fixed this.
On my return I have trawled event logs and noted a few re-occurring
errors.
The Configuration agent has restored its connection to the Configuration
Storage server 'ourisaserve.our.domain '.
ACE/Server is not responding. Run SDTEST on Windows or sdinfo on Unix
to verify port and IP address of ACE/Server. Make sure ACE/Server
process is running.
Network Timeout - - ACE/Server was responding but has now stopped.
Web publishing rule [Published site (1xx.1xx.2xx.xx] failed because the
Web listener selected for the rule is not valid. Verify that the Web
listener specifies a valid IP address on this computer.
Web publishing rule [Published site] failed because the Web listener
selected for the rule is not valid. Verify that the Web listener
specifies a valid IP address on this computer.
There is no suitable network adapter related to network 'External'.
Network Load Balancing cannot be configured properly, and will be
stopped on this server. A suitable network adapter must have a static IP
address that belongs to the network and is different than the cluster
Virtual IP address.
The Web Proxy filter failed to bind its socket to 1xx.1xx.2xx.xx port
443. This may have been caused by another service that is already using
the same port or by a network adapter that is not functional. To resolve
this issue, restart the Microsoft Firewall service. The error code
specified in the data area of the event properties indicates the cause
of the failure.
These errors are take off the servers in the application log.
In ISA I have also seen that NLB has stopped working as well along with
other alerts shown inside ISA application
Looks like another reboot tonight to bring NLB back into sync.
No windows patches have been applied for a while on either servers.
Thanks
John
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.clearswift.com
**********************************************************************
Other related posts:
