• RSS
  • Twitter
  • FaceBook

Welcome to ISAserver.org

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Page Not Found (Connection refused)

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [ISA Server 2000 General] >> Web Publishing >> Page Not Found (Connection refused) Page: [1] 2   next >   >>
Login
Message << Older Topic   Newer Topic >>
Page Not Found (Connection refused) - 24.Aug.2003 5:03:00 AM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
Hi there,

I tried to have a multiple website. I've done Using Virtual Directory to access multiple website.

Then, I tried another option to have multiple website by using different IPs and Port at the same computer. BUT IT FAILS give the message on the following below:

"10061 - Connection refused
Internet Security and Acceleration Server"
Post #: 1
RE: Page Not Found (Connection refused) - 24.Aug.2003 5:08:00 AM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
For another information:

if i used to browse http://192.168.20.1:81, it is
okay

another website is 192.168.0.1 for external website. (configure on IIS server)

if i browse 192.168.20.1, it goes to website which use 192.168.0.1

If I tried to use 192.168.20.1/web1. the connection refuse by ISA as message like the previous one..

(in reply to BenYB)
Post #: 2
RE: Page Not Found (Connection refused) - 24.Aug.2003 6:22:00 PM   
camos

 

Posts: 70
Joined: 17.Aug.2003
Status: offline
BenYB,

Here are the steps to publish multiple sites with one public IP.
1. Set up internal NIC with multiple IP's
eg: 10.0.0.10, 10.0.0.11, etc.
2. In IIS point Site1 to 10.0.0.10 port 81
3. In DNS zone mydomain.com create host Site1
Restart DNS server
4. Create Destination Set Site1 with:
Destination - Site1.mydomain.com
5. Create Web Publishing Rule Site1 with:
Destinations - Selected destination set, Name - Site1
Action - Redirect to this internal Web server (name or IP) - 10.0.0.10, Connect to this port when bridging request as HTTP - 81
6. Make sure Protocol Rules Inbound Access include HTTP protocol
7. Make sure MyISAserver Properties:
Incoming Web Requests - Use same Listener for all IP address, TCP port - 80
8. Restart ISA Server Control

Do this for each site published by IIS

Access the sites using http://site1.mydomain.com

Cheers,
Clive

(in reply to BenYB)
Post #: 3
RE: Page Not Found (Connection refused) - 25.Aug.2003 2:08:00 AM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
thank clive.. but one of your i am not really sure which you said on protocol rule. Do i have to inbound it. if i want to inbound it, what port should be enter. is it port 81 or 80?

One more things..if i have multiple IP addresses by addding at Control Panel -->Network Connection-> LAN conection'properties-> TCP/IP--> then Advanced-> add Ip addresses. Do i Have to bind the multiple IP address? and How to Bind IP addresses?.

thank you
please reply me.I am really appreciate

[ August 25, 2003, 02:49 AM: Message edited by: BenYB ]

(in reply to BenYB)
Post #: 4
RE: Page Not Found (Connection refused) - 25.Aug.2003 5:02:00 AM   
camos

 

Posts: 70
Joined: 17.Aug.2003
Status: offline
BenYB,

The inbound Protocol Rules do not need a port. They allow or reject protocol types. You want to make sure your inbound allow rule includes HTTP.

Referring to adding IP's, I am not sure what you are asking here:
Control Panel -->Network Connection-> LAN conection'properties-> TCP/IP--> then Advanced-> add Ip addresses.
On the IP Settings tab click on Add and you get a dialogue box where you enter the IP and the subnet mask. Enter the same numbers as your original IP set just increment the IP by 1 and keep the same subnet mask.

I should have mentioned the need to disable socket pooling in IIS. You can find a vb script that will do that at ISATools.org

I should also mention that in your DNS server properties, set to listen on only the primary IP for the NIC, not on all.

Keep on truckin' - you'll get it.

Cheers,
Clive

(in reply to BenYB)
Post #: 5
RE: Page Not Found (Connection refused) - 25.Aug.2003 8:00:00 AM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
you've been talked about the DNS server which you ask me to listen only Primary one. right?
in my case, 192.168.0.1 is also my DNS server and my ISA server and also IIS server.

So, where i have to choose or select my primary address? is it on the properties of DNS server (at the console tree)?

FYI, I have disable socketpooling at the beginning i configure my first webserver. I also use DHCP server.

in my case also, I used different IP address 10.10.0.2 other than 192.168.x.x because my internal network also used 192.168.x.x which i already configured at my DHCP.

(in reply to BenYB)
Post #: 6
RE: Page Not Found (Connection refused) - 25.Aug.2003 4:48:00 PM   
camos

 

Posts: 70
Joined: 17.Aug.2003
Status: offline
When you add multiple IP's to a NIC, the DNS server will by default listen on all of them. This doesn't cause any problems other than it is a waste of resources. In the DNS server properties (Computer Management mmc), set it to only listen on the primary IP of the internal NIC and not on the extra IP's that will be assigned to each Web site. In your case it will be 198.168.0.1.

It probably works but I have never tried assigning different networks to one NIC. You would need to create a separate zone on the DNS server.

Each Web site in IIS needs to listen on the IP assigned to it in the DNS zone.

You should read the tutorial on Split DNS as well, the one on Co-Located ISA server

Cheers,
Clive

(in reply to BenYB)
Post #: 7
RE: Page Not Found (Connection refused) - 25.Aug.2003 5:09:00 PM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
I've successfully done on internal multiple website but...how external client can access my multiple website? can you give me an advice on how to configure which allowing external clien(internet) can access my multiple internal website..?

please help me... anyone...

(in reply to BenYB)
Post #: 8
RE: Page Not Found (Connection refused) - 25.Aug.2003 7:55:00 PM   
camos

 

Posts: 70
Joined: 17.Aug.2003
Status: offline
BenYB,

Assuming you have set up your DNS correctly to point to your Web sites and completed all the other steps previously mentioned, there is one more step that I did but did not mention because I am not sure it is necessary. You may need to also create a Server Publishing Rule to allow your DNS server to talk to incoming public requests.

Incoming requests for http://mydomain.com would be sent to your ISA server by your domain's registered DNS servers. The ISA DNS server would pass the request to the appropriate internal site. Incoming requests for Site1 would be http://site1.mydomain.com. Incoming requests for Site2 would be http://site2.mydomain.com.

If you have multiple Web sites that each have a public FQDN you will need to make the external NIC listen on each public IP. In this case the previously described procedure would need to be modified somewhat.

What happens when someone tries to connect from the outside? Are you still getting the denied error?

Cheers,
Clive

(in reply to BenYB)
Post #: 9
RE: Page Not Found (Connection refused) - 25.Aug.2003 11:29:00 PM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
i think there will be not denied error. because if i am pointing to http://mydomain.com, it will go to http://mydomain.com of internal.(ip address of 192.168.0.10)

if we are point http://site1.mydomain.com, we have to specify the destination set in order to redirect to http://site1.mydomain.com of internal (192.168.0.11).

Is this answer your question..hope so..hehehe

however, can we set the destination set of external ip address such as A.B.C.D with following the path http://A.B.C.D/web1?
so that the destionation redirect it to site1.mydomain.com

(in reply to BenYB)
Post #: 10
RE: Page Not Found (Connection refused) - 26.Aug.2003 4:26:00 PM   
camos

 

Posts: 70
Joined: 17.Aug.2003
Status: offline
BenYB,

When you point to http://site1.mydomain.com ISA uses the FQDN in the configured Destination Set to redirect to site1. There is no need for the request to specify anything more.

You could configure the destination set of external ip address A.B.C.D with the path http://A.B.C.D/web1 and have ISA redirect it to site1 on IIS. This is a different method, one that does not use a FQDN. Choose one way or the other but don't combine them.

There is an article or tutorial that describes the use of sub-folder paths to redirect to different Web sites.

Cheers,
Clive

(in reply to BenYB)
Post #: 11
RE: Page Not Found (Connection refused) - 27.Aug.2003 11:55:00 AM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
Can it possible that the external ip address has multiple website.What i mean is that..

if i've already registered the domain, i.e mydomain.com and resolved ip address 202.152.x.x and then the external client want to open internal web that goes to web1.mydomain.com (10.10.0.1). can it be possible to use 1 external IP address to point the intenal web web1.mydomain.com which using http://site1.mydomain.com to open web1.mydomain.com(internal website). do i have to get different IP address for http://site1.mydomain.com resolve 202.152.78.125 and another website of http://mydmain.com to resolve 202.152.78.254.?

(in reply to BenYB)
Post #: 12
RE: Page Not Found (Connection refused) - 27.Aug.2003 4:36:00 PM   
camos

 

Posts: 70
Joined: 17.Aug.2003
Status: offline
BenYB,
The answer to your first question is yes, that is the whole point of this exercise.

You only need one registered domain name and one public IP (202.152.x.x) address to publish multiple Web sites. ISA effectively makes each Site a subdomain of mydomain.com (site1.mydomain.com).

Trying to make external http://web1.mydomain.com point to internal http://site1.mydomain.com is an unnecessary confusion that may not work. Keep the internal site name the same as the external published name.

Cheers,
Clive

(in reply to BenYB)
Post #: 13
RE: Page Not Found (Connection refused) - 27.Aug.2003 11:52:00 PM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
make it straight.

do you mean if my external ip address is 202.152.78.125, then it goes to http://mydomain.com (primary DNS) and at the same ip address 202.152.78.125 can go to my subdomain of web1.mydomain.com. So, if i am doing all of this, I have to make my internal Domain at DNS such as mydomain.com must be the same of the public domain that was registered. IS THIS CORRECT? (i just want to make sure).

IF THIS IS CORRECT, what would you do if you want to point to web1.mydomain.com?

Actually, I just want to do web1.mydomain.com, not doing http://mydomain.com/web1.

in my opinion, if i want to point web1.mydomain.com (I am viewing from external client).I have to make destination set of extetnal web1.mydomain.com, then another destination set that goes to web1.mydomain.com so that it points to webserver of (10.10.0.1 resolve web1.mydomain.com of internal DNS) and FQDN is a must.

IS MY OPINION CORRECT? i don't look from internal. i am looking from external assuming i am the external user from internet.

Please give a comment..

Thanks clive.

(in reply to BenYB)
Post #: 14
RE: Page Not Found (Connection refused) - 28.Aug.2003 2:19:00 AM   
camos

 

Posts: 70
Joined: 17.Aug.2003
Status: offline
BenYB,

I thought I had made it straight a couple of times. [Wink]

From the beginning: Scene 1
- External client enters http://mydomain.com,
- Registrars DNS name servers point mydomain.com to IP 202.152.78.125
- ISA receives request on external IP 202.152.78.125
- Internal DNS points http://mydomain.com to internal IP 10.0.0.1
- ISA redirects to the mydomain site on IIS at internal IP 10.0.0.1

From the beginning: Scene 2
- External client enters http://WebSite1.mydomain.com,
- Registrars DNS name servers point mydomain.com to IP 202.152.78.125
- ISA receives request on external IP 202.152.78.125
- Internal DNS points http://WebSite1.mydomain.com to internal IP 10.0.0.10
- ISA redirects to the WebSite1 site on IIS at internal IP 10.0.0.10

From the beginning: Scene 3
- External client enters http://WebSite2.mydomain.com,
- Registrars DNS name servers point mydomain.com to IP 202.152.78.125
- ISA receives request for http://WebSite2.mydomain.com on external IP 202.152.78.125
- Internal DNS points http://WebSite2.mydomain.com to internal IP 10.0.0.11
- ISA redirects to the WebSite2 site on IIS at internal IP 10.0.0.11

DNS is resolved from right to left - com. then mydomain. then WebSite1.

Your stated opinion is not quite right.
- You need a Destination Set and a Web Publishing Rule for mydomain.com
- You need a Destination Set and a Web Publishing Rule for WebSite1
- You need a Destination Set and a Web Publishing Rule for WebSite2

In my example there are 3 sites published and each will need an internal DNS entry, a Destination Set and a Web Publishing Rule. If you only want to publish one Website then it should be mydomain.com

Cheers,
Clive

(in reply to BenYB)
Post #: 15
RE: Page Not Found (Connection refused) - 28.Aug.2003 2:52:00 AM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
I am a little bit confused.

you said that the domain of external such as http://mydomain.com resolve an external ip address of 202.152.78.125. Thats' for http://www.mydomain.com. ok..so far so good

And then, you also said for your next scene, when you point http://website1.mydomain.com, it also use an external ip address of 202.152.78.125 and point to internal web website1(10.10.0.10). how would you that? i need to know the configuration.

so, i don't have to get an ip address for website1.mydomain.com

thanks clive.

(in reply to BenYB)
Post #: 16
RE: Page Not Found (Connection refused) - 28.Aug.2003 3:48:00 AM   
camos

 

Posts: 70
Joined: 17.Aug.2003
Status: offline
BenYB,

Previously I mentioned how DNS is read from left to right. The significance of that is the Registrars root servers resolve com. to a pair of primary and secondary DNS servers (usually belonging to your ISP but also could be a DNS re-director service like tzo or easyDNS) which resolves mydomain. to your external IP.

When ISA receives a request for mydomain it will look for a Publishing Rule that gets its information from your internal DNS and the Destination Set for mydomain which points to IIS 10.0.0.1.

When ISA receives a request for WebSite1.mydomain it will look for a Publishing Rule that gets its information from your internal DNS and the Destination Set for WebSite1 which points to IIS 10.0.0.10.

Through the magic of DNS and ISA Server you can publish an unlimited number of Web sites through only one external IP. ISA receives the request for other subdomain type sites and directs it to a designated internal IP. The internal IP's are free to use and unlimited in number.

So you are right, you do not have to get an external public IP for WebSite1.mydomain.com nor do you have to register the name WebSite1 with an Internet authority. Internal names like WebSite1 must be unique to your internal network but they do not need to be unique to the Internet as mydomain.com does. This means that WebSite1.someotherdomain.com is unique and different from WebSite1.mydomain.com.

Does that help?

Clive

(in reply to BenYB)
Post #: 17
RE: Page Not Found (Connection refused) - 28.Aug.2003 3:42:00 PM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
Thank you...I get you meant in our discussion so far...

Thank you clive...

(in reply to BenYB)
Post #: 18
RE: Page Not Found (Connection refused) - 28.Aug.2003 5:01:00 PM   
BenYB

 

Posts: 39
Joined: 17.Aug.2003
From: Brunei
Status: offline
Hello, I am back again.

Clive,

Can i use url redirected such as from cjb.net to have like this domain http://web1.project96.cjb.net in order external user request my internal website1.mydomain.com ?

(in reply to BenYB)
Post #: 19
RE: Page Not Found (Connection refused) - 29.Aug.2003 7:43:00 AM   
camos

 

Posts: 70
Joined: 17.Aug.2003
Status: offline
BenYB,

You are complicating matters but yes http://web1.project96.cjb.net can be used if web1.project96 is correctly configured in your DNS server zones. You will need to create a subdomain called project96 and make web1 part of it.

I think before you go wild with subdomains you should think about what it is you are trying to accomplish and get the simpler configuration working first.

Cheers,
Clive

(in reply to BenYB)
Post #: 20

Page:   [1] 2   next >   >> << Older Topic    Newer Topic >>
All Forums >> [ISA Server 2000 General] >> Web Publishing >> Page Not Found (Connection refused) Page: [1] 2   next >   >>
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts