ME and XP networking problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

cco1030 - 16 Oct 2004 16:32 GMT

I have a DSL modem and a Linksys wireless router. I have my desktop
running ME hooked up to the router with a Ethernet cable. I have 2 machines
running XP ( 1 laptop and 1 desktop) that connect with wireless cards. All 3
machines can access the internet without a problem.
The 2 XP machines recognize each other in "my network places". They can
share folders and even the printer on the XP desktop. The problem I'm having
is getting the XP machines to recognize my ME machine and vice versa. I
can't get through the networking wizard on the ME machine. Every time I
enter the "Workgroup name"and hit enter I get a blue screen with "vserver
error"
Would going wireless on my ME machine be easier?
I'm new to networking, any help would be appreciated.

Reply to this Message

Steve Winograd [MVP] - 16 Oct 2004 18:25 GMT

> I have a DSL modem and a Linksys wireless router. I have my desktop
>running ME hooked up to the router with a Ethernet cable. I have 2 machines
[quoted text clipped - 8 lines]
> Would going wireless on my ME machine be easier?
> I'm new to networking, any help would be appreciated.

Going wireless on the ME machine wouldn't make things any easier.

There's no need to run the networking wizard on the ME machine. You
can make all the necessary settings manually. Go to Control Panel |
Network and:

1. Add these network components if they aren't already present:

TCP/IP protocol
Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks

2. Remove these network components if they're present:

IPX/SPX protocol
NetBEUI protocol
Client for NetWare networks

3. Set the workgroup name to the same name as the Windows XP computer
uses (default for XP is MSHOME).

Make sure that all of the computer names are less than 16 characters
long and that they contain only numbers and letters (no blanks).

Signature

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

Reply to this Message

cco1030 - 17 Oct 2004 12:32 GMT

Hi Steve,
All the items you mentioned in "step 1" are installed on my machine and
all the items in "step 2" were not installed on my machine as you suggested.
The group name is the same on all 3 machines. All the computer names are
also less than 16 characters and contain no spaces etc. Still no luck. Craig

> > I have a DSL modem and a Linksys wireless router. I have my desktop
> >running ME hooked up to the router with a Ethernet cable. I have 2 machines
[quoted text clipped - 45 lines]
> Steve Winograd's Networking FAQ
> http://www.bcmaven.com/networking/faq.htm

Reply to this Message

cco1030 - 17 Oct 2004 15:22 GMT

One other thing I've noticed is when I go into My Network places and click
on entire network I get an error that says "unable to browse network" etc

> Hi Steve,
> All the items you mentioned in "step 1" are installed on my machine and
[quoted text clipped - 56 lines]
> > Steve Winograd's Networking FAQ
> > http://www.bcmaven.com/networking/faq.htm

Reply to this Message

Steve Winograd [MVP] - 17 Oct 2004 19:06 GMT

>One other thing I've noticed is when I go into My Network places and click
>on entire network I get an error that says "unable to browse network" etc

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
another computer by typing the other computer's name in the Start |
Run box preceded by two backslash characters:

\\computer

If that doesn't work, here are two common reasons for the inability to
browse the network:

1. The network settings are configured for user-level access control,
which isn't available in a peer-to-peer network. Go to Control Panel

| Network, click the Access Control tab, and make sure that

share-level access control is selected.

2. The user isn't logged on. Is there a logon prompt when Windows
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\CurrentVersion\
Network\Real Mode Net

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

http://www.wown.com/j_helmig/nologon.htm#AutoLogon

Please see these Microsoft Knowledge Base articles for more
information:

"Unable to Browse the Network" When You Click Network Neighborhood
http://support.microsoft.com/?scid=kb;en-us;260214

No Windows or Network Logon Dialog Box at Startup
http://support.microsoft.com/?scid=KB;en-us;141858

Signature

Reply to this Message

cco1030 - 17 Oct 2004 20:08 GMT

I tried to access by typing \\computer from my ME machine and no luck.
I then went to access control and share-level access was selected already
I have no logon prompt when windows starts.
I then went to the registry
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
Network\Real Mode Net and checked for the "Autologon" and that value was not
there.

would upgrading my ME machine to XP solve this problem? Just wondering

> >One other thing I've noticed is when I go into My Network places and click
> >on entire network I get an error that says "unable to browse network" etc
[quoted text clipped - 49 lines]
> Steve Winograd's Networking FAQ
> http://www.bcmaven.com/networking/faq.htm

Reply to this Message