ICE
TCP/IP Products => TCP-PRO => Topic started by: larryj on July 18, 2005, 03:32:10 pm
-
We get these frequently in the Linux log.
What does this mean? Does it need attention?
find_response_record: response packet id 56152 received with no matching record.
find_response_record: response packet id 56155 received with no matching record.
find_response_record: response packet id 56158 received with no matching record.
find_response_record: response packet id 56161 received with no matching record.
find_response_record: response packet id 56164 received with no matching record.
find_response_record: response packet id 56170 received with no matching record.
-
Looks like it's nothing to do with ICE. A search reveals that it's related to SAMBA.
Take a look at the following:
https://www.redhat.com/archives/redhat-list/2004-October/msg00245.html
-
So sorry my error. I grabbed the wrong lines.
Those are:
tci-couns-11 (192.168.2.197) couldn't find service j river
tci-couns-11 (192.168.2.197) couldn't find service j river
tci-couns-11 (192.168.2.197) couldn't find service j river
-
Never seen that before. If it is ice related, maybe it's got something to do with your ice.lp setup (if you are using ice.lp, does it work ok?)
-
No, we do not use ice.lp. We get 12-15 daily ICE Pro disconnects from numerous computers everyday. However, most come from this particular client, TCI-Couns-11.
New HP DL380 service running SCO UNIX OperServer 8.
New CISCO Managed switches.
Have no routers.
-
Still looks like a SAMBA issue. Look for references to "river" in your smb.conf file.