JimtheJock
IS-IT--Management
3com 3300 Superstack 2 (3c16980) with fibre module linking to 3com baseline 10/100 superstack 3 (3c16465c).
There have always been 5 PCs connected to superstack 2. Recently, 3 of these PCs changed. Old Digital 3000s running Win95 replaced with Dell Optiplex GX270 with Intel Pro 1000 MT NiCs running WinXP Pro. Until these PCs were changed there were no network problems. The NICs were set for auto negotiate but have been changed to 100 full, 100 half and 10.
Message appears in Outlook 2003 - Connection to the Exchange Server has been lost. Outlook will restore the connection when possible. (Exchange 2000 is used, on server connected to Superstack 3).
The message only appears in the application log of one of the Dell PCs - it can be any one of the three Dells.
This results in a client/server accounting application hanging on all 5 PCs connected to the Superstack 2.
No PCs connected to the Superstack 3 are affected at all.
Everyone points to the Superstack 2 as being the problem except for one MS "expert" who reckons that the problem lies within the XP Pro configuration.
Has anyone experienced this or similar problem. I want to replace several more PCs but don't want to run risk of hanging the accounting application on the main network segment.
There have always been 5 PCs connected to superstack 2. Recently, 3 of these PCs changed. Old Digital 3000s running Win95 replaced with Dell Optiplex GX270 with Intel Pro 1000 MT NiCs running WinXP Pro. Until these PCs were changed there were no network problems. The NICs were set for auto negotiate but have been changed to 100 full, 100 half and 10.
Message appears in Outlook 2003 - Connection to the Exchange Server has been lost. Outlook will restore the connection when possible. (Exchange 2000 is used, on server connected to Superstack 3).
The message only appears in the application log of one of the Dell PCs - it can be any one of the three Dells.
This results in a client/server accounting application hanging on all 5 PCs connected to the Superstack 2.
No PCs connected to the Superstack 3 are affected at all.
Everyone points to the Superstack 2 as being the problem except for one MS "expert" who reckons that the problem lies within the XP Pro configuration.
Has anyone experienced this or similar problem. I want to replace several more PCs but don't want to run risk of hanging the accounting application on the main network segment.