Two PCs Direct -- Error Message

I've hooked up 2 PCs directly to each other with a Cat 5
crossover cable. I'm running ME on both machines. One PC
recognizes only itself on the network. The other PC won't
allow me to access the network at all. When I open My
Network Places on the second machine I get the error message:
"Unable to browse the network. Windows is unable to
gain
access to the network. This may be for a number of
reasons. For more information click HELP."

I tried everything in the networking troubleshooter, but
was unable to gain access to the network on the second machine.

Anybody know what I've missed?

In article <051d01c42a76$fa8d0570$(E-Mail Removed)>, "CB"
<(E-Mail Removed)> wrote:
>I've hooked up 2 PCs directly to each other with a Cat 5
>crossover cable. I'm running ME on both machines. One PC
>recognizes only itself on the network. The other PC won't
>allow me to access the network at all. When I open My
>Network Places on the second machine I get the error message:
> "Unable to browse the network. Windows is unable to
>gain
> access to the network. This may be for a number of
> reasons. For more information click HELP."
>
>I tried everything in the networking troubleshooter, but
>was unable to gain access to the network on the second machine.
>
>Anybody know what I've missed?

Make sure that File and Printer Sharing is enabled on both computers.

It can take up to 15 minutes after a computer starts up before network
browsing works. During that time, you should be able to access the
other computer by typing the other computer's name in the Start | Run
box preceded by two backslash characters:

\\computer

If that doesn't work, a common reason for inability to browse the
network is that the user isn't logged on. Is there a logon prompt
when Windows ME starts? If so, don't cancel it. Complete the logon
by entering a user name and, optionally, a password. If there's no
logon prompt, click Start | Log Off or Start | Shut Down | Close all
programs... and log back on. If that makes network browsing work
properly, the most likely fix is to go to this registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\
Network\Real Mode Net

and delete the value named "AutoLogon", as shown here:

http://www.wown.com/j_helmig/nologon.htm#AutoLogon
--
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