To zero n on that as the problem check the switch ports that both the  
inside and outside interfaces of the CAS are connected to.  If they  
are showing CRC errors, collisions or other error conditions thats a  
good clue.... on a Cisco switch this is done with "show int fax/y"  
where X is the blade and y is the interface.  If it is a Gig  
interface then substitute gi for fa.

Ryan Dorman, CCNP
Network Communications Specialist
Millersville University
717.871.5883
[log in to unmask]


On Sep 15, 2005, at 1:13 PM, Brad Kramer wrote:

> I would just check to make sure that your duplexing is set to  
> full... I had
> something similar set up here, and it turned out that auto- 
> negotiation did
> not work well... I think "mii-tool" is installed on the CAS. Try  
> running
> that on the command line to see your interface status. If that  
> doesn't work,
> I guess you could easily get that from the switch.
>
>
> -------------
> Bradley W. Kramer
> Network/Telecom Intern.
> Ashland University
> (419) 289-5630
> [log in to unmask]
>
>
>
> On 9/15/05 12:45 PM, "Deborah Hovey" <[log in to unmask]> wrote:
>
>
>> Hello All,
>>
>> We currently have the servers and manager on our  production  
>> system on the
>> main campus connected through Gig ports.  We have a test lab set  
>> up mimicking
>> the production Manager and adding an additional server for the  
>> satellite
>> campus.  In the lab we have everything set up on 10/100 ports as  
>> it will be at
>> the new site, but everything is painfully slow.
>>
>> Also, when connecting a laptop through a WAP, the server  
>> availability seems to
>> toggle between up and down.  Has anyone else had this problem?   
>> Are Gig
>> connections a requirement?  Any insight is most appreciated.
>>
>> Thanks!
>>
>> Debbie
>> UMW
>