Jan wrote: > Maybe it is getting to be the time to try to figure things out with > tcpdump.
> tcpdump -n -p -w codatraffic.dump port codasrv > And then try to access /coda/... Jan Thanks for the reply. Sorry for the delay in replying, I\'ve been on holiday :-) I\'ve tried tcpdump on both the server and client as follows: 1) Execute tcpdump -n -p -w codatraffic.dump port codasrv on both server and client 2) Execute [EMAIL PROTECTED] etc]# ls -l /coda/edm_bfhxx_wb005.edm.mowlem.com lrw-r--r-- 1 root nfsnobod 33 Apr 21 08:42 /coda/edm_bfhxx_wb005.edm.mowlem.com -> [EMAIL PROTECTED] [EMAIL PROTECTED] etc]# cd /coda/edm_bfhxx_wb005.edm.mowlem.com bash: cd: /coda/edm_bfhxx_wb005.edm.mowlem.com: No such file or directory [EMAIL PROTECTED] etc]# on client. 3) Output from client [EMAIL PROTECTED] root]# tcpdump -n -p -w codatraffic.dump port codasrv tcpdump: listening on basp0 0 packets received by filter 0 packets dropped by kernel [EMAIL PROTECTED] root]# more codatraffic.dump Ôò¡` [EMAIL PROTECTED] root]# 4) Output from server [EMAIL PROTECTED] root]# tcpdump -n -p -w codatraffic.dump port codasrv tcpdump: listening on eth0 0 packets received by filter 0 packets dropped by kernel [EMAIL PROTECTED] root]# more codatraffic.dump Ôò¡` [EMAIL PROTECTED] root]# It appears not much is happening at all. Any suggestions? I also tried ports 370, 2430, 2432 and 2433 on the client with no result. I hope that I understood your instructions about accessing the /coda/ ... directory correctly. If not my apologies. Thanks again for your help. Paul ***************************************************************************** This email and any attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender and do not store, copy or disclose the content to any other person. It is the responsibility of the recipient to ensure that opening this message and/or any of its attachments will not adversely affect its systems. No responsibility is accepted by the Company. *****************************************************************************
