Yes I had that exact message. However after some troubleshooting the 
network guys found that one of the gbx? modules was not working and 
replaced it. The replacement fixed one of the interfaces but not the 
other. It continues to fail to link no matter what is plugged into it. 
We thought maybe it would only link if the other server was down but 
that proved not to be true. We are now thinking the card may have just 
gone bad.

Cal Frye wrote:
> Any console messages on that server? When I get troubles like this, I see the
> error message "ToDevice eth1 rejected a packet!" This happens to all my servers
> from time to time...
> 
> --Cal Frye, Network Administrator, Oberlin College
>    www.ouuf.org, www.calfrye.com
>    Say Yes Twice for Oberlin Schools!   www.oberlinyesyes.com
> 
>   "People demand freedom of speech to make up for the freedom of thought which
> they avoid. " - Soren Aabye Kierkegaard (1813-1855)
> 
> 
> Aaron Havens wrote:
>> The question came up because we were having problems with one of our
>> VLANs. Users on that VLAN can pull a DHCP address but can't go anywhere
>> else on the network. (We use DHCP relay) The Agent has the Login option
>> grayed out. If the users computer is moved to another CCA managed vlan
>> it works fine.
>>
>> The networking group said they haven't changed anything and we haven't
>> changed anything on our end with the server so I was hoping maybe the
>> problem could be resolved by rebooting.
>>
>> We currently have had 92 days of uptime with no problems. However when I
>> went to reboot the fail over servers I found that one of them did not
>> have a link on the switch. So now we are troubleshooting that.
>>
-- 
Aaron Havens
Network Technician
Computing and Telecommunications
Northeastern State University
610 N. Grand
Suite 318
Tahlequah, OK 74464
http://netnotes.nsuok.edu/~havensa/
918-456-5511 Ext. 5813