A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » System Manufacturers & Vendors » Dell Computers
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Old PowerBook and Dell laptop - crossover cable woes



 
 
Thread Tools Display Modes
  #1  
Old February 10th 05, 04:08 PM
anon
external usenet poster
 
Posts: n/a
Default Old PowerBook and Dell laptop - crossover cable woes

Got a weird problem.

Wallstreet Powerbook (233mhz, 30g drive, 384 ram, OSX 10.2.8) and Dell
Inspiron 4100 (1.13ghz, 30g drive, 256 ram, XP Home), hooking them up
with a crossover cable, I can get them to barely ping each other, but
with high packet loss - 25 to 75 percent loss.

They can see each other in their respective network setups, and if I set
up the powerbook as a mapped network drive from the XP machine, it tries
to hook up, but fails 90 percent of the time. Same if I try it from the
Powerbook's end. If they do manage to negotiate, the connection fails
anytime you try to transfer a file.

BTW, when these two machines are on my regular hub as clients
(straight-thru ethernet cable), they see each other fine, network and
transfer files beautifully; I even have the Powerbook set up as a mapped
network drive, working as a file server to the Dell. Can get to the XP
machine from the Powerbook no problem. They work normally.

I saw on a show that more modern macs were able to auto-sense when they
needed a crossover cable, and switched themselves so they do not need it
somehow, so on an off chance that OSX gave my Powerbook this ability I
tried a straight-thru cable between the two - no dice. Nothing when I
tried that.

What do you suppose is happening?

Thanks for any help!
  #2  
Old February 10th 05, 04:16 PM
Ben Myers
external usenet poster
 
Posts: n/a
Default

Possibly a defective crossover cable? They communicate OK with each other when
plugged into a regular network, so the cable is the only difference. If you
need to connect them together outside the confines of your regular network, and
a different crossover cable doesn't resolve the problem, get yourself a cheap
4-port 10/100 hub and connect them together thru the hub.

One other possibility... When connected via crossover cable, how are they
obtaining their IP addresses? Remember, there is not DHCP server to assign IP
addresses in a crossover cable setup. If they do not have fixed IP addresses
and sensible subnet mask when connected via crossover, configure them both with
fixed IP and subnet, and try again... Ben Myers

On Thu, 10 Feb 2005 16:08:09 GMT, anon wrote:

Got a weird problem.

Wallstreet Powerbook (233mhz, 30g drive, 384 ram, OSX 10.2.8) and Dell
Inspiron 4100 (1.13ghz, 30g drive, 256 ram, XP Home), hooking them up
with a crossover cable, I can get them to barely ping each other, but
with high packet loss - 25 to 75 percent loss.

They can see each other in their respective network setups, and if I set
up the powerbook as a mapped network drive from the XP machine, it tries
to hook up, but fails 90 percent of the time. Same if I try it from the
Powerbook's end. If they do manage to negotiate, the connection fails
anytime you try to transfer a file.

BTW, when these two machines are on my regular hub as clients
(straight-thru ethernet cable), they see each other fine, network and
transfer files beautifully; I even have the Powerbook set up as a mapped
network drive, working as a file server to the Dell. Can get to the XP
machine from the Powerbook no problem. They work normally.

I saw on a show that more modern macs were able to auto-sense when they
needed a crossover cable, and switched themselves so they do not need it
somehow, so on an off chance that OSX gave my Powerbook this ability I
tried a straight-thru cable between the two - no dice. Nothing when I
tried that.

What do you suppose is happening?

Thanks for any help!


  #3  
Old February 10th 05, 10:15 PM
Joe Heimann
external usenet poster
 
Posts: n/a
Default

In comp.sys.mac.comm anon wrote:
Got a weird problem.


Wallstreet Powerbook (233mhz, 30g drive, 384 ram, OSX 10.2.8) and Dell
Inspiron 4100 (1.13ghz, 30g drive, 256 ram, XP Home), hooking them up
with a crossover cable, I can get them to barely ping each other, but
with high packet loss - 25 to 75 percent loss.


They can see each other in their respective network setups, and if I set
up the powerbook as a mapped network drive from the XP machine, it tries
to hook up, but fails 90 percent of the time. Same if I try it from the
Powerbook's end. If they do manage to negotiate, the connection fails
anytime you try to transfer a file.


BTW, when these two machines are on my regular hub as clients
(straight-thru ethernet cable), they see each other fine, network and
transfer files beautifully; I even have the Powerbook set up as a mapped
network drive, working as a file server to the Dell. Can get to the XP
machine from the Powerbook no problem. They work normally.


I saw on a show that more modern macs were able to auto-sense when they
needed a crossover cable, and switched themselves so they do not need it
somehow, so on an off chance that OSX gave my Powerbook this ability I
tried a straight-thru cable between the two - no dice. Nothing when I
tried that.


What do you suppose is happening?


Thanks for any help!


The PB 233 is old enough that it does not have autosensing on the
ethernet port that will always negotiate full/half-duplex connections
properly with more modern ethernet ports. The high packet loss rate
is an usual symptom of mismatch between the two ends of the cable. I
would suggest ssticking with using the hub, that forces both laptop
ethernet ports to the same state. The ability to auto-sense is built
into the port hardware, upgrading the OS will not add capabilities to
older hardware that does not support them.

Joe

  #4  
Old February 11th 05, 12:22 AM
Tom Scales
external usenet poster
 
Posts: n/a
Default


"Joe Heimann" wrote in message
...
In comp.sys.mac.comm anon wrote:
Got a weird problem.


Wallstreet Powerbook (233mhz, 30g drive, 384 ram, OSX 10.2.8) and Dell
Inspiron 4100 (1.13ghz, 30g drive, 256 ram, XP Home), hooking them up
with a crossover cable, I can get them to barely ping each other, but
with high packet loss - 25 to 75 percent loss.


They can see each other in their respective network setups, and if I set
up the powerbook as a mapped network drive from the XP machine, it tries
to hook up, but fails 90 percent of the time. Same if I try it from the
Powerbook's end. If they do manage to negotiate, the connection fails
anytime you try to transfer a file.


BTW, when these two machines are on my regular hub as clients
(straight-thru ethernet cable), they see each other fine, network and
transfer files beautifully; I even have the Powerbook set up as a mapped
network drive, working as a file server to the Dell. Can get to the XP
machine from the Powerbook no problem. They work normally.


I saw on a show that more modern macs were able to auto-sense when they
needed a crossover cable, and switched themselves so they do not need it
somehow, so on an off chance that OSX gave my Powerbook this ability I
tried a straight-thru cable between the two - no dice. Nothing when I
tried that.


What do you suppose is happening?


Thanks for any help!


The PB 233 is old enough that it does not have autosensing on the
ethernet port that will always negotiate full/half-duplex connections
properly with more modern ethernet ports. The high packet loss rate
is an usual symptom of mismatch between the two ends of the cable. I
would suggest ssticking with using the hub, that forces both laptop
ethernet ports to the same state. The ability to auto-sense is built
into the port hardware, upgrading the OS will not add capabilities to
older hardware that does not support them.

Joe


You could also force 1/2 or full in the settings.

Tom


  #5  
Old February 11th 05, 03:23 AM
Howard Shubs
external usenet poster
 
Posts: n/a
Default

In article ,
anon wrote:

What do you suppose is happening?


It's not working well. The Wallstreet doesn't know how to auto-sense
squat. Remember, it's not even 100Mb. Use a hub or switch. This isn't
a weird problem; it's just to be expected.

--
Nobody knows Particle Man.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 11:51 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.