Forged hostname eror - old PC name being used??

[archeron]

I have a server to relay email, running on win2K server.
I purchased a new PC to upgrade this server about a month ago.
I built said new server calling it orion2 (the server in production was
called orion)
when the new server went online I took the old one off and then renamed the
new one to orion.

This has worked fine up until now, as I have started getting mail failures
from certain domains.

Mail failure details are:

Reporting-MTA: dns;orion2
Received-From-MTA: dns;pop.mydomain.com
Arrival-Date: Mon, 14 Mar 2005 10:06:01 +0000

Final-Recipient: rfc822;anyone@freeuk.com
Action: failed
Status: 5.0.0
Diagnostic-Code: smtp;550 forged hostname detected in HELO: orion2

As you can see the server name is wrong (orion2), it's showing the name as
it was before I renamed the server.

I think freeuk.com must use something like DeskKnow as a mail server as that
uses the name of the computer for the HELO greeting on SMTP connections,
thus it looks for orion2 which is wrong and tells my mail server to go away.

So, where is this old name still hiding on my server? I
have searched the registry and found no reference to it - I recall a similar
problem with a backup program on another server and found the old computer
name was hiding Environment variables under RNNAME, but I've checked that and the entry isn't there for RNNAME so I added it in but still nothing.

I've also tried a telnet session and when I log-on to my server it shows the old server name!!

I guess this is more a naming Issue with Windows2000 but any help would be very much appretiated!

 

[zbnet]

You're running Exchange 5.5. on orion2?

 

[archeron]

No, Exchange server 5.5 is running on a server called Hubble.

The Orion server is a relay server in the "DMZ" all outgoing mail passes through it as does all incoming mail for virus and spam scanning before it gets to the exchange server.

There is no server called Orion2 anymore, it was renamed, but the error messages refer to this old name and I don't know how or where to change it.

I think my best best is to just take the company email offline for a day while I rebuild the server using the correct serer name from the start instead of changing it
over when it goes "live"

 

[archeron]

It's an NT4 network, not AD.

But thanks anyway - I have fixed the little bugger now!!

It was in IIS settings, I went into my Domain properties for the SMTP server, then delivery tab, then advanced button - in here was written orion2 for my FQDN.

I changed it to orion (the actual server name) but this still gave the same error on sending email - which is strange as it worked fine on the other server.

Anyway I changed it to the proper FQDN (server.mydomain.com)
and it now all works a treat.

I just find it so annoying that microsoft have no mention of this in the knowlegebase, am I really the only one to ever have this problem?