Discussion Locked

MS SFU3.5 Slow to open an NFS session to Unix

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After installing Misrosoft Services For Unix 3.5 I find that when opening a network file or even doing a directory list to an NFS connected (Linux/Unix) server it initially takes forever.

In NT 4.0 this was fixed with a new MUP.SYS file a Registry edit to change DisableDFS and was referred to as "Connectivity Delay with Multiple Redirectors Installed".

I am hoping someone has seen the same problem and has a fix. SFU is nice for NFS but the users hate the slooow initial responses.

Thanks,
Ken

3 replies

by stress junkie

You should have already done this but you didn't mention it in your post. Try to find the sequence of events that is being taken by the computers involved in the network connections. Look at the log files on the Linux server. Look at the log files on the clients. I have found that network connectivity problems are often related to security.

If you find that the problem is, in fact, coming from the Microsoft Services for Unix software then consider the alternative. Put Samba on the Linux server and make it a part of the M$ network. That will remove a network protocol from the client once M$ 4 Unix is removed and you will enjoy the convenience of having one security model for network access. This will simplify your life and reduce the possibilities of creating security weaknesses.

I have expressed in other discussions that I am NOT a fan of NFS. I love Linux. I hate NFS. I believe that the SMB network protocol is technically better than NFS. And, just in case you're wondering, SMB was created by IBM, not M$. That's probably why M$ hasn't stopped the Samba software project, but let me stress PROBABLY. I really don't know for sure.

by kemartin

I understand your dislike of SFU and NFS.

However I have to connect to two HP Unix boxes running HP/UX 10.20 and a couple of Windows shares to both NT and Win2K servers.

As an aside while at the DOS prompt doing a DIR K: for example immediately returns the directory while doing a directory from within My Computer can take up to 20 or so seconds? What would make the difference if getting a directory from DOS or within Windows when they are both using SFU?

Thanks

by stress junkie

... about the details of SFU. I wasn't criticizing SFU in my previous post, just NFS.

The difference in behavior between the DOS box and the My Computer interfaces is a good observation. I would still check the log files on the client and on the NFS servers for more information.

Beyond that I'm afraid that you'll have to hope that someone who knows more about Windows networking than me replies to your request for help.

This discussion is closed to new replies.