Dream Machine ( Build your own PC ) Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC )

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Zeuspaul who wrote (165)	2/8/1998 3:47:00 PM
From: John Johnston	Read Replies (2) of 14778

Your cabling is ok if you can see the network from Zeus1 and the cards should be ok as well. So thats a good sign. In Networks you should see NETBEUI, TCP/IP, and MS Client, which one has an Icon that looks like a monitor. Which ever one it is is the protocal your using. Make sure you have the same protocal on both units. Since Zeus1 is ok and can see Zues2 and the network, leave it as is. The problem appears to be residing in Zues2. Have you checked your share propertis items? You may want to uninstall the Zeus2 from the network and start a fresh. Got to networks, hightlight the MS Client( assuming that's the same one used on Zeus1), then click on add client. It should walk you through the client "add to network" process.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next