Win2K Server and WinXP Home client

  • Thread starter Thread starter Allen
  • Start date Start date
A

Allen

Sorry for posting this in three newsgroups, but I'm at my wits' end. I am
attempting to set up my desktop system with Win2K Server for developing an
ASP.NET application and want to use my laptop as a client machine;
additionally, I'd like to have the desktop system act as a file/printer
server. I've tried virtually everything I can think of, but the laptop
fails to "see" the desktop in the WinXP "Workgroup Computers" window;
however, the desktop is able to "see" the laptop in the Win2K Server's
"Computers Near Me: window. Even so, neither computer is able to
communicate with the other. I'm using a cross-over Ethernet cable to
connect the two computers. I don't know if it makes any difference or not,
but the laptop computer has a modem whereas the desktop doesn't. Any help
would be greatly appreciated! Ü
 
Allen said:
Sorry for posting this in three newsgroups, but I'm at my wits' end. I am
attempting to set up my desktop system with Win2K Server for developing an
ASP.NET application and want to use my laptop as a client machine;
additionally, I'd like to have the desktop system act as a file/printer
server. I've tried virtually everything I can think of, but the laptop
fails to "see" the desktop in the WinXP "Workgroup Computers" window;
however, the desktop is able to "see" the laptop in the Win2K Server's
"Computers Near Me: window. Even so, neither computer is able to
communicate with the other. I'm using a cross-over Ethernet cable to
connect the two computers. I don't know if it makes any difference or not,
but the laptop computer has a modem whereas the desktop doesn't. Any help
would be greatly appreciated! Ü
Click to expand...

What are their IP addresses, and can you ping them by address and then
by hostname?
 
The desktop server has an IP address of 198.162.0.1 and the laptop uses
198.162.0.2. I can ping each computer from the other using their IP
addresses, but I cannot ping them by hostname.
 
Greetings --

On the WinXP PC, create local user account(s), with password(s),
that have the desired access privileges to the desired shares. Log on
to the other PCs using those account(s), and you will be able to
access the designated shares, provided your network is configured
properly.

On the Win2K PC, create local user account(s), with password(s),
that have the desired access privileges to the desired shares. Log on
to the other PCs using those account(s), and you will be able to
access the designated shares, provided your network is configured
properly.

Usually, WinXP's Networking Wizard makes it simple and painless --
almost entirely automatic, in fact. There's a lot of useful,
easy-to-follow information in WinXP's Help & Support files, and here:

Home Networking
http://www.microsoft.com/windowsxp/home/using/howto/homenet/default.asp

Networking Information
http://www.onecomputerguy.com/networking.htm

PracticallyNetworked Home
http://www.practicallynetworked.com/index.htm

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

Configuring Windows 2000 Professional to Work in a Peer-to-Peer
Network
http://support.microsoft.com/default.aspx?scid=KB;EN-US;q258717


Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
Allen said:
The desktop server has an IP address of 198.162.0.1 and the laptop uses
198.162.0.2. I can ping each computer from the other using their IP
addresses, but I cannot ping them by hostname.
Click to expand...

Do you have Client for Microsoft Networks bound to the network adapters
on both machines? Is the firewall configured on the WinXP box?

As a work-around, put the other machine's IP and hostname in your hosts
files on both machine, typically found somewhere like
C:\winnt\system32\drivers\etc\hosts. You might want to enable NetBIOS
over TCP/IP. If you're working in a workgroup instead of a domain,
ensure you have user on both machines with the same name and password
(makes things simpler, but not necessary). If you make these changes,
you will at least be able to specify the path by name, even if the
Network Neighbourhood is misbehaving. You can also do things by IP,
e.g. browser to \\192.168.0.2\C$. I make no claims about security either.

Malc
 
Might be a bad NIC, try pinging with larger packets. Make sure you do NOT have
hosts file or DNS.

| The desktop server has an IP address of 198.162.0.1 and the laptop uses
| 198.162.0.2. I can ping each computer from the other using their IP
| addresses, but I cannot ping them by hostname.
|
 
Back
Top