| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: NetBIOS Over TCP/IP in domain. |
From: "Hrvoje Mesing"
"Chris" wrote in message
news:4288b734$1{at}w3.nls.net...
> Disclaimer: This is not my strongest area...YMMV
>
> M.,
>
> I am not sure that you can disable NetBIOS in a native AD domain. Isn't
> NetBios one of the fundamental protocols (even running over TCP/IP) of
> windows networking? We're running into problems with needing Wins servers
> to deal with the fact that Netbios (in a non-windows domain environment)
> won't cross subnets/routers.
-+-
Main DC/GC and Fileserver got it's NetBIOS o TCP/IP disabled + few Workstations.
Well, for now I see no Hard anomalies.
Everything that uses Browsing, like DameWare "Workstation"
enumeration and Add/Remove Printer > Connect to printer is not working
properly.
Still, normal communication is working nicely. DameWare Computers shows all
found computers, DameWare AD browsing works nice.
Add/Remove Printer > when used with "Browse Directory" works
as it should Add/Remove Printer > "Connect to printer..." is
working Ok if \\printserv_FQDN\.. is given.
Minor problem with Group policy softW. Installation (computer
configuration) but rather strange.
If Share to application is given in \\netbios_name\ and DC on which the
same share resides is not using NetBIOS will not work as should. Meaning,
softW. package will sometimes install, sometimes wont. Event Log and All of
the AppMgmt*, MSI*, etc. logs shows or Access denied errors, or cannot read
file *, or something similar. If the same share path is given in
\\name_FQDN\.. format, everything works perfect.
Now, same test performed on Win2K and Win2K3 with NetBIOS and without NetBIOS.
If share \\netbios_name\.. is used then there is no rule in either
configuration. Sometimes it will install, sometimes not. Everything else is
working wonderful.
If share \\name_FQDN\.. is used, it will work as expected every time!
This is very, very strange, I tested this in lotta configurations and found
unsolved problems on the *Google*.
Also, found some similar explanation from MS, still, it is involving NT 4.0
explicitly (which I do not use) and Kerberos.
Summary:
- MS is encouraging NetBIOS off
- there are no big problems for now.
- Main DC/GC/FS/PS is running in 250+ computers environment.
- All services in LAN + Exchange are working as expected.
I will continue testing for sometime.
Thank You,
-+-
M.
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)SEEN-BY: 633/267 270 5030/786 @PATH: 379/45 1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.