|
Question : PC to Mac 2 computer Network
|
|
I own a Macintosh G3 266 and a Pentium II 233. I'm trying to connect the two as a network. I was told that I could connect the two across Ethernet (built-in on the Mac and card installed on the PC) without a hub if I used a crossover cable, which I have. My only question is, how do I configure it? Does one of the machines have to be a "host?" What protocol do I use?
|
Answer : PC to Mac 2 computer Network
|
|
I really cannot help you with that particular piece of software... all I can suggest is now contacting their tech support department
as their web page suggests and asking them for help if the following solution does not work:
Online Troubleshooter
What we know:
COPSTalk is installed, but you're having trouble seeing the devices on the network. You don't see any devices.
Troubleshooter response:
What follows is a series of instructions for solving your problem of not seeing the devices on your network.
If you try these instructions, but you're still not having any luck, contact COPS Technical Support at [email protected].
Checking Connections
The first thing to do is to make sure your computer is properly connected to the network. If you feel certain that your physical
connection is OK, feel free to skip to
the section below on resource conflicts.
First, determine whether your computer is connected to an Ethernet or LocalTalk network. If it is Ethernet, determine whether
you're using coaxial cable (also
known as thinnet or 10BASE-2) or unshielded twisted-pair wiring (also known as 10BASE-T).
For coaxial (10BASE-2) networks, each workstation should be connected to a BNC T-connector, which in turn should be
connected to two cables (one on either
side of the T-connector) or to one cable and a terminator plug. You cannot plug the coaxial cable directly into the BNC
connector on your network adapter - you
must use a T-connector.
For twisted-pair (10BASE-T) cable, the RJ-45 plug on the cable should be plugged directly into the RJ-45 jack on your network
adapter. The other end of the
cable connects to a hub; generally, there can be only one device connected to each port on the hub. Most 10BASE-T adapters
have indicator lights that signal
whether the link between the adapter and the hub is intact and functioning correctly. Check the documentation for your adapter
to determine the function of each of
the lights. If your adapter has a link status indicator light, but it does not come on when the computer is powered on an the
network cable is plugged in to the
adapter, the cable is bad or is not correctly connected to the hub. Some cards also indicated reversed polarity in the cable by
causing the link status light to flash - in
this case you'll need to replace the cable with one that is correctly wired.
There is one instance where a hub is not required for use with a 10BASE-T network: when there are only two devices being
connected, and a specially made
crossover cable is used. In this instance, the cable is plugged directly into the network adapter on each computer. This will not
work with a standard 10BASE-T
patch cable - you must use a crossover cable that has the send and receive pairs reversed from their standard configuration.
Such cables are usually available from
network supply vendors - you should be very explicit in explaining what you need.
For LocalTalk networks, a LocalTalk connector plugs into the network adapter, with standard telephone wire plugged into an
RJ-11 jack on the connector. Most
LocalTalk connectors have two RJ-11 jacks, allowing devices to be daisy-chained together. If a device is at the end of the
chain, the second jack is occupied by a
terminating resistor plug. A few LocalTalk connectors have lights that indicate the presence of a signal on the wire; most do not.
Troubleshooting Resource Conflicts
If you're properly connected to the network, but you're still not seeing devices, you most likely have a resource conflict with your
network adapter. Open the System
control panel, select the "Device Manager" tab, click on the "Network Adapter" branch to open it, and check the icon for your
network adapter: is there a question
mark or exclamation point icon over it?
If so, it's likely that there's a resource conflict between your network adapter and another device in your computer, or that the
driver for the adapter is not correctly
installed. You can use the System control panel to change settings for most Plug & Play devices; non-Plug & Play devices may
require you to change jumper or
switch settings, or to use a utility program, to change the settings on the device. Once you've resolved any conflicts, restart your
computer and try the AppleTalk
network again.
If you don't see any indication that the card isn't functioning properly, you may have a resource conflict that Windows 95 is not
detecting. A good approach in this
situation is to remove all the installed network components from the Network control panel and reboot, allowing Windows to
reinstall the driver for you. You'll then
need to restore COPSTalk to the Network control panel.
If you're not using a Plug and Play network adapter, you'll still want to remove and reinstall all the network components from the
Network control panel; you'll then
need to reinstall the driver manually. If this is the case, make sure that you do not recreate the resource conflict. Run the
configuration utility for the network adapter
from the adapter's driver diskette. Keep Windows from touching the resources you assign by using the following method. Go to
the System control panel, click on
the Device Manager tab, double-click on "Computer", then click the Reserve Resources tab. From here, you'll be able to
specify resource settings that Windows
can't use but your non-Plug & Play network adapter can. Don't forget to restore the Client for AppleTalk Networks to the
Network control panel.
If you try this approach but still aren't seeing devices, contact COPS Technical Support.
|
|
|
|
|
