Welcome to ISAserver.org

10061 - Connection refused

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> General >> 10061 - Connection refused

Page: [1]

Message

<< Older Topic Newer Topic >>

10061 - Connection refused - 28.Feb.2006 8:28:28 PM

smothers

Posts: 16
Joined: 29.Jan.2003
From: Portland, OR US
Status: offline

I am in the process of migrating from ISA 2000 to 2004.

I am still hosting two FQDN and their respective sites on the 2000 ISA server. I have created all new publishing rules on the new ISA 2004 server for Domain B, (currently do not have domain A published site created as I deleted them to see if that might be the case), but have not switched over the IP addresses to the new server yet however.

I have 2004 firewall clients on all users, and all published servers will be changed to securenat clients of the new server when I switch over. Problem exists however whether they are firewall, proxy or secure nat.

ISA 2000 currently hosts two FQDN Domain A and Domain B. Domain is also the name of my internal domain.

Users can access all internet sites, and all internally hosted domains on domain B.

Kelly

My current issue is this, users cannot access any sites from Domain A.

I have an A record for the www, for internal users to access the servers behind the ISA 2000. I've tried both bypassing servers for local domain and and directly access domain tabs.

< Message edited by smothers -- 28.Feb.2006 10:14:10 PM >

Post #: 1

Featured Links*

RE: 10061 - Connection refused - 28.Feb.2006 9:44:04 PM

tshinder

Posts: 47644
Joined: 10.Jan.2001
From: Texas
Status: online

Hi Smothers,

For internal to internal connections, you should be using direct access and not looping back through the ISA firewall.

HTH,
Tom

_____________________________

Thomas W Shinder, M.D.
Sr. Consultant/Technical Writer
Prowess Consulting http://www.prowessconsulting.com/
Blog: http://blogs.isaserver.org/shinder/

GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8

(in reply to smothers)

Post #: 2

RE: 10061 - Connection refused - 28.Feb.2006 10:13:47 PM

smothers

Posts: 16
Joined: 29.Jan.2003
From: Portland, OR US
Status: offline

Thanks Tom, I understand that, and in this scenario I'm not looping, as it's going out the isa 2004 and in the isa 2000. However, the plan is to allow that, as my user base would like to be able to use the same url as external users.

It is like pulling teeth to get them to use direct connect to the servers in question. I would imagine that it gives them a warm fuzzy if it works for them it is working for the external user as well.

With that said. Can you think of a reason why It will not 'loop' for the one domain and will for the other?

Kelly

(in reply to tshinder)

Post #: 3

RE: 10061 - Connection refused - 5.Mar.2006 4:20:42 PM

tshinder

Posts: 47644
Joined: 10.Jan.2001
From: Texas
Status: online

Hi Kelly,

I understand and agree that users should use the same URL for remote access and access when located on the corpnet. That's why the combination of split DNS and Direct access is so powerful!

HTH,
Tom

_____________________________

Thomas W Shinder, M.D.
Sr. Consultant/Technical Writer
Prowess Consulting http://www.prowessconsulting.com/
Blog: http://blogs.isaserver.org/shinder/

GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8

(in reply to smothers)

Post #: 4