*Hobbit's white paper on CIFS security has more detail than you'll
ever want to know on CIFS, which will probably lead you to an
understanding that you need to allow some traffic on port 137 to get
browse working.
Adam
ftp://ftp.avian.org/avian/papers/cifs.txt
Roger Marquis wrote:
| We've successfully firewalled an NT fileserver using the TIS firewall
| toolkit, v2.0 plug-gw on port 139. The problem is only Unix clients can
| access these shares/filesystems (using samba), Win95 clients cannot.
|
| Because the NT server checks the servername as well as sharename of each
| query we've edited the local LMHOSTS files so that the NT servername is
| mapped to the firewall's IP address. However, although we see traffic
| going to and from the NT server, all our Win95 clients fail to mount the
| share.
|
| Are there any white papers on firewalling NT SMB filesystems?
|
| Roger Marquis
|
--
He has erected a multitude of new offices, and sent hither swarms of
officers to harrass our people, and eat out their substance.
References:
|
|
