RE: [TCLUG:22973] Samba Exchange Plugins

["Austad, Jay" <austad@marketwatch.com>]

Yes, 138 and 139 stuff still works, but only for backwards compatibility.
If I access a share from my win2k box to another win2k box, it uses only
port 445, nothing else.  I was able to access a share from my box which is
inside the firewall to a box outside.  I wondered why this worked, since
before it required special conduits.  Turns out that it only used port
445/tcp.

Jay

-----Original Message-----
From: Jon Schewe [mailto:jpschewe@eggplant.mtu.net]
Sent: Saturday, October 21, 2000 9:43 AM
To: tclug-list@mn-linux.org
Subject: Re: [TCLUG:22973] Samba Exchange Plugins


"Austad, Jay" <austad@marketwatch.com> writes:

> The protocol that exchange uses between it and it's mail clients is a
> firewall administrators nightmare.  It uses like 3 or 4 different ports,
> both UDP and TCP, and uses RPC (so you have to edit the registry on the
> exchange server to bind the rpc ports to 2 specific ports).  Looks like MS
> is finally starting to think about the firewall nightmares they create,
> win2k uses port 445/tcp for drive/folder sharing now.  It still opens the
> old ones, but you don't need them, it's just for backwards compatibility
> with nt and 9x.

You mean they changed the ports from 138 and 139 to 445?

-- 
Jon Schewe | http://eggplant.mtu.net/~jpschewe
For I am convinced that neither death nor life, neither angels 
nor demons, neither the present nor the future, nor any 
powers, neither height nor depth, nor anything else in all 
creation, will be able to separate us from the love of God that 
is in Christ Jesus our Lord. - Romans 8:38-39


---------------------------------------------------------------------
To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
For additional commands, e-mail: tclug-list-help@mn-linux.org