Discussion Locked

2 netw. PCs Win2000 can't see eachother

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have two PCs running Win2000, one as server. PC #1 cannot see PC #2, and PC #2 cannot see PC #1. What could be the problem? Or, better yet, what is the proper way of setting them up? Are there any instructions anywhere on how to do it properly? Thanks for your help.

9 replies

by blaine moore

How are they connected, through a hub or directly by cat5 cable?

In terms of physically setting them up:
Option A) Use a hub/router/switch or other network device
Plug each device into a normal port. If connecting a cable modem or other broadband device, you will generally want to plug that into the uplink port. Some hubs have an uplink port that can be toggled to a normal port. If you want the two win2k computers to talk to each other, do _not_ plug either of them into the uplink port.
Option B) Directly connecting the two PCs
There are a few ways to do this. You can connect parrallel ports, serial ports, etc and then connect through them. I assume you want to network them through a NIC, however. To do that, you will need a crossover cable to connect the two. A straight through ethernet cord will be insufficient, since both machines will attempt to send and recieve on the same lines instead of sending to the other's recieve wire. You can purchase crossover cables at most computer stores, and if you crimp your own cable and don't know how to make one then there is a good tutorial at http://www.littlewhitedog.com/reviews_other_00009.asp

Once you have the two machines able to physically communicate with each other, you need to set up windows to place them both on the same network with a subnet mask that will allow them to see one another. Open a command prompt (cmd) and run ipconfig /? for the syntax of using that command.

by p. dickason, cne, mcse, cca

If one of the PC's is Windows 2000 server, you can configure DHCP to deploy addresses within the same subnet as the server while then they could talk to each other. Or to make things easy, just check the TCP/IP address on each machine to ensure they are within the same subnet. I'm assuming the non-server is set to obtain an address automatically. Thats the default setting. If your server is 192.168.0.1 with a 24 bit subnet mask (255.255.255.0), make your workstation 192.168.0.{any number between 2 and 254) with a 24 bit subnet mask as well. Also make sure the server and workstation is configured to use the same workgroup name. This is found if you right click my computer and select properties then the network ID tab. If your server is configured as a domain controller (you used dcpromo to install active directory), then your workstation will have to join this domain to communicate to the server. (this isn't entirely true but for all intents and purposed, it should be done). Then configure the workstation to point to the server as well for DNS since AD uses DNS to communicate. Hope this helps.
Pete

by cg it

To add to answers 1 & 2, you also have to configure access policies to allow another computer to access the "shared" files and/or folders if you are using peer to peer networking. This is accomplished in admin tools/local security policy. In local security policy, you add in those computers you wish to provide access in "access this computer from the network".

This discussion is closed to new replies.