Disabling NetBios over TCP/IP

  • Thread starter Thread starter mike
  • Start date Start date
M

mike

I would like to know what will be the effect if I disable
Netbios over TCP/IP in our environment. I would like to
disable this so I can close ports 138 and 139.

Please help me.

Thanks,

Mike
 
I would like to know what will be the effect if I disable
Netbios over TCP/IP in our environment. I would like to
disable this so I can close ports 138 and 139.

Please help me.

Thanks,

Mike
Click to expand...

Hi

You don't need to disable it if you have a firewall. If you have a LAN
you'll lose the ability to address PCs by Netbios name and, AFAIK, that's
all you'll lose. If you have multiple NICs installed then you only need to
unbind it from the internet connected NIC.

Regards

Bill
 
Mike,

Depends on what services are you running on your network...
If these are native tcp/ip services, like iis, dns & so on, then you can and
should.
On the other hand, if you have MS networking (ie. shares, wins), you *must*
re-plan your network.
Consider an intranet environment, based on pure tcp/ip, where "shares" are
provided as "downloads" in departmental sites.

Regards,
damned
 
Browsing will no longer function
Applications that depend on NetBIOS will no longer work.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Only recommended in pure W2K/XP Pro/W2003 networks where no applications
rely on netbios names and you do not plan on using My Network Places to
access shares. --- Steve
 
microsoft.public.win2000.security news group, Steven L Umbach <n9rou@no-
spam.ameritech.net> says...
Only recommended in pure W2K/XP Pro/W2003 networks where no applications
rely on netbios names and you do not plan on using My Network Places to
access shares.
Click to expand...

Or restricting which workstations a user is allowed to logon to by using
the Log On To option for a user account, or using clustering, etc, :-)
 
Back
Top