Answered by:
Isa Server 2006 SP1, 10061 connection refused, the server you are trying to access refused the connection with the gateway
-
Hi
We are getting error 10061 connection refused....with ISA 2006 logs when trying to browse an internet site (http://URL:7001) which is published on port 7001. This external site is working fine from internet. There is another Firewall in front of ISA (Cisco ASA), as per update from CISCO team that firewall is not blocking this URL, shall anyone help us to rersolve this issue
Thanks in advance
LMS- Edited by Laljeev Madanamma Saturday, December 11, 2010 5:32 AM
Question
Answers
-
10061 error code is when we dont have the connectivity with the server
client--------isa server----internet -----------web server
you are getting error 10061 connection refused in the isalogs . From my experience on such cases i can say that connectivity with the server is not there. But to do actual fact finding to find who is causing the connectivity problem you need to take network traces.
Run network monitor 3.4 while doing repro of the issue.
1. Network monitor on the client.
2. Network monitor on the internal NIC of the ISA server.
3. Network monitor on the exernal NIC of the ISA server.
filter the traffic on all three network traces to traffic for that website. From my experience i can say when you will filter this traffic on external NIC of the ISA server you might see "syn" packets going out for that website but no answers coming back from the web server. if you see that then check the device to which external NIC connects as that might be causing this loss of connectivity.
if you cant read network traces , i would suggest opening a case with microsoft.
Thanks and Regards Suraj Singh My blog: http://blogs.technet.com/b/sooraj-sec/- Proposed as answer by Suraj Singh MSFT Saturday, December 11, 2010 5:15 AM
- Marked as answer by Keith AlabasterModerator Sunday, December 12, 2010 9:50 AM
All replies
-
Hi,
10061 is "A connection was refused by the destination host". It seems to be a problem on the published Server. You should check your Server settings if the server accepts the request and there are no settings that deny the request. This error means that ISA Server tried to contact the published server (in this case the published Web Server) and the server refused the request. Have you checked the Bridging tab on ISA Server that the port matches with the port on the published server. Run a NETSTAT -AN |more on the published server to see if the Server is listening on port 7001
regards Marc Grote aka Jens Baier - www.it-training-grote.de - www.forefront-tmg.de - www.nt-faq.de -
-
10061 error code is when we dont have the connectivity with the server
client--------isa server----internet -----------web server
you are getting error 10061 connection refused in the isalogs . From my experience on such cases i can say that connectivity with the server is not there. But to do actual fact finding to find who is causing the connectivity problem you need to take network traces.
Run network monitor 3.4 while doing repro of the issue.
1. Network monitor on the client.
2. Network monitor on the internal NIC of the ISA server.
3. Network monitor on the exernal NIC of the ISA server.
filter the traffic on all three network traces to traffic for that website. From my experience i can say when you will filter this traffic on external NIC of the ISA server you might see "syn" packets going out for that website but no answers coming back from the web server. if you see that then check the device to which external NIC connects as that might be causing this loss of connectivity.
if you cant read network traces , i would suggest opening a case with microsoft.
Thanks and Regards Suraj Singh My blog: http://blogs.technet.com/b/sooraj-sec/- Proposed as answer by Suraj Singh MSFT Saturday, December 11, 2010 5:15 AM
- Marked as answer by Keith AlabasterModerator Sunday, December 12, 2010 9:50 AM
-
-
-
-
hi laljeev
thats exactly what i thought and thats what happens in most of the cases where you see 10060 or 10061 errors. they tell us about the connectivity issues and in every such case network trace is your best friend , to point out which device in the path is causing the connectivity problem. in your case its cisco ASA...:) i guess we can close this question now..?....:)
Thanks and Regards Suraj Singh My blog: http://blogs.technet.com/b/sooraj-sec/ -
-

