08-11-2011 09:24 PM
I am getting continual messages as below in my syslog server:
Local7.Error chiwad01 2011 Aug 12 00: java: %WAAS-CIFSAO-3-131207: (288163) Error replying to client 172.16.6.167.
How do I find out what the problem is ? only get this on this one server
regards
Solved! Go to Solution.
08-11-2011 10:29 PM
Hi,
Is 172.16.6.167 client or server? Whatever it is, this server / pc is either virus infected / is opening constant CIFS connections, may cause slowness across device. These kind of error messages arise in the situation where :
1. A PC is infected wit hVirus / trojen and opening "n" number of remote connections.
2. A server that has AntiVirus software installed may cause this when it pushes AV signature updates to the clients.
3. A server that has any sort of security scanning software installed can cause "n" number of connections to open.
3. A server that has any sort of inventory management software installed can also cause this sort of situation.
In otehr words, this PC / server needs to be analyzed to find out why it is opening so many connections. Is it suppose to open so many connections?
This is not WAAS problem but rather that particular PC / server problem. You may want to run CLI command --> sh stat conn | inc 172.16.6.167
to find out how many open connections this client has.
Hope this helps.
Regards.
PS: If this answers your question, please mark this as Answered.
08-11-2011 10:29 PM
Hi,
Is 172.16.6.167 client or server? Whatever it is, this server / pc is either virus infected / is opening constant CIFS connections, may cause slowness across device. These kind of error messages arise in the situation where :
1. A PC is infected wit hVirus / trojen and opening "n" number of remote connections.
2. A server that has AntiVirus software installed may cause this when it pushes AV signature updates to the clients.
3. A server that has any sort of security scanning software installed can cause "n" number of connections to open.
3. A server that has any sort of inventory management software installed can also cause this sort of situation.
In otehr words, this PC / server needs to be analyzed to find out why it is opening so many connections. Is it suppose to open so many connections?
This is not WAAS problem but rather that particular PC / server problem. You may want to run CLI command --> sh stat conn | inc 172.16.6.167
to find out how many open connections this client has.
Hope this helps.
Regards.
PS: If this answers your question, please mark this as Answered.
08-15-2011 12:58 AM
Thanks for your response I'll pass this on to my Server guys
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide