Accessing file shares with NETBIOS disabled

  • Thread starter Thread starter Gary
  • Start date Start date
G

Gary

2 Win2k adv servers in a workgroup. There is a requirement
to disable NetBIOS over TCP/IP. 1 machine hosts a file
share and the other one cannot access this share? Have a
hosts entry for the server yet it just does not seem to be
able to resolve the name. Have read that win2k network
programs can use both NetBIOS and Winsock APIs. Is there
anything else I need to do to get the name resolution
performed by DNS? Do I have to have a DNS server opposed
to hosts file entries? Do you still need the browser
service running?

Many thanks
 
Gary said:
2 Win2k adv servers in a workgroup. There is a requirement
to disable NetBIOS over TCP/IP. 1 machine hosts a file
share and the other one cannot access this share? Have a
hosts entry for the server yet it just does not seem to be
able to resolve the name. Have read that win2k network
programs can use both NetBIOS and Winsock APIs.

You should be able to use FQDNs or IP addresses:

net use \\146.23.44.12\share
or
net use \\server1.domain.com\share
Is there
anything else I need to do to get the name resolution
performed by DNS?

If you want to use just the hostname and not the FQDN,
use DHCP option 15 to put in your domain name. By
default, TCP/IP will append this as a suffix to a bare
host name.

If your servers have more than domain.com in their
suffix, (e.g. server1.subnet.domain.com) in
TCP/IP settings -> advanced -> DNS -> append these
DNS suffixes in order. Put in the possible DNS suffixes
for the hosts you want accessed.
Do I have to have a DNS server opposed
to hosts file entries?

You can do it with host file entries
Do you still need the browser
service running?

If you do not have NBT, browsing will not work.
 
Cheers Matt

I have tried using 'net use' with both the FQDN and the IP
and I just get network error 67 which is 'Network name
cannot be found'. I am not using DHCP but static IPs. Are
there any other services that need to be running on either
box for network comms to work using DNS resolution? I have
the Workstation and DNS Resolver service running on both
boxes and the Server service obviously running on the
machine that hosts the file share. Are there any other
services that need to be running?

Gary
 
Gary said:
Cheers Matt

I have tried using 'net use' with both the FQDN and the IP
and I just get network error 67 which is 'Network name
cannot be found'. I am not using DHCP but static IPs. Are
there any other services that need to be running on either
box for network comms to work using DNS resolution? I have
the Workstation and DNS Resolver service running on both
boxes and the Server service obviously running on the
machine that hosts the file share. Are there any other
services that need to be running?

Can you ping from one box to the other, using both FQDN and
IP addesses?

On the server doing the sharing, what do you get when you
do a 'net share' from the command line?
 
Can ping each machine from its neighbor using both IP
address and FQDN. 'net share' on the sharing machine lists
the admin shares and standard shares that I have set up?
Bloody weird. Appreciate your replies, is there anyother
services that need to be running?
 
2 Win2k adv servers in a workgroup. There is a requirement
to disable NetBIOS over TCP/IP. 1 machine hosts a file
share and the other one cannot access this share? Have a
hosts entry for the server yet it just does not seem to be
able to resolve the name. Have read that win2k network
programs can use both NetBIOS and Winsock APIs. Is there
anything else I need to do to get the name resolution
performed by DNS? Do I have to have a DNS server opposed
to hosts file entries? Do you still need the browser
service running?

Many thanks

I have the exact problem from one of our fileservers. When I disable
Netbios I cant map a share. When I the type netstat -n it seems that
the smb port(445) is closed. But on the other servers it responds
fine. I believe it is the server service that will start it, and I
dont know how to get it to work. Try it on your server and see if its
the same problem.
 
Gary said:
Can ping each machine from its neighbor using both IP
address and FQDN. 'net share' on the sharing machine lists
the admin shares and standard shares that I have set up?
Bloody weird. Appreciate your replies, is there anyother
services that need to be running?

the client has to be running workstation. Also, do you have
"client for Microsoft Networks" component bound to the client's
LAN adapter? And "File and Print Sharing for Microsoft Networks"
component bound to the server's adapter?
Network Connection->properties->networking

Can you do a
net view \\sevename
from the client and get a response from the server?


--
Matt Hickman
IOWA RAISES VOTING AGE TO FORTY-ONE
Rioting on Des Moines Campus
Robert A. Heinlein (1907 - 1988)
_Methuselah's Children_ ASF c.1941
 
Back
Top