> > > Flaky switch? (Too) long or bad (non-standard) cabling? That was > > > usually the explanation when I was seeing such behaviour. > > > > > Not sure what you mean about hijacking the thread, but I am > sorry -- I > > didn't mean to do anything wrong. > > No, you're only hurting yourself: Thread hijacking describes > using the "reply" facility of your email program to start a > new thread (instead of starting a new, fresh email, e.g. by > clicking on the ML address). > Email agents that make use of information in the mail headers > for displaying threads will show your mail inside the > structure of an existing thread. Some people might not even > find your message buried in there. See the following link for > knowing what I mean: > http://groups.google.com/group/linux.gentoo.user/browse_frm/th > read/601571a0fced1a73/e17f8a0483af6690?tvc=1 > > > > As far as the switch, its on a hub that is on the span port of a > > foundry switch (the hub is used as a poormans network tap -- I have > > seen the same type of failure on machines directly connected to a > > switch also) > > > > The cable is a commercially manufactured cable that tests out > > correctly > > - -its about 6 feet long > > Did you try if it works with another cable, on another port > of the switch/hub? That would be proper exclusion of probable > errors. You're description tells me what you have, but not if > it's working right now. > > HTH, > > -hwh > -- > gentoo-user@gentoo.org mailing list > >
Hans: Thanks for the explaination -- Outlook strikes again :( I will change the way I do things As far as the problem, I am going to try new hardware and see what happens TIM Timothy A. Holmes IT Manager / Network Admin / Web Master / Computer Teacher Medina Christian Academy A Higher Standard... Jeremiah 33:3 Jeremiah 29:11 Esther 4:14 -- gentoo-user@gentoo.org mailing list
