What'd i miss?
ok i've two computors i tring to link using
One is a Compaq with a Pci card built in to the motherboard the other is a Celeron with a add in card.
I've set both cards up,installed ipx and tcp/ip protocalls clients etc.(ipx is default)
The NIC for the Celeron system came with a dionostic's disk and everything checks out allright.(Card and cable to other comp)
Under Network neighbourhood i can see the name of the computor i'm currently on and the workgroup it belongs to but i can't see/accsess the other comp.(I get the same results on both comps)
Any idea's on what i've missed?Do i have to tell the system i'm using a Twisted Pair cable or something?
Any help much appricated.
Are you using a HUB? If not you have to use a "CROSSOVER" cat5 cable. If you are using a HUB then you can use regular cat5 cables. It sounds like you NEED A CROSSOVER CABLE.
Still leaning the terms
Yes i asked the guy to cross the wires when he made the cable and i just found a site that listed the wiring code for crossover.
All checked out fine.
I've set up a connection on that black round stuff (thin eithernet?)before so i did this system basically the same. Is their anything different?
Could one of the wires in the cable be broken? How many have to be ok to pass the cable connected test?
[This message has been edited by Hurt_Me_Not (edited 06-12-99).]
The compaq doesn't have a light but the Celeron does and that goes a steady green when the cord's pluged in.
Would it be a direct short that a multimeter would pick up?
I set up the address about 2am last night.
But i didn't delete the other setings first.
I'll go try that now.
Thanks for all the reply's
If the link lights come on, on both nics. That mean there is no broken wires and it's the right type of cable. But sometimes a cable can still be bad even though the lights come on. That happens when there is current transfering between the wires.
The setup would be basically the same (in the configuration) between using the Cat5 cable and the coax. What I would personally do at this point would be to first make sure I dont have any conflict with the NIC cards, 2nd I would remove all items from network configurations (reboot) then start from scratch. (1st) set up client for Microsoft networking (make sure you set the computers to the same DOMAIN. (2nd) ethernet adapter. (3rd) TCP/IP Protocol (set up very basic tcp/ip just the IP address and subnet mask...make sure you have different address for the IP on the different computers BUT HAVE SAME subnet mask (255.255.255.0) (4th) file and printer sharing for microsoft networking. and make sure you set the hard drives or individual files to SHARING. If they are not set to sharing you might beable to attach to the other computer but you will not "see" anything.
Hope this helps!
[This message has been edited by Mntsnow (edited 06-12-99).]
*** If you need IPX/SPX for a game or such or you can't change the default(can't see why not)look under control panel|network|configuration tab and highlight your NIC adapter <--->IPX/SPX and click properties.Click frame types and make sure the value is AUTO. If this still doesn't resolve change the value to 802.3 on both machines.IPX can't see other machines if frame types aren't the same.
[This message has been edited by sourjon (edited 06-14-99).]
It was on Auto but i read one of the replies to a eariler question and tried 802.3
I think the card in the Compaq is suss.
I'll let you know how i go.
[This message has been edited by BC (edited 06-14-99).]
You might want to also check file and print sharing on. This will let you see the other pc. But it sounds like you have a bad card/driver issue.
Set up Microsoft NetBeui Protocol on both machines. It is by far and away the most forgiving protocol for small LANs.
If you are using coax (thin eithernet), make sure you have a terminator on each end of the cable. Each system must have a "tee" connector attached to the card, the cable attached between each card, and a terminatod at each "end" of the lan.
If the cabling is correct, and the network setting are correct, both systems should be talking.
Hope this helps.
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke