Protocol choice, networking XP and 98SE

In my "Network connection on Win98SE machine keeps
failing" thread, one of the things I reported is the use on
my Win98SE machine of both TCP/IP and NETBEUI
(wired network to a WinXP machine and the Internet via a
2wire gateway connected to Telus DSL). I've run across
a couple of recommendations that one should use only
NETBEUI in this and maybe other situations, dumping
TCP/IP altogether. These suggestions go back some few
years -- but then, so do WinXP and Win98SE. Any
thoughts from this group on which protocols or
combinations thereof are more reliable? Thanks.

Anthony Buckland wrote:

> In my "Network connection on Win98SE machine keeps failing"
> thread, one of the things I reported is the use on my Win98SE
> machine of both TCP/IP and NETBEUI (wired network to a WinXP
> machine). I've run across a couple of recommendations that
> one should use only NETBEUI in this and maybe other situations,
> dumping TCP/IP altogether. These suggestions go back some few
> years -- but then, so do WinXP and Win98SE. Any thoughts
> from this group on which protocols or combinations thereof
> are more reliable? Thanks.

One thing to note is that it has been said by some that XP's
implimentation of NetBeui is faulty or prone to problems, and that
there is a way to incorporate Windows-2000 files into an XP system to
obtain a more stable (or more compatible) solution.

XP seems to have been designed specifically to thwart easy and
trouble-free network compatibility with win-98 systems.

On Jun 4, 8:10 pm, "Anthony Buckland"
<anthonybucklandnos...@telus.net> wrote:
> In my "Network connection on Win98SE machine keeps
> failing" thread, one of the things I reported is the use on
> my Win98SE machine of both TCP/IP and NETBEUI
> (wired network to a WinXP machine and the Internet via a
> 2wire gateway connected to Telus DSL). I've run across
> a couple of recommendations that one should use only
> NETBEUI in this and maybe other situations, dumping
> TCP/IP altogether. These suggestions go back some few
> years -- but then, so do WinXP and Win98SE. Any
> thoughts from this group on which protocols or
> combinations thereof are more reliable? Thanks.

hi i am amol for your group membership

In article <#(E-Mail Removed)>, "Anthony Buckland"
<(E-Mail Removed)> wrote:
>In my "Network connection on Win98SE machine keeps
>failing" thread, one of the things I reported is the use on
>my Win98SE machine of both TCP/IP and NETBEUI
>(wired network to a WinXP machine and the Internet via a
>2wire gateway connected to Telus DSL). I've run across
>a couple of recommendations that one should use only
>NETBEUI in this and maybe other situations, dumping
>TCP/IP altogether. These suggestions go back some few
>years -- but then, so do WinXP and Win98SE. Any
>thoughts from this group on which protocols or
>combinations thereof are more reliable? Thanks.


I've done setup and troubleshooting on hundreds of networks with WinXP
and Win98SE. I always remove NetBEUI (and IPX/SPX) if present and use
only TCP/IP. I strongly recommend using TCP/IP has the only network
protocol:

1. Using more than none network protocol can make File and Printer
Sharing unreliable, especially when XP is involved.

2. NetBEUI is an unsupported protocol in XP. Microsoft didn't test it
fully, and there's no guarantee that it will work.

3. Nothing in Windows networking has ever required NetBEUI.

4. TCP/IP is required for Internet access.

5. TCP/IP supports all Windows networking functions.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

In article <(E-Mail Removed)>, "Steve
Winograd [MVP]" <(E-Mail Removed)> wrote:
>In article <#(E-Mail Removed)>, "Anthony Buckland"
>
>1. Using more than none network protocol can make File and Printer
>Sharing unreliable, especially when XP is involved.

I apologize for my unfortunate typo. That should say:

>1. Using more than one network protocol can make File and Printer
>Sharing unreliable, especially when XP is involved.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

Funny as I've always setup my Ethernet using Netbuie since (if memory serves
me right) it was all that 'came in the package' back in WFW3.x days. I've
seen no reason to change and have had no problems using it on any mix of 9x,
2K & XP pcs. What I like about it is the lack of any 'bs' to set it up. Give
the pc a name and assign it to WorkGroup and it works. Seems to me tcp/ip
involves a lot more rig-a-more-ol before it works. That's not to say it
doesn't but the only reason I install it (and sometimes IPX/SPX) is for
multiplayer gaming in-house and for apps such as PCAnywhere. In fact, I feel
"safer" when the pc uses tcp/ip for internet and solely netbuie for
ethernet.

"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In article <(E-Mail Removed)>, "Steve
> Winograd [MVP]" <(E-Mail Removed)> wrote:
> >In article <#(E-Mail Removed)>, "Anthony Buckland"
> >
> >1. Using more than none network protocol can make File and Printer
> >Sharing unreliable, especially when XP is involved.
>
> I apologize for my unfortunate typo. That should say:
>
> >1. Using more than one network protocol can make File and Printer
> >Sharing unreliable, especially when XP is involved.
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional - Windows Networking
> http://mvp.support.microsoft.com
>
> Steve Winograd's Networking FAQ
> http://www.bcmaven.com/networking/faq.htm

pjp wrote:

> In fact, I feel "safer" when the pc uses tcp/ip for internet
> and solely netbuie for ethernet.

"Steve Winograd [MVP]" wrote in message

> 1. Using more than one network protocol can make File
> and Printer Sharing unreliable, especially when XP is
> involved.

Using XP back when it first came out, all the way up to at least SP2,
was a disaster as far as network security is concerned, and MS's
tactical decision to force XP to use TCP/IP for everything only made
XP's security situation worse.

I agree fulling with pjp in that file and print sharing with NetBeui
on your local lan was an excellent choice for security reasons,
especially on networks that weren't NAT-protected from the internet,
which was common in the late 90's until cheap NAT-routers started to
be used for SOHO situations.

NetBeui actually has better performance for local file-sharing than
TCP does.

But MS was bent on dominating the internet, so along with surgically
integrating IE and other shit like active directory into Windoze, they
also made sure that file sharing via TCP was basically XP's only
option, and they made doubly sure by turning on file-sharing by
default. That, and all their other netbios holes turned XP into the
premiere zombie/botnet platform by 2003, thereby spawning the spam
avalanche that continues to plague the internet.

In article <(E-Mail Removed)>, "pjp"
<pjpoirier_is_located_at_@_hotmail_._com> wrote:
>>>In my "Network connection on Win98SE machine keeps
>>>failing" thread, one of the things I reported is the use on
>>>my Win98SE machine of both TCP/IP and NETBEUI
>>>(wired network to a WinXP machine and the Internet via a
>>>2wire gateway connected to Telus DSL). I've run across
>>>a couple of recommendations that one should use only
>>>NETBEUI in this and maybe other situations, dumping
>>>TCP/IP altogether. These suggestions go back some few
>>>years -- but then, so do WinXP and Win98SE. Any
>>>thoughts from this group on which protocols or
>>>combinations thereof are more reliable? Thanks.
>>
>>I've done setup and troubleshooting on hundreds of networks with WinXP
>>and Win98SE. I always remove NetBEUI (and IPX/SPX) if present and use
>>only TCP/IP. I strongly recommend using TCP/IP has the only network
>>protocol:
>>
>>1. Using more than none network protocol can make File and Printer
>>Sharing unreliable, especially when XP is involved.
>>
>>2. NetBEUI is an unsupported protocol in XP. Microsoft didn't test it
>>fully, and there's no guarantee that it will work.
>>
>>3. Nothing in Windows networking has ever required NetBEUI.
>>
>>4. TCP/IP is required for Internet access.
>>
>>5. TCP/IP supports all Windows networking functions.
>
>Funny as I've always setup my Ethernet using Netbuie since (if memory serves
>me right) it was all that 'came in the package' back in WFW3.x days. I've
>seen no reason to change and have had no problems using it on any mix of 9x,
>2K & XP pcs. What I like about it is the lack of any 'bs' to set it up. Give
>the pc a name and assign it to WorkGroup and it works. Seems to me tcp/ip
>involves a lot more rig-a-more-ol before it works. That's not to say it
>doesn't but the only reason I install it (and sometimes IPX/SPX) is for
>multiplayer gaming in-house and for apps such as PCAnywhere. In fact, I feel
>"safer" when the pc uses tcp/ip for internet and solely netbuie for
>ethernet.

WfW3.x came with IPX/SPX and NetBEUI -- it wasn't necessary to use
NetBEUI even back then. Microsoft later released TCP/IP for WfW3.x.

The OP's network uses a broadband router (2wire gateway) connected to
a DSL modem. A broadband router acts as a DHCP server and NAT
firewall, so:

1. The only required setup is to configure each computer to obtain an
IP address automatically.

2. It's safe to use TCP/IP as the only network protocol. The
computers have non-routeable private IP addresses and can't be
accessed by other people on the Internet.

I've written a web page with more information on network protocols:

Windows XP Network Protocols
http://www.practicallynetworked.com/..._protocols.htm
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

Hi all

I have a slightly different problem, in that I must (MUST) network with a
number of legacy DOS boxes using NetBEUI. This has never been a problem and
I have prepared literally dozens of XP boxes by adding NetBEUI protocol
(copying the two files from the CD etc) and it all works perfectly. My
problem is that, with the latest batch of XP PC's with the latest
incarnation of XP Pro re-installed, NetBEUI no longer works (it does however
continue to work older PC's kept up to date with MS patches and poltices).
I am right now trying to determine which MS component has broken NetBEUI
support but if anyoune has any more info, I would appreciate it. Eventually
the DOS boxes will be replaced and the problem will go away but not for a
year or two. And I can't touch them.

MS did a similar thing with W2K SP4 but quickly brought out a hotfix to
repair the damage.

Regards,

Denville.

"Anthony Buckland" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> In my "Network connection on Win98SE machine keeps
> failing" thread, one of the things I reported is the use on
> my Win98SE machine of both TCP/IP and NETBEUI
> (wired network to a WinXP machine and the Internet via a
> 2wire gateway connected to Telus DSL). I've run across
> a couple of recommendations that one should use only
> NETBEUI in this and maybe other situations, dumping
> TCP/IP altogether. These suggestions go back some few
> years -- but then, so do WinXP and Win98SE. Any
> thoughts from this group on which protocols or
> combinations thereof are more reliable? Thanks.
>