This looks like an emerging issue specific to Win2003 SP1 on Dual-Homed
servers.
We are having same EXACT problem on an IIS box (not Exchange).
Look at these posts:
Windows Server 2003 Community Forum
Posting Category: Windows Server Networking
Search: SP1
Posting: 4/21/05 "Strange behavior" by Dennis P. Smith
Windows Server 2003 Community Forum
Posting Category: IIS General
Search: SP1
Posting: 4/21/05 "IIS Problem after SP1 in windows 2003" by Carlos
IIS-Resources.com Forum
http://www.iis-resources.com/modules...forumpost16979
Note: This is our description of the same problem, originally posted on an
independent IIS Forum (moderated by 3 IIS-MVPs)
"Backup" wrote:
> Well I attempted to correct the problem "AGAIN" this will be the 2nd time I
> had to do this.
>
> What I did was remove all the IP addresses from the network interface, then
> I added them once more and wow look at that it's working again. I did this
> one time before, about 5 days ago. I want to see if this problem happens
> again as I don't know why I happens in the 1st place.
>
>
>
> I know some might say well you're traversing two subnets in one card. etc.
> But it should work with out any issues as my internal network and DMZ
> network aren't out on the public internet, thus no breach in network traffic
> security there.
>
>
>
>
>
>
> "seth" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> >i will guess that uninstalling sp1 will fix the issue
> > i had removed sp1 from one server after my trendmicro products that use a
> > web interface didn't work properly; they would fail with numerous cgi
> > application errors. the interface was fine after dumping sp1
> >
> > "Backup" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> >> Help.
> >>
> >> I have server 2003 with exchange server 2003, from the day I updated to
> >> SP1 I seemed to start having problems.
> >>
> >>
> >>
> >> For one the system is configured with two IP addresses, one for the
> >> internal network and the other for our DMZ, the DMZ IP address has
> >> traffic forwarded to it so that I can serve http email for OWA and so the
> >> server can receive email on port 25.
> >>
> >>
> >>
> >> It seems that now this doesn't happen. If I attempt to connect from
> >> outside I just sits there, no connection is made what so ever.
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>
>