My understanding, that for your NT machines to communicate it
would be all be NetBIOS over TCP/IP so you could open a well known
port (netbios = 138 & 139 ?) That would ALLOW communications, how
you secure that or control it, is another question..
If the NT machines were running other services (ftp or whatever)
that would follow the usual rules.
>>> "Wadzinski, Tom IS" <Tom .
I have a question about TCP/UDP services not supported by a given
firewall. When I search for the right firewall for our org, I
vendors about what happens if I have a service that their firewall
support. With most vendors, they'll say, " Simple, create a
says, basically: Open port xxx for whatever external(untrusted)
you want to be able to communicate with whatever
you want." They act like this is no big deal, but isnt' this
large security risk, just allowing any traffic on a particular
My main goal is to create a fairly secure method of having remote
(who are running NT Workstation 4.0, etc..) access an NT domain
a firewall. If anyone has had success with users using dial-up
networking to login into to an NT domain through a firewall, I
love to hear about it.