Ports 139/445

Can anyone tell me if Surgemail is somehow utilizing ports
139 or 445 
on a Windows Server platform?  Specifically Windows 2003.

I have been trying to crank up the security on our server
and when I 
block ports 139 (NetBios) and port 445 (SMB) I lose
connectivity to 
Surgemail.  It will not deliver mail and I can not log into
the 
webmail port.  I am not sure yet whether it is 139 or 445
that leads 
to the problem.  I hesitate to fiddle with the system too
much even 
though it is Sunday and most of the users are not paying
much 
attention.  I did get one call from a client who noticed the
email 
went away for a bit.

More on why I am doing this later.


Orin Wells
Supportawasco.com
253-630-5296 

I'm blocking 139 and 445 on Windows 2000 without issues. I'm
using the IPSec
rules as a firewall.


> -----Original Message-----
> From: Orin Wells [mailto:Orinwellsawasco.com]
> Sent: Sunday, December 03, 2006 4:21 PM
> To: surgemail-listnetwinsite.com
> Subject: [SurgeMail List] Ports 139/445
> 
> Can anyone tell me if Surgemail is somehow utilizing
ports 139 or 445
> on a Windows Server platform?  Specifically Windows
2003.
> 
> I have been trying to crank up the security on our
server and when I
> block ports 139 (NetBios) and port 445 (SMB) I lose
connectivity to
> Surgemail.  It will not deliver mail and I can not log
into the
> webmail port.  I am not sure yet whether it is 139 or
445 that leads
> to the problem.  I hesitate to fiddle with the system
too much even
> though it is Sunday and most of the users are not
paying much
> attention.  I did get one call from a client who
noticed the email
> went away for a bit.
> 
> More on why I am doing this later.
> 
> 
> Orin Wells
> Supportawasco.com
> 253-630-5296
> 

Orin Wells wrote:
> Can anyone tell me if Surgemail is somehow utilizing
ports 139 or 445
> on a Windows Server platform? Specifically Windows
2003.
>
> I have been trying to crank up the security on our
server and when I
> block ports 139 (NetBios) and port 445 (SMB) I lose
connectivity to
> Surgemail. It will not deliver mail and I can not log
into the webmail
> port. I am not sure yet whether it is 139 or 445 that
leads to the
> problem. I hesitate to fiddle with the system too much
even though it
> is Sunday and most of the users are not paying much
attention. I did
> get one call from a client who noticed the email went
away for a bit.
>
> More on why I am doing this later.
>
>
> Orin Wells
> Supportawasco.com
> 253-630-5296
>
I am guessing it matters if your server's os is using either
for name
resolution as Surgemail doesn't use either and DNS is on
port 53(tcp & udp).

Orin Wells wrote:
> Can anyone tell me if Surgemail is somehow utilizing
ports 139 or 445 on 
> a Windows Server platform?  Specifically Windows 2003.

It shouldn't use those ports at all unless you have set it
to use them.

Regards,
Stuart

> 
> I have been trying to crank up the security on our
server and when I 
> block ports 139 (NetBios) and port 445 (SMB) I lose
connectivity to 
> Surgemail.  It will not deliver mail and I can not log
into the webmail 
> port.  I am not sure yet whether it is 139 or 445 that
leads to the 
> problem.  I hesitate to fiddle with the system too much
even though it 
> is Sunday and most of the users are not paying much
attention.  I did 
> get one call from a client who noticed the email went
away for a bit.
> 
> More on why I am doing this later.
> 
> 
> Orin Wells
> Supportawasco.com
> 253-630-5296
> 


-- 
When replying please quote original message to save time and
always let
us know what OS and version of SurgeMail you are using.

************************************************************
****************
If you wish to communicate with other users and talk about
SurgeMail and
also get news about updates etc then join the SurgeMail
List.
Send an email to surgemail-list-requestnetwinsite.com with only 
"subscribe" in the message body

FAQ - http
://www.netwinsite.com/surgemail/help/faq.htm
************************************************************
****************