TCP/IP slower than NetBEUI...?

  • Thread starter Thread starter Kenneth
  • Start date Start date
K

Kenneth

Howdy,

Under Win 2000 Pro, we had been running both NetBEUI (as default for
the intranet) and TCP/IP for Internet on our five node network. We run
the systems through a switch and router.

We were advised to eliminate the NetBEUI and decided to give that a
try.

Now that we have eliminated the NetBEUI, we find that opening shared
files is incredibly slow, with some taking three or four times as long
to open as they did before the change to TCP/IP.

What might cause that problem, and are there things we might do to
speed things up?

Sincere thanks,
 
Most likely Name Resolution. First thing to check is your Internal DNS. TCP
relies on DNS. You need a Local DNS server for Your Network. Not to be
confused with your ISPs DNS. Personally if you have no servers to load DNS
on I would stay with NetBEUI. Or you could setup HOSTS files on all your
machines to resolve names for your network. Do a search of your HD for HOSTS
Open it in notepad and follow the instructions.
Good Luck
 
Most likely Name Resolution. First thing to check is your Internal DNS. TCP
relies on DNS. You need a Local DNS server for Your Network. Not to be
confused with your ISPs DNS. Personally if you have no servers to load DNS
on I would stay with NetBEUI. Or you could setup HOSTS files on all your
machines to resolve names for your network. Do a search of your HD for HOSTS
Open it in notepad and follow the instructions.
Good Luck
Click to expand...

Hi Yor,

I thank you for your suggestions...

In your opinion, is there any downside to using NetBEUI for intranet,
and TCP/IP for Internet?

Thanks again,
 
Hi Yor,

I thank you for your suggestions...

In your opinion, is there any downside to using NetBEUI for intranet,
and TCP/IP for Internet?

Thanks again,
Click to expand...

Hello again,

I just tried the Hosts file suggestion on all the machines.

The improvement is dramatic.

Thanks again,
 
Glad to help. I have NetBUIE on all my network machines, mainly because we
still run some Win9x systems, and they seem to work better that way. And
NetBUIE can not get pass the firewall so any machine I want to limit from
the Internet I just remove TCP, then they can see the local network but can
not find the internet.
With TCP you need a method of name resolution as you have seen. With only a
few workstations HOSTS files will do the job. But as you add more clients
you really need your own DNS sever or else updating the HOSTS files can be a
pain.

Two other points to consider.
A. If you do have any Win9x machines remove the SPX protocol, it will have
been installed by default, and will degrade the network traffic. You do not
need unless you have a Novel Server running on your system.
B. The newer Microsoft Systems do not support NetBUIE, So in the future you
will Have to decide on some form of name resolution.

Good Luck...yor
 
Glad to help. I have NetBUIE on all my network machines, mainly because we
still run some Win9x systems, and they seem to work better that way. And
NetBUIE can not get pass the firewall so any machine I want to limit from
the Internet I just remove TCP, then they can see the local network but can
not find the internet.
With TCP you need a method of name resolution as you have seen. With only a
few workstations HOSTS files will do the job. But as you add more clients
you really need your own DNS sever or else updating the HOSTS files can be a
pain.

Two other points to consider.
A. If you do have any Win9x machines remove the SPX protocol, it will have
been installed by default, and will degrade the network traffic. You do not
need unless you have a Novel Server running on your system.
B. The newer Microsoft Systems do not support NetBUIE, So in the future you
will Have to decide on some form of name resolution.

Good Luck...yor

Kenneth said:
Hello again,

I just tried the Hosts file suggestion on all the machines.

The improvement is dramatic.

Thanks again,
Click to expand...

Hi Yor,

The updating of the Hosts file was actually extremely easy because all
the systems share everything: I just updated one, and then pasted it
to the others. Of course, that approach might not be appropriate with
a larger net, but for our small office, it worked just fine.

All the best, and thanks again,
Click to expand...
 
Yor Suiris said:
With TCP you need a method of name resolution as you have seen. With only a
few workstations HOSTS files will do the job. But as you add more clients
you really need your own DNS sever or else updating the HOSTS files can be a
pain.
Click to expand...

Not the case. Name resolution works just fine without WINS or DNS when
running only TCP/IP. Netbios Naming does *not* require NetBEUI. Netbios
Naming with TCP/IP will not work across subnets unless you use WINS, but
NetBEUI will not work across subnets at all,...so you get the same "effect"
with TCP/IP as NetBEUI without any means of "naming resolution" yet with
less limitations.

TCP/IP is also not functional across the Internet if you use RFC Private
Addresses which creates the identical situation as with NetBEUI. The Proxy
or NAT Device can cut off users from the Internet more conveniently than
removing TCP/IP from the machine.
 
Back
Top