Mathias Wohlfarth
2002-Feb-05 06:07 UTC
Antwort: Re: [Samba] Re: accessing samba across two different subnets
Does your winNT point to the samba-server as the wins server? If yes - it look more that you have a problem with your gatway. regards MW "Madhvi Nundalalee" <madhvin@yahoo.com>@lists.samba.org on 05.02.2002 06:10:51 Gesendet von: samba-admin@lists.samba.org An: <samba@lists.samba.org> Kopie: Org.Element: Telefon: Thema: Re: [Samba] Re: accessing samba across two different subnets hello I have set wins support = yes However, I have not included the name resolve order setting in smb.conf. I have set name resolve order = wins lmhosts bcast The PC that is having problems has winnt worksattion as OS. ----- Original Message ----- From: "Martin Thomas" <mthomas@rhrk.uni-kl.de> To: <samba@samba.org> Cc: <madhvin@yahoo.com> Sent: Monday, February 04, 2002 9:07 AM Subject: [Samba] Re: accessing samba across two different subnets> >hello > > > >PC a is connected on the same subnet as the samba server. It takes > >around 3 seconds to open a document(word) via Windows explorer . > >PC B is connected on a different subnet and it takes at least 15 s to > >access same document as PC A. > > > >can anyone comment on this problem ?/? > > > >Cheers > >madhvi > > Do you have a WINS-Server? Creating one might help you if you > do not already have one. > What are the settings for the "name resolve order"-parameter > in your smb.conf? > > Martin > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: lists.samba.org/mailman/listinfo/samba >_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at mail.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: lists.samba.org/mailman/listinfo/samba
I have a problem with SAMBA that I'm hoping someone will know something about. I have compiled and configured SAMBA 2.2.2 a number of ways and have found that I always get VERY slow (30-60 seconds) browse access from my various Windows machines. Whenever a Windows client tries to browse a share SAMBA goes through quite a lot, but with 'debug level = 4' I can see in my log.smbd file many attempts to find and open 'DESKTOP.INI", some of which can take 30 seconds, all of which fail. Samba looks in several places for this non-existent file before giving up. It fails to find the file, but not until my official DNS server at my ISP gives up. So after a LOOOONG delay, the originally requested share is opened and displayed to the client. I understand the reason that this is happening, it's actually the Windows client asking for the file and recursing the directory tree if it can't find it, it's not truly a problem with SAMBA itself. Can anyone tell me how to correct or work around this? In my rather exhaustive Internet search for a resolution to this issue I've seen the question asked many times but never seen an answer. Thanks to all, Jason Farque