Re: [OT] Any Cisco Knowledge Lurking here?

["Dean Smith" <dean@xxxxxxxxxxxxxxx>]

Do you have a model number ? and do you have Telnet or Console access ?

Without knowing the exact slimserver discovery mechanism its hard to say
why it would be an issue - but I've seen various issues in the past with
Cisco switches that involve timing of spanning-tree convergence and MAC
address tables etc that for a small network can be eliminated fairly
quickly with a bit of config

Dean
----- Original Message -----
From: nick@xxxxxxx
To: ukha_d@xxxxxxx
Sent: Tuesday, December 14, 2004 9:30 PM
Subject: [ukha_d] [OT] Any Cisco Knowledge Lurking here?



I have a couple of Squeezeboxes.  Like the rest of my network, they
live around a 12 port Cisco switch.  Whenever I upgrade the
Slimserver software, it has to "discover" the two Squeezeboxes
again.  This does not work.....

The workaround is to temporarily join up the Slimserver machine and
the two Squeezeboxes via a hub.  Slimserver then finds the boxes.  I
can then put all the cables back to the switch as they were before
and all is well (until the next time!).

I am completely Cisco-ignorant - it was ex-work and saved from the
skip, on the grounds that all the books say a switch is better than
a hub......

I can only assume that the thing is either blocking port 3483 on TCP
and/or UDP (might as well be Chinese for all that means to me).  I
think I have done a factory reset which, I think, means that the
thing should "just work".

Obviously not!  All pointers welcome!  Thanks.

Nick

PS - the obvious answer is to use the hub and link that to the
switch for access to the rest of the network.  Yes, probably, but I
like a challenge!