Please clarify accepted protocols between XP and ME

[jim.t]

I'm running a cable modem to Linksys router to a WinME box and a WinXP box. Before with WinME and Win95 DOS-based systems I used the NetBeui/TCPIP protocol for both boxes.

Now with XPHome (from everything I've read) I am to use the same NetBeui/TCPIP configuration with the ME box and IPXSPX/TCPIP/adapter configuration with the XP box because Netbeui is no longer available for WinXP...correct?? So why are the how-tos showing hardwiring IP-address and subset mask on the XP? I thought with a router I needed to select "obtain Ip automatically" and let it grab those addresses dynamically.

Also someone else told me that NetBios took the place of Netbuei, and I wouldn't need IPX/SPX, but "select network protocol" window it only shows NWLink IPX/SPX/Netbios combination...not Netbios alone.

Any thoughts?

Thanks, Jim

[cat5e]

TCP/IP is the Universal Protocol that is used for Internet surfing, and can be used for all types of Windows OS.

NetBEUI is a simpler protocol can be used for local traffic on both WinME and Windows XP (Home and Pro).

IPX/SPX, is an old protocol that was used in some early games.

You must have TCP/IP on all computers.

NetBEUI is optional read here about it.

Link to: Set NetBEUI as the Default Sharing Protocol in WinXP. (http://www.ezlan.net/netbeui.html)

IPX/SPX if not needed can be remove.

Log to this page it has a lot of links to instructions to Windows Network Settings, and Sharing.

Link to: Windows Network - Installing & Sharing. (http://www.ezlan.net/Installing.html)
:cool:

[omendata]

IPX/SPX AND NETBUIE ARE THE FASTEST PROTOCOLS

on a msal network netbuie is the best but cannot be used for accessing the internet!

dont install more than one protocol - each broadcast your pc makes has to go out on each protocol insalled - this slows down your networking

Ideally you should only have tcp/ip installed for an internet connected machine/small network

netbios is not a protocol its a api related to netbuie that provides the network commands to perform transfer of data from one host to another - It is quite confusing!

The commands are interpreted by a network control program or network operating system that is NetBIOS compatible.

[cat5e]

As far as small LANs (8 or fewer computers), my experience as well as actual in vivo evaluation, shows that if NetBEUI is bound to File and Printer Sharing, and the TCP/IP is used for Internet only. Both the Internet connection, and LAN transfer are faster (about 5%-10%).

In addition it adds more security since NetBEUI is not Routable to the Internet. I.e your files would not be shared with WWW.

:cool:

[omendata]

Did you use a software or hardware analyzer?

I luvv my Fluke testers! Beautiful pieces of equipment and that soft yellow rubber - orgasmic - grrrrrrr!

Interesting - I was basing mine on large networks with switches and routers , should have kept it simple DUH - still would have thought even on a small single hub network it would be faster with just one protocol but there you go.

What end to end tester did you use - Im gonna give it a go right now! Saturday night and doing nerdy network thruput tests - sad eh!

Im actually doing some IPX tests on a small 3 computer hub network at this very moment - as we speak so to speak!

It also depends on the data you transfer - I did some tests using 700mb files but bursty traffic will not show the same speed results - with the tests I did there was virtually no difference!

My tests were involving the various network card settings to increase the speed - ie receive threshold etc on 3com and intel cards - doesnt matter how ye tweak em it makes little difference!
:t

[jim.t]

Thanks for the feedback. I've gone over and over the setups for both boxes. I still have a lingering feeling that when I tried to setup networking on the XP using the network wizard...and creating the floopy to apply to the ME box (which I did)... I might have created some problems on the ME box (even though all looks well).

My problem is there seems to be mulitple ways of solving the
ME->XP network, that I've gotten a tad confused. Do I use NetBios on the XP? Do I install IPX/SPX...and then what do I do with TCP/IP? Right now if I were installing MEe to Win95, both machines look to have everything setup the way they should. But, I'm sure I've overlooked something...somewhere. I love challenges, but this is a real puzzle.

Thanks.

[omendata]

You cannot install netbios - its already inbuilt!

Just remove everything and install only netbuie on your network , client of rmicrsoft networks and file and print sharing to test inter-host communication then install tcp/ip but start off slowly dont try and do everything at once and dont use any networking wizard - its cr@p!

[cat5e]

Originally posted by omendata
Interesting - I was basing mine on large networks with switches and routers , should have kept it simple DUH - still would have thought even on a small single hub network it would be faster with just one protocol but there you go.BBSs like this and other are great since they really mix Pro and Humble users together.

However there is one slight drawback. Often Professional Guys give advice that pertains to the Heavy stuff that they are using in work (Kind of Bulldozer Mechanic trying to give advice to a Morris Mini. owner).

So the Fluke and the Chariot are in the “closet” for such purposes. What I am talking about is based on Functional Windows XP Pro systems, configured with OfficeXP and similar programs for Small Office Network, using an Entry Level Cable/DSL Router as the center piece, and tune for max. TCP/IP for Cable Internet. The effect can be seen clearly when the computers are actually used for other purposes rather then just testing.
:t

[jim.t]

Ok, folks... and cat5e, that has got to be the best layed-out tutorial on how to link up two M/S OS's (that don't like each other)I've seen in a while. Box to box, step by step, the way an old **** like me likes it.

It certainly cured my file-sharing ills, and I'm really not sure how or why. Most of it I understand for each PC, but not sure why it works between them. I won't hestitate saying y'all came through again. You guys are GOOD!

Question: do I have to load the printer drivers (hooked to ME box) on the XP box also, or will it find the printer thru the network? Sorry to appear so lame, but it's be a long few days.

Thanks, Jim.

[cat5e]

Originally posted by jim.t
Question: do I have to load the printer drivers (hooked to ME box) on the XP box also, or will it find the printer thru the network? Sorry to appear so lame, but it's be a long few days.

Thanks, Jim. You better off installing the drivers on the XP box too. Some Windows Applications do not like to print when there is no local drivers.

As far as a tutorial. The Link in my first post contains the Best Links that can be found on the Internet concerning these issues.

All Windows OSs (including WinXP) were designed and released before the current Boom in Personal Networkng, so consider yourself a Semi-Pioneer. It will be better with the next OS.
:t

[omendata]

Yeah catman - I usually do give advice based on the users experience!

I just assumed (bad idea) that small network would be the same!

Im gonna test it with the fluke when i can grab it from work - not to disprove anything - Im sure you are right - just to satisfy my own curiosity!

:t

When I do a build I usually copy the xp cd onto a separate partition on the hard disk - then do the install - that way if there is ever anything needed its always on the hard disk - no need ot go looking for the XP CD which by the time I find it (knoiwing my bad luck) is usually scratched an nae use to man nor beastie!
:-@

[cat5e]

Omendata, it is slightly of the Topic, but along the same line.

We all know that “Switch is better than Hub”.

Log here, look at the left side frame and click on Switch vs. Hub: Switch vs. Hub Test Results. (http://www.scottmac.net)
:t

[omendata]

Hmmm not seen that one before!

Interesting link Catman!