Netbeui and gigabit

[jsj6791]

What's the compatibility between the netbeui and gigabit adapters? I've recently upgraded my network to gigabit w/ jumbo frame, and while my previous setup worked fine connecting with netbeui, I could not connect them with the new setup. After trying while to figure it out, I uninstalled netbeui as a last resort, and it finally worked with tcp/ip.

I am using 2 intel gigabit nics and smc switch, which all works fine with netbeui until I activate the jumbo frame. Is this true? Is jumbo frame not compatible with netbeui?
Thanks in advance for the help.

 

[alent1234]

why are you using netbeui vs tcp/IP?

netbeui is broadcast based, non-routable and will eat up more bandwidth than ip

 

[jsj6791]

Originally posted by: alent1234
why are you using netbeui vs tcp/IP?

netbeui is broadcast based, non-routable and will eat up more bandwidth than ip

I think I saw a post here somewhere where JackMDS was mentioning netbeui was more secure. The article he mentioned was

Netbeui

Right?

 

[alent1234]

if you are afraid of people hacking in from the outside, then yes it's more secure but only if you don't have TCP/IP installed. If you have TCP/IP installed and properly configured on your PC then your computer will answer requests from the internet unless you have a firewall.

 

[spidey07]

Originally posted by: alent1234
why are you using netbeui vs tcp/IP?

netbeui is broadcast based, non-routable and will eat up more bandwidth than ip

but its faster than TCP, especially with gigabit.

And it has actually LESS overhead than TCP/IP meaning it uses less bandwidth for a given conversation.

 

[Yellow Dog]

Originally posted by: alent1234
if you are afraid of people hacking in from the outside, then yes it's more secure but only if you don't have TCP/IP installed. If you have TCP/IP installed and properly configured on your PC then your computer will answer requests from the internet unless you have a firewall.

Or if you unbind file and print sharing from TCP/IP you provide an additional level of protection for your stuff.

 

[jsj6791]

Originally posted by: spidey07
but its faster than TCP, especially with gigabit.

And it has actually LESS overhead than TCP/IP meaning it uses less bandwidth for a given conversation.

So netbeui can coextist with gigabit, jumbo frame enabled?

 

[spidey07]

Originally posted by: jsj6791

Originally posted by: spidey07
but its faster than TCP, especially with gigabit.

And it has actually LESS overhead than TCP/IP meaning it uses less bandwidth for a given conversation.

So netbeui can coextist with gigabit, jumbo frame enabled?

One would think so, but I'd have to look at the protocol fields to truly make sure.

netbeui doesn't care what kind of network you use. It doesn't really matter. What probably happened was you were a victim of microsoft networking where the bindings got out of order (regardless of what you set them to)

 

[Yellow Dog]

you have to keep in mind that any network connection is dependent on TWO different protocols.

The first is dependent on the type of hardware/wiring such as Ethernet, Wireless, IR, Token Ring, and so on.

The second is the layer 3 protocol, such as TCP/IP, NetBeui, IPX/SPX, AppleTalk, Vines, and so on.

Layer 3 protcols don't care if they are going to be shipped out on Ethernet, wireless or whatever, and the hardware protocols don't care if they are sending TCP/IP, NetBeui or any of the others. The protocol "stack" and the hardware and device drivers deal with all the details.

 

[Pepsi90919]

Originally posted by: alent1234
why are you using netbeui vs tcp/IP?

netbeui is broadcast based, non-routable and will eat up more bandwidth than ip

but it WORKS.

 

[Yellow Dog]

Originally posted by: Pepsi90919

Originally posted by: alent1234
why are you using netbeui vs tcp/IP?

netbeui is broadcast based, non-routable and will eat up more bandwidth than ip

but it WORKS.

wrong, right and wrong. NetBeui is NOT broadcast based. And yes it is non-routable, which is the primary reason it is faster (less protocol overhead and more payload) and why it is more secure. And because it has less protocol overhead and a greater payload it is slightly faster than IP.

Gotta remember that IP was developed by a government grant back in the 60's, it is NOT leading edge technology.

 

[jsj6791]

Originally posted by: Yellow Dog
Layer 3 protcols don't care if they are going to be shipped out on Ethernet, wireless or whatever, and the hardware protocols don't care if they are sending TCP/IP, NetBeui or any of the others. The protocol "stack" and the hardware and device drivers deal with all the details.

Okay, so it shouldn't really matter whether you're using giga or 10/100, right?

I was browising through the intel website and found this in their support section. Looks like it might have to do with nic's itself.

Intel 1000MT support

Problem passing NetBeui traffic

Symptom(s):

Server has to ping client before client can ping server
Network passes all traffic except NetBEUI, netBIOS

Cause:
WINS service only passes over the first VLAN

Solution:

Disable WINS
Put server address permanently in arp

End of article.

Isn't WINS already disabled in XP?
And I have no idea what they mean by putting server address in arp.

Help anybody?

 

[wadewood]

I use Netbeui for small home network. I have installed Airlink+ brand Gigabit nics (no jumbo frame support) with an Airlink Gigabit Switch ($20 at Frys). It works fine over Netbeui.

For what it is worth, my throughput tests show speeds around 80 Mbps on file transfers between computers.

 

[JackMDS]

Every week one NetBEUI thread like this one is On.

There are always few people that are very good posting the ?Ethnic Slogans? version of Networking about NetBEUI,

Few years past I I am yet to see one person giving a solid technological answer explaining why Not to use NetBEUI on a Network that is comprised of few computers.

:sun:

 

[WiseOldDude]

All of my file and printer sharing is by NetBEUI only, including 2003 server, XP pro & home, wired and wireless. It is secure because my shares cannot be accessed from the internet, it is fast (NetBEUI is a more efficient protocol than TCP/IP).

And like you I have never heard anyone give any valid reason not to use it, other than perhaps it comes from the evil gates empire, and as such must be bloated and slow.

 

[Nothinman]

Few years past I I am yet to see one person giving a solid technological answer explaining why Not to use NetBEUI on a Network that is comprised of few computers.

The same thing could probably be said of IPX, but would you recommend it?

 

[spidey07]

Originally posted by: Nothinman

Few years past I I am yet to see one person giving a solid technological answer explaining why Not to use NetBEUI on a Network that is comprised of few computers.

The same thing could probably be said of IPX, but would you recommend it?

No, the same cannot be said for IPX. IPX is just the network/transport with its associated overhead. Netbeui by very protocol is more efficient.

We're talking about procol efficeincies (OMG! sp????) here.

Until somebody gives a complete, thorough protocol analysis and does the math of netbeui vs TCP the fact remains. Netbeui is faster thatn IP/TCP....this reallly can't be debated.

Sure its outdated, sure it broadcast based, sure it blow chunks...but its still more efficient. And to top it off, its immune to microsoft difficutly with networking.

 

[Nothinman]

If it's so great, why isn't it installed by default? And why was it moved to a secondary folder (support or legacy or something) on the XP discs?

 

[Goosemaster]

Originally posted by: Nothinman
If it's so great, why isn't it installed by default? And why was it moved to a secondary folder (support or legacy or something) on the XP discs?

do you really have to ask?

 

[JackMDS]

Originally posted by: Nothinman
If it's so great, why isn't it installed by default? And why was it moved to a secondary folder (support or legacy or something) on the XP discs?

Because in the broad spectrum of default installations of a generally used OS, there is many more considerations than just what would be used by a small segment of users that Networks peer to peer few computers.

In addition bear in mind that in top of technological factors there are a myriad of factors involving, Legal issues, Support issues, Marketing Issues, etc, that affect what you see in a final product.

:sun:

 

[Nothinman]

With the popularity of home networks, one would think that if the protocol was so great and made filesharing work without any intervention that they would be promoting it for SOHO networks.

 

[spidey07]

Originally posted by: Nothinman
With the popularity of home networks, one would think that if the protocol was so great and made filesharing work without any intervention that they would be promoting it for SOHO networks.

Microsoft isn't known for making good decisions.

 

[ktwebb]

Yeah that Microsoft has made one bumbling decision after another for years.

 

[ktwebb]

he second is the layer 3 protocol, such as TCP/IP, NetBeui, IPX/SPX, AppleTalk, Vines, and so on.

NetBEUI is a transport layer protocol. Oh, and it is a broadcast based protocol as well.

 

[Nothinman]

Microsoft isn't known for making good decisions.

They seem to be doing ok for themselves...