Discussion Locked

netbeui

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm still kind of a newbie but...
Currently my office runs a single domain network. My Sys Admin has asked
me to find a way to run our network without netbeui. Every time we take it off
a machine it no longer has connectivety. Is there a way around this so we can run pure
TCP/IP. As a little background we run four servers 3 mains and a backup
with about 120 clients and 4 network printers

14 replies

by tamj123

I think easist way to setup tcp/ip is using dhcp server.
first make sure both server and workstation has tcp/ip protocol install.
second install dhcp on one of nt server, and setup the tcp/ip pool.
on the nt client make sure you select obtain ip address from dhcp server option under network properties.
get jetdirect for your printers

by tmaclennan

Without netbeui you will need to set up an lmhosts file that resolves the names of your servers (and any pcs offering services) and printers to their IP addresses. Put that on each PC and on the servers.

by tmaclennan

If your Sys Admin is asking you to find the way to do this, what is his job? Is he trying to get you to find a way to fix this on the clients, so he doesn't have to mess with the server? Hmmm.

by avachon

Hi, while netbeui still is running, add the tcp/ip protocol (on both servers and clients). If you do not need internet access you can use reserved addresses such as 192.168.5.x-xx. You can set up dhcp (set up a scope) so your clients will automatically get their ip address. You also can set up wins for netbios to ip name resolution (helps cut down on broadcasts). To test that the tcp/ip stack is installed correctly on servers, test with the loopback address of 127.0.0.1 You then can test connectivity by pinging clients from the server(s) using the client ip address (which you can get by running the command ipconfig /all if nt workstions running dhcp for example - this will tell you client ip address, wins server address, dhcp server address, etc. When wins is set up you should be able to ping clients via their netbios name and receive the icmp replies. For extensive information about setting up tcp/ip, wins, dhcp you'll look at microsoft's website (technet and knowledge base) and search under those labels. When tcp/ip is set up and functional across your domain, go into network|protocols and remove netbeui. Sysadmin probably wants to remove netbeui because a. it is not routable which may become a concern and b. it is very chatty on the wire. Hope this helps you get started.

by avachon

Hi, it's even easier for you since you have dhcp running already. You could use lmhosts for name resolution but that entails setting up a lmhosts file on each client. Better to set up wins as I mentioned translates netbios names to ip addresses (helps further cut down on broadcasts in your network). Typically you'd try to get your connectivity working first - ping a client from the server; ping server-to-server. If connectivity okay, setup wins.

by kjohansson

Sorry. I forgot to mention that we are already running a DHCP server and our clients
do obtain automatically.

by ronnonf

Set up a WINS Server and use DHCP to push out the correct ip address of the WINS Server. Otherwise, get ready for some sneaker.
A little aside WINS translates Netbios names to ip addresses.

by spiceman

Netbeui is a small network protocol ideal for a handful of computers. In your case you should use TCP/IP and if the network is internal (not directly linked to the internet) you can use any ip address combination of node and network e.g. 12.100.100.x

Just uninstall netbeui if you don't need it though you can have several protocols.

You can have a DHCP server to allocate the ip addresses (easier to administer) or fixed ip addresses on each machine.

good luck

This discussion is closed to new replies.