Mark, items 1-4 should not pose any problem. item 5 I have started with item 6-9 I will discuss with our network staff Tx for the pointers Frank
> ----- Original Message ----- > From: "Mark Perry" <[EMAIL PROTECTED]> > To: "Servers Alive Discussion List" <salive@woodstone.nu> > Subject: RE: [SA-list] Error code 1460 > Date: Tue, 07 Oct 2008 20:25:38 +0200 > > > You don't give enough info and I don't blame you so here is a generic > list of gremlins which may be loose in your network..... > > 1. Has any core network infrastructure changed? > 2. Are the timeout Alerts coming from a single or a few servers in the > same geographic or topological area or all areas? > 3. Though you have tried installing SA on another server is this new > server running the latest updates. It May be that a new M$ or AV or > other patch has slowed networking. > 4. What other possible changes have been made to affected servers e.g. > software/hardware upgrades, patch management, new software, new > switches, mismatched managed switches e.g. netgear and 3com on same > network segment (breaks ability to auto build spanning trees and > management traffic between switches doesn't work). > 5. Try running wireshark on different network segments a look for > network storms. > 6. Actually go and look at your network switches normally the lights > will be flashing randomly but if you see a switch with constantly lit > activity on all ports you may have an overloaded switch. I have seen > this when a netgear switch was double connected to a 3com switch - this > produced a network loop with both switches effectively saying this way > to each other for a single infinite ping packet let alone all the other > traffic. > 7. Log onto all managed switches and check throughput on all ports. > 8. Make sure a firewall isn't in the way and messing with your traffic. > 9. Has anyone deployed a deep packet inspection device or enabled DPI > on a firewall. > > > There is loads of stuff to check but hopefully this list will give you a > few ideas. > > > Mark Perry > > Systems & Networks Administrator > > Telephonetics VIP Ltd > > > > "making sound > > business sense" > > > > Simply dial +44 (0)1442 242 242 and ask for me by name. > > www.telephoneticsVIP.co.uk > > Providing innovative hosted and customer premises speech recognition and > voice automation solutions. > > > > Disclaimer: available at > http://www.telephoneticsVIP.co.uk/telephonetics/emaildisclaimer.jsp or > by sending email to <mailto:[EMAIL PROTECTED] > applies to this email. > > Registered address: 7th Floor, Hamilton House, 111 Marlowes, Hemel > Hempstead, Hertfordshire HP1 1BB > > Registered in England No: 2831215 > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Frank Schnell at home > Sent: 07 October 2008 18:35 > To: Servers Alive Discussion List > Subject: [SA-list] Error code 1460 > > Hello all, > > we are running since a few years a SA instance. Occasionally > there were false alerts when checking Windows process/services. > The extra informatiobn showed error code 1460 (time out) > even though the service was running happily. About 8 weeks ago > these false alerts increased to about 15 a day. Since a week > we have about 200 of these per day. The average time out value > is 2-3 seconds. > > I do understand that this is not a time out problem with the > actual check settings in SA. I increased it to 300 sec and still > the same problem. > > The problem lies somewhere else, but where? Could someone elaborate > on how that check is actually being performed. We do use authentication > data per check on Windows services/processes. From a Wireshark dump > I see that WMI is somehow involved. How can a analyse this problem? > > We already installed SA on a different, brandnew computer, to ensure > it is not a problem with the computer SA is running on. No change. > > Any hints, tips and tricks are welcome. > > Tx > Frank > > -- > _______________________________________________ > Surf the Web in a faster, safer and easier way: > Download Opera 9 at http://www.opera.com > > Powered by Outblaze > > To unsubscribe send a message with UNSUBSCRIBE in the subject line to > salive@woodstone.nu > If you use auto-responders (like out-of-the-office messages), make sure > that they are not sent to the list nor to individual members. Doing so > will cause you to be automatically removed from the list. > > > > > -------------------------------------------------------------------------------- > > Telephonetics VIP is a limited company registered in England and > Wales. Registered number: 2831215. Registered office: 7th Floor, > Hamilton House, 111 Marlowes, Hemel Hempstead, Hertfordshire, HP1 > 1BB. > > The disclaimer available at: > http://www.telephoneticsvip.co.uk/telephoneticsvip/emaildisclaimer.jsp , > applies to this message and any associated files. > > > -------------------------------------------------------------------------------- > > To unsubscribe send a message with UNSUBSCRIBE in the subject line > to salive@woodstone.nu > If you use auto-responders (like out-of-the-office messages), make > sure that they are not sent to the list nor to individual members. > Doing so will cause you to be automatically removed from the list. > -- _______________________________________________ Surf the Web in a faster, safer and easier way: Download Opera 9 at http://www.opera.com Powered by Outblaze To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
