Crossover Cable Not Working

[Appletax]

I am using an Ethernet cable with a crossover adapter and I cannot
see either computer.

Both have file sharing enabled. Both are in the same workgroup.



What else can I do?

 

[Robert]

[Apologies if you've already tried these]

IP's set manually? (Both the same range & subnet)
Able to ping from one to the other?
Tested w/o firewall?

 

[Appletax]

[Apologies if you've already tried these]

IP's set manually? (Both the same range & subnet)
Able to ping from one to the other?
Tested w/o firewall?

Why would the IPs have to be static ? Kinda strange

?? e.g. 192.168.2.5 192.168.2.6

I will try that and report back

 

[Ccomp5950]

Why would the IPs have to be static ? Kinda strange

?? e.g. 192.168.2.5 192.168.2.6

I will try that and report back

Because with a cross over cable between the two you no longer have a DHCP server handing out IP addresses. So you have to manually set the IP addresses.

 

[ATTech]

Because with a cross over cable between the two you no longer have a DHCP server handing out IP addresses. So you have to manually set the IP addresses.

That's actually what APIPA was designed for. With the absence of a DHCP server, the computer will decide on an IP address and send out a broadcast to see if anyone already has the IP address, if not, it will assign that address. The subnet and addresses are already handled within the protocol.

Even so, I would also suggest static IPs and make sure you are trying to access it via IP address.

 

[Ccomp5950]

That's actually what APIPA was designed for...

A little bit of reading later, learned a bit. I always thought of 169.* as "Error".

Even still I honestly wouldn't be surprised if Windows doesn't allow sharing over 169.*

 

[MobileTechie]

Prepared to be surprised - because it does

 

[mraikes]

That's actually what APIPA was designed for. With the absence of a DHCP server, the computer will decide on an IP address and send out a broadcast to see if anyone already has the IP address, if not, it will assign that address. The subnet and addresses are already handled within the protocol.

Even so, I would also suggest static IPs and make sure you are trying to access it via IP address.

THAT's why I hang out here. I'm sure the APIPA thing is old news to many of you, but I'd never given automatic private addressing much thought - except as an indication of a DHCP or configuration problem.

But suddenly APIPA is now a tool I didn't even realize I had, and might make certain tasks a bit simpler. Thanks!

 

[DarDar]

THAT's why I hang out here. I'm sure the APIPA thing is old news to many of you, but I'd never given automatic private addressing much thought - except as an indication of a DHCP or configuration problem.

But suddenly APIPA is now a tool I didn't even realize I had, and might make certain tasks a bit simpler. Thanks!

Ditto! I knew what APIPA stood for but i never put 2+2

 

[Appletax]

Both already had an IP address assigned by my ISP.

I changed the IP addresses to a static address:
192.168.1.12 and 192.168.1.13
Subnet: 255.255.255.0
Gateway: 192.168.1.1

I even just created my first crossover cable using the "type a" cable arrangement.

striped green, solid green, striped orange, solid blue, striped blue,
solid orange, striped brown, solid brown.

They are connected and I only see packets being sent but not received.
I cannot see the computers in the Network window.

 

[Martyn]

I am using an Ethernet cable with a crossover adapter and I cannot
see either computer.

Both have file sharing enabled. Both are in the same workgroup.



What else can I do?

Operating systems? Temporarily fit a small 4 port switch and two straight cables. Turn off firewalls and ping each other. Sometimes one way pings can be caused by incorrect subnet mask on one computer.

That's actually what APIPA was designed for. With the absence of a DHCP server, the computer will decide on an IP address and send out a broadcast to see if anyone already has the IP address, if not, it will assign that address. The subnet and addresses are already handled within the protocol.

Even so, I would also suggest static IPs and make sure you are trying to access it via IP address.

Reminds me of some years ago `I got called into a network problem whereby no one could print. It turned out the dhcp server had gone down and they hadn't realised it and all the client pcs had gone onto the 169 network but the printer was on a fixed ip in the 192 range

 

[Appletax]

It works now

I can see both computers. I created a folder on the desktop and shared it out with full permissions for Everyone. I can add stuff to it from my own laptop.

The reason why I need to use a crossover cable is because my SeaGate external hard drive is broke and needs to be sent to SeaGate, but I don't yet have the $20 to get the Advanced Return? option.... No extern. HDD means I can't download software to customer's computers.

 

[Frank]

I even just created my first crossover cable using the "type a" cable arrangement.

striped green, solid green, striped orange, solid blue, striped blue,
solid orange, striped brown, solid brown.

They are connected and I only see packets being sent but not received.
I cannot see the computers in the Network window.

I'm not sure if you terminated both ends of the cable with 568A or not. But to make a crossover cable, one end should be 568A and the other end should be 568B.

 

[Frank]

It works now

I can see both computers. I created a folder on the desktop and shared it out with full permissions for Everyone. I can add stuff to it from my own laptop.

The reason why I need to use a crossover cable is because my SeaGate external hard drive is broke and needs to be sent to SeaGate, but I don't yet have the $20 to get the Advanced Return? option.... No extern. HDD means I can't download software to customer's computers.

Awesome, what was the problem?

 

[Appletax]

I'm not sure if you terminated both ends of the cable with 568A or not. But to make a crossover cable, one end should be 568A and the other end should be 568B.

I used 568A for both ends because the student aid told me that's how to do it : /
It works though

 

[ATTech]

I used 568A for both ends because the student aid told me that's how to do it : /
It works though

A lot of modern computers can detect a straight through cable and adjust accordingly.

You also may want to correct the student aid, since you made a straight through cable.

 

[Appletax]

A lot of modern computers can detect a straight through cable and adjust accordingly.

You also may want to correct the student aid, since you made a straight through cable.

I switched one end to the B type arrangement and now it won't work lol

 

[Paul Rodgers]

Honestly I would just run things through a switch if you can.

Do you have a cable tester available? You might have goofed up on the wiring or have a short that would throw everything off. Very easy to have happen.