Re: Connecting 2 machines with crossover cable

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Steve Winograd [MVP] (winograd_at_pobox.com)
Date: 10/31/04


Date: Sun, 31 Oct 2004 03:00:22 -0700

In article <10o96ss98sr3l17@corp.supernews.com>, Lou Ramsey
<lour@mailinator.com> wrote:
>Carey Holzman wrote:
>
>> www.careyholzman.com/netfixes.htm
>
>Chris,
>
>The Windows platform (including Windows 9x and NT/2000/XP) has its
>networking infrastructure based upon TCP/IP, with NetBIOS Over TCP/IP
>(NBT) used as an interface between TCP/IP and the various networking
>applications.
>
>Any properly configured installation of Windows will run just fine with
>these components.
>
>Be selective when accepting advice, in web pages or otherwise, that
>contains instructions to install redundant and unnecessary components,
>such as IPX/SPX or NetBEUI. Adding these extra components may serve as
>a workaround, but will add needless complications that may cause
>problems in the future.

I agree with you, Lou.

Installing an additional protocol for file and printer sharing isn't
necessary, and it can make browsing a Windows network unreliable,
especially when XP is involved.

If a network doesn't work with TCP/IP as the only protocol, adding
IPX/SPX or NetBEUI might appear to make it work. However, it won't
work optimally, and the underlying problem will still exist. It's
much better to fix the underlying problem. Practically all TCP/IP
problems are due one of these easily correctable errors:

1. A firewall program is improperly configured.
2. NetBIOS over TCP/IP isn't enabled.
3. IP addresses aren't in the same subnet.

There's one exception to the TCP/IP-only rule, but it's a
configuration that Microsoft specifically recommends not using: all of
the computers connect to a broadband Internet service through a hub or
switch (not a router) and receive public IP addresses from the ISP.

-- 
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 Program
http://mvp.support.microsoft.com


Relevant Pages

  • Windows XP TCP/IP settings
    ... I have a computer in our office with Windows XP Home SP2. ... TCP/IP and Winsocks on this computer using two pieces of software. ... Networking functionality of this computer. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Win98/WinXP home network
    ... >i have a windows 98SE laptop and a windowsXP home desktop computer. ... Networking is a lot of fun, but you need to start with a basic understanding how ... installation creates entries in the system registry. ... When you have any specific questions about file sharing or networking (and ...
    (microsoft.public.windowsxp.network_web)
  • Re: hacking Linux and Win
    ... Root access to windows is routine... ... Unix and VMS were where TCP/IP came from more or less: Its been grafted onto windows, and it never really caught up. ... The Internet is a multi user, layered access of TCP/IP networking: Windows a single user program loader with almost no networking native to it, simply entered this arena and never ever caught up. ...
    (comp.os.linux.misc)
  • Re: TCP/IP configuration/Network Adapter
    ... I just aquired a windows xp x64 professional edition setup disc and ... installed it on a 64bits machine.After the installation of the OS and all the ... all items (even Internet Protocol TCP/IP by changing the reference 0xa0 to ... Steve Winograd, MS-MVP (Windows Networking) ...
    (microsoft.public.windowsxp.network_web)
  • Re: hacking Linux and Win
    ... Root access to windows is routine... ... Unix and VMS were where TCP/IP came from more or less: Its been grafted onto windows, and it never really caught up. ... The Internet is a multi user, layered access of TCP/IP networking: Windows a single user program loader with almost no networking native to it, simply entered this arena and never ever caught up. ...
    (comp.os.linux.misc)