I've seen this question asked on the list, but never answered. I've tried searching the archives, etc., but don't find anything relevant. I have a network with several Win95 and 98 client machines and one NT4 machine (NT Workstation, not Server). It's currently using Novell, but I've been testing a Samba server as a replacement. The 95 and 98 clients work fine. When I browse the network, the server appears, I can open it, look at the shares, etc. Everything is quick and correct. Even printing works fine. On the NT machine, however, it takes up to a minute to open the Samba Server in Network Neighborhood. It takes up to another minute to open any of the shares. If I run "NET USE" from a command-line window, it takes the same amount of time to complete. Once the share is mapped to a drive, it works fine for a while, but after a time, you can't open "My Computer" without another long wait, and can't access the mapped drives without another long wait. This is Samba 2.0.3 on RedHat 5.2, but I'm having a similar problem on a test box running 5.1 and an older version of Samba. The NT system was at SP3, and is now at SP4. The upgrade had no effect on the operation. Defining a WINS server on the NT system had no effect, other than to make the "Workstation" service fail to start most of the time. I'm using SECURITY=USER, and everything else seems to be working fine. I had tested this setup with NT Server a while back, and I vaguely recall having similar problems with it, but I gave up on it for other reasons before I had a chance to figure out what was wrong. Because of this, I suspect the problem is on the client side. Anyone have any ideas?
Ken Hall wrote: | On the NT machine, however, it takes up to a minute to open the Samba Server | in Network Neighborhood. It takes up to another minute to open any of the | shares. This sounds a lot like the NT machine has several protocols configured: if you have TCP/IP, Novell and NetBlooie turned on, bit only one is responding, you get several 30-second timeouts as the client machine tries NetBEUI, Novell and then IP for some of its operations. --dave -- David Collier-Brown, | Always do right. This will gratify some people 185 Ellerslie Ave., | and astonish the rest. -- Mark Twain Willowdale, Ontario | http://java.science.yorku.ca/~davecb Work: (905) 477-0437 Home: (416) 223-8968 Email: davecb@canada.sun.com
When the world was young, "Hall, Ken (ECCS)" <KeHall@exchange.ml.com> carved some runes like this:> I have a network with several Win95 and 98 client machines and one NT4 > machine (NT Workstation, not Server). It's currently using Novell, but > I've been testing a Samba server as a replacement. The 95 and 98 clients > work fine. When I browse the network, the server appears, I can open it, > look at the shares, etc. Everything is quick and correct. Even printing > works fine. > > On the NT machine, however, it takes up to a minute to open the Samba > Server in Network Neighborhood. It takes up to another minute to open any > of the shares. If I run "NET USE" from a command-line window, it takes > the same amount of time to complete. Once the share is mapped to a drive, > it works fine for a while, but after a time, you can't open "My Computer" > without another long wait, and can't access the mapped drives without > another long wait. > > This is Samba 2.0.3 on RedHat 5.2, but I'm having a similar problem on a > test box running 5.1 and an older version of Samba. The NT system was at > SP3, and is now at SP4. The upgrade had no effect on the operation. > Defining a WINS server on the NT system had no effect, other than to make > the "Workstation" service fail to start most of the time. I'm using > SECURITY=USER, and everything else seems to be working fine.You could try having the NT box use an lmhosts file instead of WINS; I use the #PRE option for the samba server. It might also be related to the specific services running under NT (they won't let me near an NT admin account, 'cause I'm a linux dude :) We have a similar setup here (mostly win95, 1 win98, 1 NT4SP3 workstation, 1 linux/samba box) but NT seems to access the samba shares just as fast as the win95 clients (even faster on the linux /usr/doc tree, but the NT box is our fastest machine - PII-450). We don't use WINS, we have no PDC, and only a simple LAN with no subnets. I have samba running as the master browser, with most of the win clients disabled (as far as browse master competition). All machines use lmhosts for NetBIOS names, and hosts for internal DNS names. The samba box is a lowly 486 with 32 megs RAM, but performance is fine (it also runs apache, MySQL, VNC sessions, etc). Even with all the system updates, win95 still can't Net View the NT box (but it works with samba): C:\WINDOWS>net view \\rama Shared resources at \\RAMA Sharename Type Comment -------------------------------------------------- arnold Disk Your Home Directory docs Disk Linux docs public Disk HTML Document Tree smb Print lp smbps Print lp0 source Disk Source Code tmp Disk Temporary file space The command was completed successfully. C:\WINDOWS>net view \\mothra Error 234: Additional data is available. Obviously, the M$ networking stuff is hosed from one platform or service pack to another (or, How do you say in your country... It's completely FUBAR'd). If you really want to alleviate these headaches, I think the only option is to bail NT and get linux on those clients. The development tools are much better, and there are numerous open source packages (depending on your requirements) that can fill most needs. Never miss a chance to evangelize... Steve ****************************************************************** Stephen L Arnold http://www.rain.org/~sarnold #include <std_disclaimer.h> ******************************************************************
> Date: Mon, 10 May 1999 09:24:38 -0400 > From: "Hall, Ken (ECCS)" <KeHall@exchange.ml.com> > To: Multiple recipients of list <samba@samba.org> > Subject: Performance (?) problem with Samba and NT > Message-ID: <59523CAF2AA3D111A8AB00805FE67F2E6F3BBA@ewst03.exchange.ml.com> > > I've seen this question asked on the list, but never answered. I've tried > searching the archives, etc., but don't find anything relevant. > > I have a network with several Win95 and 98 client machines and one NT4 > machine (NT Workstation, not Server). It's currently using Novell, but I've > been testing a Samba server as a replacement. The 95 and 98 clients work > fine. When I browse the network, the server appears, I can open it, look at > the shares, etc. Everything is quick and correct. Even printing works > fine. > > On the NT machine, however, it takes up to a minute to open the Samba Server > in Network Neighborhood. It takes up to another minute to open any of the > shares. If I run "NET USE" from a command-line window, it takes the same > amount of time to complete. Once the share is mapped to a drive, it works > fine for a while, but after a time, you can't open "My Computer" without > another long wait, and can't access the mapped drives without another long > wait. > > This is Samba 2.0.3 on RedHat 5.2, but I'm having a similar problem on a > test box running 5.1 and an older version of Samba. The NT system was at > SP3, and is now at SP4. The upgrade had no effect on the operation. > Defining a WINS server on the NT system had no effect, other than to make > the "Workstation" service fail to start most of the time. I'm using > SECURITY=USER, and everything else seems to be working fine. > > I had tested this setup with NT Server a while back, and I vaguely recall > having similar problems with it, but I gave up on it for other reasons > before I had a chance to figure out what was wrong. Because of this, I > suspect the problem is on the client side. > > Anyone have any ideas?Do you have Novell Client 32 installed on the NT machine? I have this problem on my NT machine which does use Client 32. Several other NT boxes with MS client work just fine. Coincidence?? BRG
Thanks to all the folks on the list who offered suggestions on this. I think I found the problem. In desperation, I installed a new copy of NT on a fresh disk and tested different combinations, and it seems to work best with just Windows Networking and TCP/IP configured. Adding the Microsoft Client for Novell slowed things down a little, but initial access to the NetWare server was much slower than to Samba. Adding the 32-bit Novell client made the NetWare server nice and quick, but the initial connection and later reconnection to the Samba server slowed to a crawl. I checked the Novell site for info on this but didn't come up with anything. I'm not going to pursue it because the new server goes live next weekend so it becomes academic anyway.