IP Address Control

[Ryan Hale]

Hi everyone -

To my knowledge - here is everything that has been running on that server and where it is (or where it is telling me) it is running:

Frontier - 66.221.37.205:80
LiveStats - 66.221.37.205:8080
IMail Web Messaging Email Server - 66.221.37.205:8383
IIS - 66.221.37.206:81

I looked through all of the services running on the server and there were a number of other programs and databases that were running in the background that IMail and LiveStats were dependent on.  I've shut all of these as well as LiveStats and IMail down so now we've isolated it down to Frontier and IIS.

I changed the port from 81 to 80 and restarted IIS, but it is still telling me that the Address is in Use.

**********************

By the way, when I check 66.221.37.206:80 - with Frontier started and running at 66.221.37.205:80 -at Rex's HTTP viewer (thanks Matt!), I get...

Cannot connect to 66.221.37.206:80: Connection refused

With Frontier turned off and IIS started and I check 66.221.37.206:80, I get...

HTTP/1.1·200·OK(CR)
(LF)
Server:·Microsoft-IIS/5.0(CR)
(LF)
Content-Location:·http://66.221.37.206/Default.htm(CR)

***********************

So here is my bottom line question (and this may have to be answered by someone at Userland)...  Is it possible that Frontier could somehow claim both of my IP addresses, but then only listen on the one that I have told it to, in this case 66.221.37.205?  I would think this would be consistent with the results that I have been getting so far...

Thanks!

Ryan Hale
636.561.3403 
ryan.hale at levistable.com

http://www.ryanjhale.com
http://www.levistable.com



---------- Original Message ----------------------------------
From: "Matt Mower" <matt at novissio.com>
Reply-To: Frontier-Users at userland.com
Date:  Mon, 9 Sep 2002 08:27:59 +0100

Hi folks,

Pardon my jumping in but I thought the following might help:

Rex Swain's HTTP Viewer [http://www.rexswain.com/httpview.html]
URL = http://66.221.37.206:81/
FMT = AUTO
REQ = HEAD 
Sending request:
HEAD / HTTP/1.0
Host: 66.221.37.206

. Finding TCP protocol...
. Binding to local socket...
. Connecting to host...
. Sending request...
. Receiving response...

Total bytes received = 281
Elapsed time so far: 0 seconds 
Header (Length = 281):
HTTP/1.1.200.OK(CR)
(LF)
Server:.Microsoft-IIS/5.0(CR)
(LF)
Content-Location:.http://66.221.37.206:81/Default.htm(CR)
(LF)
Date:.Mon,.09.Sep.2002.07:28:03.GMT(CR)
(LF)
Content-Type:.text/html(CR)
(LF)
Accept-Ranges:.bytes(CR)
(LF)
Last-Modified:.Sat,.07.Sep.2002.14:08:47.GMT(CR)
(LF)
ETag:."307a23157856c21:91b"(CR)
(LF)
Content-Length:.146(CR)
(LF)
(CR)
(LF)

Done


Regards,

matt

> -----Original Message-----
> From: frontier-users-admin at userland.com 
> [mailto:frontier-users-admin at userland.com] On Behalf Of David A. Bayly
> Sent: 09 September 2002 08:19
> To: Frontier-Users at userland.com
> Subject: Re: IP Address Control
> 
> 
> Ryan,
> 
> I see a different response when I telnet to 66.221.37.206:81. It 
> identifies itself as Microsoft sever. Just for sanity check I then 
> telneted into  a known frontier server. Another different response. 
> So whatever answered me on port 80 wasn't either of these servers.
> 
> So you are running at least one more web server application. I don't 
> know enough about Windows to guess what it might be. Perhaps someone 
> else can take a guess.
> 
>