I've looked at the only server we have connected through NFS and it is fat dumb and happy. I looked at other log(this machine and others) and this is the only machine that got the error. I also did a netstat -a on all machines and didn't see 2049,so obviously that is the wrong command. I was able to ping all servers. Thanks Mace
-----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Wednesday, September 13, 2006 10:14 AM To: [email protected] Subject: Re: tcp not available message?? On Wednesday, 09/13/2006 at 08:51 EST, =?iso-8859-1?Q?Larry_Macioce?= <[EMAIL PROTECTED]> wrote: > This morning I decided to bring our test and development Linux servers > down and back up as they had been up for a while and were running short of > swap space. I then tried to log back on and was unable to do so to one of > the severs. > I then shut it down from maint and looged into a 3270 VM screen to watch > it reboot. The system started with it's normal messages then hung for > awhile and eventually I got the message: > > mount server reported tcp not available, falling back to udp NFS supports both TCP and UDP connections, but the NFS server has to have indicated its willingness to use TCP. If it doesn't do that, then the client will use UDP. If you can ping the mount server from the guest, then IP connectivity is present and the problem is not in the wires, virtual or otherwise. There could be firewall interference. Check the NFS server to see if it has a TCP listen up on port 2049. Do the console logs of previous logons of the same server show the same message? I.e. is the really a new problem? Alan Altmark z/VM Development IBM Endicott ----------------------------------------- ******************************************************************** The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. ********************************************************************
