Can 98 client log on to 2000 server with netbios disabled.

  • Thread starter Thread starter John
  • Start date Start date
J

John

Upgraded a department to xp with the exception of one 98
machine that must stay on the network? I would like to
turn netbios off and use dns for resolution. When I turn
netbios off in the tcp/ip configuration of the server
adapter,the 98 machine can no longer log on to the server.
Is there a keep netbios turned off on the server and still
allow 98 computers to log on?
 
Unfortunately, W9x and NT4 need NetBIOS for this functionality. So you'll
have to keep it enabled until you get rid of the 9x machines, unless of
course, there are other apps or services running that require NetBIOS.

Do you have any apps that require NetBIOS? Good way to test it is to disable
it for a couple days and watch what happens, unless you're familiar with
your installed apps' requirements.

Do you or your users require Network Neighborhood to be functional? How
about connection by UNCs, such as \\computername\share ? Mapped drives by
connecting to it's UNC by computer name and not FQDC? How about Outlook 2000
connecting to an Exchange 55 server? All those features require NetBIOS too.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Nothing else requires netbios - I've had it disabled
until it was pointed out to me that we had one
workstation that required 98 due to a propietary card on
the pc that will not run on 2k or above. It is the only
98 machine left in this department - I have netbios over
tcp/ip disabled on all the xp workstations and was hoping
to improve security by keeping it disabled on the
server. Doesn't look possible. The 98 machine doesn't
need network neighborhood. Are you saying that I could
use a unc path to connect to a mapped drive on the server
with netbios disabled? I believe I tried that but
received the error that I had to be logged on. Of
course, with nebios disabled, I wasn't able to logon.
Thanks for your prompt reply - saved much loss of time
and frustration.
 
John said:
Nothing else requires netbios - I've had it disabled
until it was pointed out to me that we had one
workstation that required 98 due to a propietary card on
the pc that will not run on 2k or above. It is the only
98 machine left in this department - I have netbios over
tcp/ip disabled on all the xp workstations and was hoping
to improve security by keeping it disabled on the
server. Doesn't look possible. The 98 machine doesn't
need network neighborhood. Are you saying that I could
use a unc path to connect to a mapped drive on the server
with netbios disabled? I believe I tried that but
received the error that I had to be logged on. Of
course, with nebios disabled, I wasn't able to logon.
Thanks for your prompt reply - saved much loss of time
and frustration.
Click to expand...
 
John said:
Nothing else requires netbios - I've had it disabled
until it was pointed out to me that we had one
workstation that required 98 due to a propietary card on
the pc that will not run on 2k or above. It is the only
98 machine left in this department - I have netbios over
tcp/ip disabled on all the xp workstations and was hoping
to improve security by keeping it disabled on the
server. Doesn't look possible. The 98 machine doesn't
need network neighborhood. Are you saying that I could
use a unc path to connect to a mapped drive on the server
with netbios disabled? I believe I tried that but
received the error that I had to be logged on. Of
course, with nebios disabled, I wasn't able to logon.
Thanks for your prompt reply - saved much loss of time
and frustration.
Click to expand...

Sure, you can connect using a UNC without NetBIOS. Use the FQDN or the IP:
\\machine.domain.com\share
or
\\192.168.5.20\sharename

But I guess you have to deal with the 9x issue. Their authentication
mechanism is based on NTLM, which requires NetBIOS. No way around that,
unfortunately.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
This is a complex issue: the NetBIOS resolution sequence is \\IP no DNS
name? no "do a WINS lookup" WINS no "do three broadcasts" Broadcast no "is
LMHOST enabled" (if yes lookup name in LMHOST) no use DNS for Windows name
resolution no FAILURE.

If the last step "use DNS for Windows name resolution" is yes than look up
the name in HOST no lookup NetBIOS name with domain name attached with DNS
and if that fails try just the NetBIOS name no FAILURE.

See how NetBIOS is last in the sequence.

This is the sequence a 98 client would execute to find a HOST.

HINTS:
Check IP with the ping command, take a look at with the "net view" comand.
Check the NetBios status "nbtstat -c" command clear the cache "nbtstst -R.
IF the name is just an IP use the "net use * \\198.168.0.0\somthing" or
substitute the server for the IP. check your Wins and DNS client settings.
Reserve a IP and pull the DHCP auto enable settings.

You need to shut down the NetBIOS and configure the 98 machine to use one of
the other methods. I have a network with 95, 98, 2000, and XP and it is all
TCP/IP so its possible.

SAM
 
In
Samuel Thomsen said:
This is a complex issue: the NetBIOS resolution sequence is \\IP no
DNS name? no "do a WINS lookup" WINS no "do three broadcasts"
Broadcast no "is LMHOST enabled" (if yes lookup name in LMHOST) no
use DNS for Windows name resolution no FAILURE.

If the last step "use DNS for Windows name resolution" is yes than
look up the name in HOST no lookup NetBIOS name with domain name
attached with DNS and if that fails try just the NetBIOS name no
FAILURE.

See how NetBIOS is last in the sequence.

This is the sequence a 98 client would execute to find a HOST.

HINTS:
Check IP with the ping command, take a look at with the "net view"
comand. Check the NetBios status "nbtstat -c" command clear the cache
"nbtstst -R. IF the name is just an IP use the "net use *
\\198.168.0.0\somthing" or substitute the server for the IP. check
your Wins and DNS client settings. Reserve a IP and pull the DHCP
auto enable settings.

You need to shut down the NetBIOS and configure the 98 machine to use
one of the other methods. I have a network with 95, 98, 2000, and XP
and it is all TCP/IP so its possible.

SAM
Click to expand...

So Sam, you're saying change the provider order?

So you're saying that NetBIOS is disabled on your servers and domain
controllers and your 9x machines are logging in to the domain?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top