From: "Glenn Meadows" 

Update on this problem:

There were port mapping problems in the Netopia Router from the DSL
provider that were finally resolved on Friday.  It appears when the router
was initially configured, there were some "strange" port mappings
going on.  It took some serious digging by Scott and a tech from their
provider (Megapath I think), to track down where things were going awry.

Installing 2K server, obviously, had no effect on clearing the problem, as
it was at the entrance to the office where things were strange.

--

Glenn M.
"Hrvoje Mesing"  wrote in
message news:428f781f{at}w3.nls.net...
>
> "Scott"  wrote in message
> news:428c9ee8{at}w3.nls.net...
>> Well...
>>
>>
>> NOthing worked. And I mean nothing. I couldn't even ping my loopback
>> address at port 25. And, as a noble friend said to me, "trying to solve
>> the WHY, when sometimes it's easier and quicker to change paths and go
>> with a different solution (different server OS), then at a later time,
>> re-focus on why the other didn't work. "
>>
>> I'm going to blow out that last install and then see what happens. If the
>> new one doesn't go well, I'll retro to 2K server and let the chips fall
>> where they may.
>
>
> ---
>
>
> use portQry_v2 (beside netstat -aNo) to catch port :25 bindings.
> Also, use netmon, netcap, tcpdump, etc. to catch possible traffic to and
> from :25 to get the picture of what is going on.
>
> If You still cannot get to the bootom, use TCPIPFix, reinstall TCP
> catalogs with netsh or reinstall TCPIP with loading the protocols *.inf
> catalog and selecting to reinstall TCP/IP.
>
> Reverting to the Win2K will not solve the problem.
> Also, check for the application logs (which is trying to use :25 -
> SurgeMail) it will have a Debug log of what break the binding to :25.
>
>
> ---
> M.
>

--- BBBS/NT v4.01 Flag-5