OESF Portables Forum

Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Security and Networking => Topic started by: sargon on October 27, 2004, 04:08:36 pm

Title: Can't connect CF Ethernet to Cisco Catalyst via DH
Post by: sargon on October 27, 2004, 04:08:36 pm

I have a C-860 (Cacko ROM 1.21b), which I am trying to connect to a network through any one of several Cisco Catalyst switches via TRENDnet TE-CF100 card (I have tried two of them). If I configure the network connection for DHCP and DNS via DHCP, the Z tries for a couple of seconds to connect before giving up. If I manually configure DNS and hostname and then try to connect via DHCP, the Z tried for several seconds before giving up. However, If I configure a static address for the card, the Z will connect.

The Catalysts are all configured for auto-negotiate (I know because I administer them).

I use the Z (or would like to use the Z) for checking user connectivity problems, as it is something I can easily carry in a Grinder Gear case.

The problem only exists with Catalyst switches. 3Com, Netgear, and D-link switches do not cause the problem.

I have tried to resolve this for months and I finally give up.

Suggestions will be greatly appreciated.

Title: Can't connect CF Ethernet to Cisco Catalyst via DH
Post by: skoorb on October 27, 2004, 04:34:27 pm

I have the same issues with my cf-100.  there does not appear to be a fix.  We have 6500 series switches here (running catos).   Kind of annoying since we have 6o+ vlans here.


I found this on google groups, but it isn't even completely correct.


TE-CF100:
This adapter may not work with Cisco 4000, 5000, and 6000 series "core"
Switches. The LEDs on the Switch and on the TE-CF100 do indicate a link, but
TE-CF100 does not receive IP from DHCP server and SNMP Software does not
register TE-CF100's MAC address. Using static IP on the TE-CF100 does not
make any difference. However, installing a different 10/100 Switch between
the core Switch and TE-CF100, everything works fine. This is a hardware
(PHY) compatibility problem between TE-CF100 and Cisco core Switch, I have
reported this to Engineering, but there will be no quick solution for this
problem. The "workaround' solution is to install another Switch between the
core Switch and the TE-CF100.
I've already reported your problem to the engineer and the above information
is already recorded in our database.
I will keep you updated if there is any new driver or firmware upgrade.
Sorry for the inconvenience