The only NT server here is blocked COMPLETELY at the firewall. No in and no out. It is only used internally as a file server and (Blech!) as a Windows messaging server..
TimH > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Leo Clark > Sent: Friday, October 19, 2001 10:44 AM > To: eug-lug > Subject: [EUG-LUG:3317] Re: Windows Networking traffic... > > > FYI. If your useing Windows 2000 and Active Directory you > might want to > look at closeing a couple other ports: > > kerberos 88 Kerberos Secure Authentication > ldap 389 Lightweight Directory Access Protocol > kpassw 464 Kerberos Passwords > msft-gc 3268 Microsoft Global Catalog > msft-gc-ssl 3269 Microsoft Global Catalog with LDAP/SSL > > --------------<<<((((((0))))))>>>-------------- > Leo Clark > [EMAIL PROTECTED] > > > On Fri, 19 Oct 2001, Kahli R. Burke wrote: > > > Tim, > > > > If you've got the router or firewall set to drop these > packets, that > > should do it. There isn't anything you need to do on the > clients. I > > would try a test on a client to make sure the router/firewall is > > configured properly. > > > > > > Kahli > > > > Tim Howe wrote: > > > > >I currently prevent traffic on ports 137-139 from leaving > our network. > > >Is there anything else that must be blocked to prevent > this traffic from > > >leaking out? > > > > > >TimH > > > > > > > > > > >
