The 66...209 address was the original address for this machine and has
functioned soundly as a mail/web server for the past 12 months.  The 64...39
IP was added as an additional NIC/IP combination just recently.  Also, I am
not sure if it is related, but today I went over the logs thoroughly and
found that the POST server is using 65.117.116.209 when it calls the
internal templates (Report Post Status, Data, etc).  65.117.116.209 has not
existed on this machine for more than 12 months!  Where could the POST
server possibly be getting this address?

We are using Windows 2000 Server with dual NIC cards, and the second NIC was
added at the same time as the new IP address, which was just a few weeks
ago.  We have web sites running successfully through both IP addresses on
the same server.


Regards,
Raven


-----Original Message-----
From: Howie Hamlin [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 21, 2003 1:07 PM
To: inFusion Support List
Subject: Re: [iMS] post server logging and unmatched received headers


Is 66.202.57.209 configured in Windows properly for connection to the
Internet?  The address that iMS prints in the log
file is the address that it requests for use and Windows may override the
request.

Regards,

Howie

----- Original Message -----
From: "Raven R. Cecil" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Friday, February 21, 2003 1:20 PM
Subject: RE: [iMS] post server logging and unmatched received headers


> Yes.
>
>
> Regards,
> Raven R. Cecil
>
>


==^=======================================================
     This list server is Powered by iMS
   "The Swiss Army Knife of Mail Servers"
   --------------------------------------
To leave this list please complete the form at 
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^=======================================================


Reply via email to