Re: [Samba] samba - xp -ad issue
On Wed, Dec 15, 2010 at 09:38:32AM -0500, Jim Flanigan wrote: > I have a samba 3 server connected to an windows domain. > All connections appear correct most of the users can > connect via windows xp with no issue. However there are a > unlucky few whose work stations cannot connect. All xp > work stations are the same (at least as well as a large > company can get). The user in question have ad accounts on > the Linux server. We use ad as the userid source and > Kerberos authentication on the *nix machines. So user I'd > and passwords are not the issue. > > The error received is that the network path is not > available, xp takes about 5 minutes to determine that the > path is not available. The issue does not appear to be > location dependent. Two users seated 10 feet from each > other one will have the issue the other will not. It > appears as though the issue is workstation level. I have > turned on level of debugging info but nothing obvious > stands out. > > Are there an suggestions? Probably doing network traces on the workstations is the only way to sanely diagnose what's going on. www.wireshark.org has the required software. Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba - xp -ad issue
I was hoping that someone has seen a similar problem to the one I am facing. I have a samba 3 server connected to an windows domain. All connections appear correct most of the users can connect via windows xp with no issue. However there are a unlucky few whose work stations cannot connect. All xp work stations are the same (at least as well as a large company can get). The user in question have ad accounts on the Linux server. We use ad as the userid source and Kerberos authentication on the *nix machines. So user I'd and passwords are not the issue. The error received is that the network path is not available, xp takes about 5 minutes to determine that the path is not available. The issue does not appear to be location dependent. Two users seated 10 feet from each other one will have the issue the other will not. It appears as though the issue is workstation level. I have turned on level of debugging info but nothing obvious stands out. Are there an suggestions? Jim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba xp and ad files
Hello What is the best methode to upload a policy settings to the samba netlogon directory for a network of XP computers. Upload the .adm files ? Thanks in advance Guy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - XP performance problem
On Fri, Aug 12, 2005 at 12:00:19PM +0200, David Beck wrote: > Ooops. I tried with copy from the cmd shell and made a few experiments > with that. You are right, it does not show the performance problem. > > I used Total Commander for copying the files, so I looked into the > configuration options and found that it has some "way too smart" options > for copying files. It used small buffers to speedup the transfer of > small files (default option). If I set compatibility mode for the Samba > drive then it works fine. > > Sorry for wasting your time and thank you for the tests you made. That > helped. No problem, that helps a lot to know we don't have a performance issue here. > Best regards, > David. > > PS: TC: Crap software of a crap architecture. On that we *both* agree :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - XP performance problem
Ooops. I tried with copy from the cmd shell and made a few experiments with that. You are right, it does not show the performance problem. I used Total Commander for copying the files, so I looked into the configuration options and found that it has some "way too smart" options for copying files. It used small buffers to speedup the transfer of small files (default option). If I set compatibility mode for the Samba drive then it works fine. Sorry for wasting your time and thank you for the tests you made. That helped. Best regards, David. PS: TC: Crap software of a crap architecture. Jeremy Allison wrote: On Thu, Aug 11, 2005 at 11:50:25PM +0200, David Beck wrote: I copied large files. First I tried a CD image around 600 Megs. Later I realized that 50 Megs is good enough for testing this. I think anything around 25 Megs would do. Exactly how did you copy them ? I'm using a 200Mb file and don't see it. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - XP performance problem
On Thu, Aug 11, 2005 at 12:39:55PM -0700, Jeremy Allison wrote: > > Ok, I'm using the "disk test" part of www.passmark.com and can reproduce > the "1 byte write every 64k followed by a qfilinfo" call against Samba, > latest SVN code - but it also does the same against my Windows 2003 SP1 > server Looking closely, the "disk test" here does the 1 byte per 32k write until it's set the "full size" for the test - then does writes. The "full size" for the test seems to be related to the size of the underlying disk you're testing. I don't see a difference in behaviour between Samba3 and W2K3 here with an XP client. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - XP performance problem
On Wed, Aug 10, 2005 at 11:05:06AM +0200, David Beck wrote:
> Thank you for the suggestion. I'll keep the info for reference.
>
> Followup for the performance issue:
>
> The trace shows that the conversation changes right after the "trans2:
> query file info internal" stage, so I looked into the samba code at this
> file:
>
> http://websvn.samba.org/cgi-bin/viewcvs.cgi/branches/SAMBA_3_0/source/smbd/trans2.c?rev=8959&view=markup
>
> case SMB_FILE_INTERNAL_INFORMATION:
> /* This should be an index number - looks like
> dev/ino to me :-)
>
> I think this causes us to fail the IFSKIT
> BasicFileInformationTest. -tpot */
>
> DEBUG(10,("call_trans2qfilepathinfo:
> SMB_FILE_INTERNAL_INFORMATION\n"));
> SIVAL(pdata,0,sbuf.st_dev);
> SIVAL(pdata,4,sbuf.st_ino);
> data_size = 8;
> break;
>
> The comment speaks for itself. I suspect the 8 byte here contains some
> magic that makes XP behaves as I found.
>
> I made an other experiment: I turned off the oplock support ("Oplocks =
> No") and this made XP behave like if it was talking to a Windows server.
> No extra tran2 calls and 1 byte writes. The performance got better
> because the slowdowns disappeared, but it was still slower compared to
> the windows machine.
Ok, I'm using the "disk test" part of www.passmark.com and can reproduce
the "1 byte write every 64k followed by a qfilinfo" call against Samba,
latest SVN code - but it also does the same against my Windows 2003 SP1
server
BTW: - just using a cmd.exe prompt "COPY" command or using cut and
paste from a Windows explorer Windows doesn't reproduce this problem,
that writes completely normally.
What Windows server are you using ? It looks like a reported allocation
issue to me - but I'm still trying to understand what triggers this
behaviour in the client ?
Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - XP performance problem
On Wed, Aug 10, 2005 at 11:05:06AM +0200, David Beck wrote: > >> > >>After spending a lot of time with investigation I decided to go > >>deeper in this issue. I installed ethereal to capture the traffic and > >>compare the results bw XP-Windows and XP-Tru64. The test was to copy > >>50Meg file to both servers and capture the packets. To my surprise > >>the conversation was quite different. > >> > >>XP-Windows (excerpt): > >>- nt create and x > >>- trans2: query file info internal > >>- set file info > >>- tcp data stream... > >> > >>XP-Samba (excerpt): > >>- nt create and x > >>- trans2: query file info internal > >>- (query file info + write and x request) many times, incresing > >>offset, one byte length > >>- tcp data stream > >> > >>In case of XP-Samba, the last two steps are repeated many times. > >>Large part of the effective bandwith is filled with query file info > >>and 1 byte writes. I can't reproduce this on my XP vmware session. *exactly* how are you getting this traffic pattern ? Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - XP performance problem
On Wed, Aug 10, 2005 at 11:05:06AM +0200, David Beck wrote:
> Thank you for the suggestion. I'll keep the info for reference.
>
> Followup for the performance issue:
>
> The trace shows that the conversation changes right after the "trans2:
> query file info internal" stage, so I looked into the samba code at this
> file:
>
> http://websvn.samba.org/cgi-bin/viewcvs.cgi/branches/SAMBA_3_0/source/smbd/trans2.c?rev=8959&view=markup
>
> case SMB_FILE_INTERNAL_INFORMATION:
> /* This should be an index number - looks like
> dev/ino to me :-)
>
> I think this causes us to fail the IFSKIT
> BasicFileInformationTest. -tpot */
>
> DEBUG(10,("call_trans2qfilepathinfo:
> SMB_FILE_INTERNAL_INFORMATION\n"));
> SIVAL(pdata,0,sbuf.st_dev);
> SIVAL(pdata,4,sbuf.st_ino);
> data_size = 8;
> break;
>
> The comment speaks for itself. I suspect the 8 byte here contains some
> magic that makes XP behaves as I found.
Hmmm. Good detective work. One thing I'd like to check though - can you try the
following (not production) patch and recompile and test please ? I'm
still at LinuxWorld and so won't be able to get to this until tomorrow
at the earliest.
If this fix makes things go faster I have a working theory...
Jeremy.
Index: smbd/dosmode.c
===
--- smbd/dosmode.c (revision 9229)
+++ smbd/dosmode.c (working copy)
@@ -22,11 +22,13 @@
static int set_sparse_flag(const SMB_STRUCT_STAT * const sbuf)
{
+#if 0 /* JRATEST */
#if defined (HAVE_STAT_ST_BLOCKS) && defined(STAT_ST_BLOCKSIZE)
if (sbuf->st_size > sbuf->st_blocks * (SMB_OFF_T)STAT_ST_BLOCKSIZE) {
return FILE_ATTRIBUTE_SPARSE;
}
#endif
+#endif
return 0;
}
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - XP performance problem
Thank you for the suggestion. I'll keep the info for reference.
Followup for the performance issue:
The trace shows that the conversation changes right after the "trans2:
query file info internal" stage, so I looked into the samba code at this
file:
http://websvn.samba.org/cgi-bin/viewcvs.cgi/branches/SAMBA_3_0/source/smbd/trans2.c?rev=8959&view=markup
case SMB_FILE_INTERNAL_INFORMATION:
/* This should be an index number - looks like
dev/ino to me :-)
I think this causes us to fail the IFSKIT
BasicFileInformationTest. -tpot */
DEBUG(10,("call_trans2qfilepathinfo:
SMB_FILE_INTERNAL_INFORMATION\n"));
SIVAL(pdata,0,sbuf.st_dev);
SIVAL(pdata,4,sbuf.st_ino);
data_size = 8;
break;
The comment speaks for itself. I suspect the 8 byte here contains some
magic that makes XP behaves as I found.
I made an other experiment: I turned off the oplock support ("Oplocks =
No") and this made XP behave like if it was talking to a Windows server.
No extra tran2 calls and 1 byte writes. The performance got better
because the slowdowns disappeared, but it was still slower compared to
the windows machine.
Then I looked into the traces again and found that XP sends 1260 bytes
in each packets when talking to the windows server and 536 bytes when
talking to the samba server. The MTU is 1300. I suspect, this issue may
be related to the different subnets where the two machines are located.
Hope this helps someone out there,
David.
Jonathan Johnson wrote:
I can't say that this will apply in your situation, but I've seen
where having stale "connections" to non-existent servers can cause a
performance issue when browsing. Here's a couple of things to try:
1) Remove any shortcuts to non-existent network locations -- this
applies to broken mapped drives, shortcuts on the desktop and in My
Documents, and shortcuts in My Network Places
2) Look in the registry at
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2
(or ...\MountPoints) -- Under this key, there will be several subkeys.
Some of these are in the form of ##Server##Share -- if there are any
of these that refer to nonexistent servers or shares, remove them. DO
NOT remove any of the other keys, else your system might not boot
properly. This key is seems to be the Windows version of the
/etc/fstab file.
Nevertheless, I'm glad to see that you found something interesting.
Hopefully, your research will help the developers solve some other
nagging problems!
--Jonathan Johnson
David Beck wrote:
Hello There,
After having googled the whole internet for days I decided to go
public with this issue.
The result of my google queries so far is that there are plenty of
others with the very same problem I have and noone posted a
reasonable answer to this:
Using Samba 3 with XP gets bad performance. I tested this on Tru64
5.1b and FreeBSD 5.3 with the very same symptoms.
The throughput bw XP and Samba goes up and down. It starts
transfering with a reasonable speed and after having transfered
around 16 megs it slows down.
I tried many configuration options regarding locking, tcp settings,
xmit size and every combination that could make any sense for me.
Then I gave up with this configuration mess as I could lower the
performnce easily, but the performance jittering was the same.
Now a few notes before I continue: I tested the FreeBSD server on the
loopback interface and the file write speed was around 43 Megs that
is close to the disks maximum. I also tested the XP machine with a
Windows server and the write performnce was around 10 Megs on a
100Mbit link. In addition to that the FreeBSD machine is at my home
and the Tru64 and the Windows server are where I work. I'm pretty
sure that this is not a network issue.
After spending a lot of time with investigation I decided to go
deeper in this issue. I installed ethereal to capture the traffic and
compare the results bw XP-Windows and XP-Tru64. The test was to copy
50Meg file to both servers and capture the packets. To my surprise
the conversation was quite different.
XP-Windows (excerpt):
- nt create and x
- trans2: query file info internal
- set file info
- tcp data stream...
XP-Samba (excerpt):
- nt create and x
- trans2: query file info internal
- (query file info + write and x request) many times, incresing
offset, one byte length
- tcp data stream
In case of XP-Samba, the last two steps are repeated many times.
Large part of the effective bandwith is filled with query file info
and 1 byte writes.
The packet data can be downloaded from these links:
http://dbeck.beckground.hu/download/xp-samba.bz2
http://dbeck.beckground.hu/download/xp-win.bz2
I also made a screenshot of a bandwith monitor to show what I mean by
performanc
Re: [Samba] Samba - XP performance problem
I can't say that this will apply in your situation, but I've seen where having stale "connections" to non-existent servers can cause a performance issue when browsing. Here's a couple of things to try: 1) Remove any shortcuts to non-existent network locations -- this applies to broken mapped drives, shortcuts on the desktop and in My Documents, and shortcuts in My Network Places 2) Look in the registry at HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 (or ...\MountPoints) -- Under this key, there will be several subkeys. Some of these are in the form of ##Server##Share -- if there are any of these that refer to nonexistent servers or shares, remove them. DO NOT remove any of the other keys, else your system might not boot properly. This key is seems to be the Windows version of the /etc/fstab file. Nevertheless, I'm glad to see that you found something interesting. Hopefully, your research will help the developers solve some other nagging problems! --Jonathan Johnson David Beck wrote: Hello There, After having googled the whole internet for days I decided to go public with this issue. The result of my google queries so far is that there are plenty of others with the very same problem I have and noone posted a reasonable answer to this: Using Samba 3 with XP gets bad performance. I tested this on Tru64 5.1b and FreeBSD 5.3 with the very same symptoms. The throughput bw XP and Samba goes up and down. It starts transfering with a reasonable speed and after having transfered around 16 megs it slows down. I tried many configuration options regarding locking, tcp settings, xmit size and every combination that could make any sense for me. Then I gave up with this configuration mess as I could lower the performnce easily, but the performance jittering was the same. Now a few notes before I continue: I tested the FreeBSD server on the loopback interface and the file write speed was around 43 Megs that is close to the disks maximum. I also tested the XP machine with a Windows server and the write performnce was around 10 Megs on a 100Mbit link. In addition to that the FreeBSD machine is at my home and the Tru64 and the Windows server are where I work. I'm pretty sure that this is not a network issue. After spending a lot of time with investigation I decided to go deeper in this issue. I installed ethereal to capture the traffic and compare the results bw XP-Windows and XP-Tru64. The test was to copy 50Meg file to both servers and capture the packets. To my surprise the conversation was quite different. XP-Windows (excerpt): - nt create and x - trans2: query file info internal - set file info - tcp data stream... XP-Samba (excerpt): - nt create and x - trans2: query file info internal - (query file info + write and x request) many times, incresing offset, one byte length - tcp data stream In case of XP-Samba, the last two steps are repeated many times. Large part of the effective bandwith is filled with query file info and 1 byte writes. The packet data can be downloaded from these links: http://dbeck.beckground.hu/download/xp-samba.bz2 http://dbeck.beckground.hu/download/xp-win.bz2 I also made a screenshot of a bandwith monitor to show what I mean by performance jittering: http://dbeck.beckground.hu/download/samba-performance-write.PNG http://dbeck.beckground.hu/download/samba-performance-read.PNG Please note that the original packet log for the 50 Meg file was very large, so I kept only the interesting parts. Last, could anyone there, Samba and SMB wizards help me, how to solve this performance issue? Thank you in advance, David. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - XP performance problem
On Mon, Aug 08, 2005 at 03:12:55PM +0200, David Beck wrote: > Hello There, > > After having googled the whole internet for days I decided to go public > with this issue. > The result of my google queries so far is that there are plenty of > others with the very same problem I have and noone posted a reasonable > answer to this: > > Using Samba 3 with XP gets bad performance. I tested this on Tru64 5.1b > and FreeBSD 5.3 with the very same symptoms. > The throughput bw XP and Samba goes up and down. It starts transfering > with a reasonable speed and after having transfered around 16 megs it > slows down. > I tried many configuration options regarding locking, tcp settings, xmit > size and every combination that could make any sense for me. > > Then I gave up with this configuration mess as I could lower the > performnce easily, but the performance jittering was the same. > > Now a few notes before I continue: I tested the FreeBSD server on the > loopback interface and the file write speed was around 43 Megs that is > close to the disks maximum. I also tested the XP machine with a Windows > server and the write performnce was around 10 Megs on a 100Mbit link. In > addition to that the FreeBSD machine is at my home and the Tru64 and the > Windows server are where I work. I'm pretty sure that this is not a > network issue. > > After spending a lot of time with investigation I decided to go deeper > in this issue. I installed ethereal to capture the traffic and compare > the results bw XP-Windows and XP-Tru64. The test was to copy 50Meg file > to both servers and capture the packets. To my surprise the conversation > was quite different. > > XP-Windows (excerpt): > - nt create and x > - trans2: query file info internal > - set file info > - tcp data stream... > > XP-Samba (excerpt): > - nt create and x > - trans2: query file info internal > - (query file info + write and x request) many times, incresing offset, > one byte length > - tcp data stream Can you send me the ethereal capture traces please ? I have a theory... Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba - XP performance problem
Hello There, After having googled the whole internet for days I decided to go public with this issue. The result of my google queries so far is that there are plenty of others with the very same problem I have and noone posted a reasonable answer to this: Using Samba 3 with XP gets bad performance. I tested this on Tru64 5.1b and FreeBSD 5.3 with the very same symptoms. The throughput bw XP and Samba goes up and down. It starts transfering with a reasonable speed and after having transfered around 16 megs it slows down. I tried many configuration options regarding locking, tcp settings, xmit size and every combination that could make any sense for me. Then I gave up with this configuration mess as I could lower the performnce easily, but the performance jittering was the same. Now a few notes before I continue: I tested the FreeBSD server on the loopback interface and the file write speed was around 43 Megs that is close to the disks maximum. I also tested the XP machine with a Windows server and the write performnce was around 10 Megs on a 100Mbit link. In addition to that the FreeBSD machine is at my home and the Tru64 and the Windows server are where I work. I'm pretty sure that this is not a network issue. After spending a lot of time with investigation I decided to go deeper in this issue. I installed ethereal to capture the traffic and compare the results bw XP-Windows and XP-Tru64. The test was to copy 50Meg file to both servers and capture the packets. To my surprise the conversation was quite different. XP-Windows (excerpt): - nt create and x - trans2: query file info internal - set file info - tcp data stream... XP-Samba (excerpt): - nt create and x - trans2: query file info internal - (query file info + write and x request) many times, incresing offset, one byte length - tcp data stream In case of XP-Samba, the last two steps are repeated many times. Large part of the effective bandwith is filled with query file info and 1 byte writes. The packet data can be downloaded from these links: http://dbeck.beckground.hu/download/xp-samba.bz2 http://dbeck.beckground.hu/download/xp-win.bz2 I also made a screenshot of a bandwith monitor to show what I mean by performance jittering: http://dbeck.beckground.hu/download/samba-performance-write.PNG http://dbeck.beckground.hu/download/samba-performance-read.PNG Please note that the original packet log for the 50 Meg file was very large, so I kept only the interesting parts. Last, could anyone there, Samba and SMB wizards help me, how to solve this performance issue? Thank you in advance, David. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + xp "Delayed Write Failed"
On Fri, Jul 08, 2005 at 03:21:57PM +0200, Kosa Attila wrote: > On Fri, Jul 08, 2005 at 03:11:45PM +0200, Kosa Attila wrote: > > > > I append the tcmpdump (egrep) issue and smb.conf-sambaversion. > > Sorry, stranded :) Sorry, I don't send :( http://members.chello.hu/kosa.attila/smb.conf-2.2.3a-15.gz http://members.chello.hu/kosa.attila/smb.conf-2.2.9-0.gz http://members.chello.hu/kosa.attila/tcpdump-2.2.3a-15.dmp.gz http://members.chello.hu/kosa.attila/tcpdump-2.2.9-0.dmp.gz -- Udvozlettel Zsiga Sorry, for my poor English! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + xp "Delayed Write Failed"
On Fri, Jul 08, 2005 at 03:11:45PM +0200, Kosa Attila wrote: > > Every test under running tcpdump: > tcpdump -ni eth1 -w tcpdump.dmp > tcpdump -ln -r tcpdump.dmp -s 0 -xX less 150 \ > | egrep "^SMB P" > tcpdump-sambaversion.dmp > > I append the tcmpdump (egrep) issue and smb.conf-sambaversion. Sorry, stranded :) -- Bye Zsiga Sorry, for my poor English! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + xp "Delayed Write Failed"
Hello! I testing samba and XP (file size ~14MB). Copy, 2.2.3a-15 samba->XP (Explorer) Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:4723 751 to 825: 66 76 to 150: 490 826 to 900: 1 151 to 225: 201 901 to 975: 0 226 to 300: 4 976 to 1050: 7 301 to 375: 0 1051 to 1125: 1 376 to 450: 3 1126 to 1200: 0 451 to 525: 3 1201 to 1275: 0 526 to 600: 0 1276 to 1350: 194 601 to 675: 0 1351 to 1425: 2 676 to 750: 3 1426 to 1500+: 10300 Copy, 2.2.9-0 samba->XP (Explorer) Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:4699 751 to 825: 103 76 to 150: 503 826 to 900: 1 151 to 225: 16 901 to 975: 0 226 to 300: 171 976 to 1050: 11 301 to 375: 0 1051 to 1125: 2 376 to 450: 4 1126 to 1200: 1 451 to 525: 3 1201 to 1275: 0 526 to 600: 0 1276 to 1350: 174 601 to 675: 0 1351 to 1425: 2 676 to 750: 4 1426 to 1500+: 10297 Copy, 3.0.14a samba->XP (Explorer) Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:4718 751 to 825: 21 76 to 150: 481 826 to 900: 0 151 to 225: 11 901 to 975: 0 226 to 300: 222 976 to 1050: 0 301 to 375: 1 1051 to 1125: 2 376 to 450: 1 1126 to 1200: 0 451 to 525: 1 1201 to 1275: 0 526 to 600: 0 1276 to 1350: 217 601 to 675: 0 1351 to 1425: 2 676 to 750: 2 1426 to 1500+: 10305 Copy, 3.0.20pre1-1 samba->XP (Explorer) Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:4683 751 to 825: 103 76 to 150: 494 826 to 900: 0 151 to 225: 12 901 to 975: 0 226 to 300: 178 976 to 1050: 7 301 to 375: 1 1051 to 1125: 1 376 to 450: 4 1126 to 1200: 1 451 to 525: 0 1201 to 1275: 0 526 to 600: 0 1276 to 1350: 179 601 to 675: 0 1351 to 1425: 1 676 to 750: 4 1426 to 1500+: 10298 I not see here significant difference. Program running, 2.2.3a-15 samba Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75: 12920 751 to 825: 469 76 to 150:1780 826 to 900: 2 151 to 225: 528 901 to 975: 0 226 to 300: 216 976 to 1050: 0 301 to 375: 1 1051 to 1125: 3 376 to 450: 6 1126 to 1200: 1 451 to 525: 1 1201 to 1275: 1 526 to 600: 1 1276 to 1350: 1 601 to 675: 1 1351 to 1425: 390 676 to 750: 3 1426 to 1500+: 28431 Program running, 2.2.9-0 samba Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:8041 751 to 825: 470 76 to 150: 186872 826 to 900: 2 151 to 225: 132 901 to 975: 3 226 to 300: 218 976 to 1050: 4 301 to 375: 1 1051 to 1125: 1 376 to 450: 6 1126 to 1200: 1 451 to 525: 1 1201 to 1275: 0 526 to 600: 1 1276 to 1350: 1 601 to 675: 1 1351 to 1425: 346 676 to 750: 3 1426 to 1500+: 28430 Program running, 3.0.14a samba Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75: 10179 751 to 825: 469 76 to 150: 225618 826 to 900: 2 151 to 225: 145 901 to 975: 0 226 to 300: 232 976 to 1050: 0 301 to 375: 12 1051 to 11
Re: [Samba] samba + xp "Delayed Write Failed"
On Thu, Jul 07, 2005 at 03:07:56AM -0700, Jeremy Allison wrote: > On Thu, Jul 07, 2005 at 11:53:39AM +0200, Kosa Attila wrote: > > >max xmit = 8192 > >block size = 4096 > > Why have you changed these ? What was the purpose of doing so ? > Just remove them from your smb.conf. My disks block size is 4096 byte. We tried all kinds of value to both options, in order to find the optimal values. man smb.conf (samba 3.0.14a version) /max xmit \(G\) The default is 65535, which is the maximum. In some cases you may find you get better performance with a smaller value. Therefore we tried to lower the default value. But we tried the default value, too. Unfortunately it hasn't changed for the better :( I make a little drawing to make the network topology clear (it may help). | WIN | | NT 4 | |1000 | |-firewall--Internet -- 100 1000 | --- | | samba |--|switch|| XP | |VNC | PDC| | VNC | | | LDAP || | | | | replica||1000 | | | --| --- | |1000MB| my | eth1 | cable| Linux| |samba |---| | box | |3.0.20| samba PDC eth0 192.168.3.35 (192.168.3.0/24) samba 3.0.20 eth0 192.168.3.190 (192.168.3.0/24) samba 3.0.20 eth1 192.168.20.1 (192.168.20.0/24) XP nic1 192.168.3.191 (192.168.3.0/24) XP nic2 192.168.20.2 (192.168.20.0/24) WIN NT 4192.168.3.21 (192.168.3.0/24) -- Bye Zsiga Sorry, for my poor English! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + xp "Delayed Write Failed"
On Thu, Jul 07, 2005 at 11:53:39AM +0200, Kosa Attila wrote: >max xmit = 8192 >block size = 4096 Why have you changed these ? What was the purpose of doing so ? Just remove them from your smb.conf. Jeremy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba + xp "Delayed Write Failed"
Hello! Hardver: Windows XP Compaq Proliant DL360, Linux Compaq Proliant DL380. 2 pieces of processors Intel Xeon 3,2GHz, 2GB RAM, 6 gigabit interface (2 tg3, 4 e1000), Debian Woody, 2.4.31 vanilla kernel. 6 U320 SCSI 15krpm HDD, 2 HDD RAID1 system, 4 HDD RAID1+0 data. Every network cards connect at speed of 1000MB full duplex, with XP crosscable (but we've tried with gigabit switch, too, we have tried both types of cards). In the XP's (there are more of them) there are 2 pieces of interface at gigabit speed, one of them is connected to the network of PDC, the other is connected to the cards of the above mentioned computer with crosscable. There is also a Windows NT 4.0 SP6 server with gigabit card, too. Surroundings: Windows domain, samba PDC (2.2.8a) that gets users from LDAP. The Linux computer belongs to the domain, the LDAP-server is set to it in libnss-ldap.conf file (the "getent passwd" sees the users and groups), and the samba is able to authentify the users with the help of the options "security = server, password server = IP.address", there's no problem with this. DL380 the samba's version is: 2.2.3a-15. Its speed is convencing, the program mentioned below communicates with the server at a speed of 140-15kbit/s (measuring with iptraf, Incoming ~9, Outgoing ~5), by the netwatch of Windows the utilization of the network sometimes reaches the 19%. When I make run the program below onto files on an XP, then by the network of Windows the utilization of the net is never higher than 15%. The utilization of the processor on the XP is above 50% while the program is running. There's a program that - when running on the XP - reads from mapped network drive and writes back there. It reads certain data and generates different files from the data. These files are relatively big size (both the read and written ones), now the biggest is the size of 400MB. However undefinable times we get the next error message in Windows: "Delayed Write Failed". This time a note gets also into the diary of the events, its the status code is: c20c (see later why it's important). Searching in the Microsoft's Knowledge Base we've found these messages that are like the error message above: http://support.microsoft.com/default.aspx?scid=kb;en;321733 - here the error message is the same but the status code is not. It seems that the SP2 solves this problem on XP, we've looked through the mentioned things and everything is OK, they are set up so that they should work. http://support.microsoft.com/default.aspx?scid=kb;en-us;Q293842 - the error message is similar, the status code is the same, too but by Microsoft this error doesn't happen on XP. http://www.tangent-systems.com/support/delayedwrite.html - this is a good summary of the problem above. It analyses what kind of settings are needed for servers and clients in order to avoid this error (that is depending on the combination of the server and the client to switch on or to switch off the SMB signing). On the basis of the last link we have checked the settings of the Windows NT server (on that making the program run the error message doesn't happen) and they suit the requirements written in the article. The 2.2.3a-15 samba Windows NT behaves as a server on the network, that is SMB signing should be switched off in it, too... however this version doesn't know such an option! (I can't understand, if it doesn't know the option of SMB signing how it can use? Otherwise, if this samba can't use it, it can't be switched off because it is not switched on...) Anyway, we've also tried 2.2.8, 2.2.9 versions, but there was no result beside the drastic slowing down, the error message arises again on XP. (Drastic slowing down means: the speed doesn't exceed 2kbit/s in contradiction to the previous 15kbit/s, Incoming ~10700, Outgoing ~8500). We have ported 3.0.14a and 3.0.20pre1-1 versions aswell, they have SMB signing option (client signing = diabled, server signing = disabled), and it solves the question of error. Using these versions the error message doesn't arise on XP. But the speed is awful! We aren't able to reach 3kbit/s :( If debug level = 3, even 2kbit/scan't be exceeded! On XP the utilization of the processor doesn't go over 27%! By the Windows netwatch the utilization of the network never exceeds 2%! The utmost packet size (with iptraf) 76-150 byte. It's interesting that in case of simple copy (that is I copy from samba to XP starting copy from XP with Explorer) by the Windows netwatch speed is fixed 11%, by iptraf it is roughly fixed 117000kbit/s (with version 2.2.3a-15). And neither copies always run without errors! Sometimes an error message arrives: "Network name can't be reached" (or something like that - it can't be totally reproducted the copy is sometimes successful, sometimes not). Here is the 2.2.3a-15 samba version's smb.conf file (as it can be seen, we haven't tuned too much on it, it's almost the default config)
[Samba] Samba XP 2005 is next week (May 2 - 4)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 FYI This is a last minute reminder that the Samba XP conference will be next week, May 2 - 4, at the Hotel Freizeit in GÃttingen - Germany. More information about the conference itself can be found at http://www.sambaxp.org/. The technical sessions are listed at http://www.sambaxp.org/index.php?id=25. IMO (and I'm not on the program committee so I can honestly say this), the technical sessions look to be very strong this year. There's a full-day Winbind tutorial people might find to be interesting. In the interest of full disclosure, I am teaching it. But there seems to be enough trouble surrounding Winbind administration that hopefully people will find it helpful. Most of the active developers, both on Samba 3 and 4, will be there. So if there is a Samba topic you would like to chat about, this is one of the better chances to do so. The next conference that majority of Samba developers attend is the CIFS conference in San Jose, CA, Aug 1 - 5. More information can be found at http://www.cifs2005.org/. cheers, jerry = Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCbmuoIR7qMdg1EfYRAoDqAJ9GXUEJXvn1UihmFUSizTA7p3XU5wCgx9Op XiaHt1+lNRLWo6wpGbQwL9A= =LdeV -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba XP multip user login problem
Hi, I have a problem reg. the interconnection of Samba and XP und the "Fast User switching" facility of XP. Problem occurs like this: If there are more than one user logged into a XP machine (i.e via remotedesktop/fast user switching) only the last logged in user is able to access the samba shares. The other ones are getting a window which prompts for username and password, but they will never succeed. One of the share is the home of the user and is shown as loginname in the network neighborhood (i.e. \\samba\USER). If there are more than one logged into the XP machine I can see a \\samba\USER and a \\samba\nobody. So it seems that the Samba isn't able to handle more the one user per XP machine. Our setup is a little bit trocky but not too much. We are using Samba 2.2.8a and a XP machine as password server. Does anybody knows about restrictions/problems regarding this setup or multiple user logged into an XP machine? Under native XP file sharing it is possible to change the user and to connect to the same XP-share from different accounts on the same machine. Thanks in advance. Sven Hahlbrock -- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba -> XP. Slow log in/out
I have a server running slackware 9.1 and samba samba-2.2.8a and have WinXP Home (SP1) on a client machine. I have all of my users "My documents" pointing at a subdirectory of their home directories (ie. /home/USER/.documents). All of the users are able to use this with no problems EXCEPT me. When I log in to my user profile in Windows, the system tray takes about 5 minutes to load up. If I try to log out it hangs for about 5 minutes during this time. I am able to prevent this behaviour by pointing "My Documents" to a folder on the local (C:) hard drive and not using my samba share. Also - when I right-click on "My Documents" (in XP), go to "Properties" and change "Target" to \\SERVER\robert, it hangs for ages when I press Apply or OK. I recently reinstalled my entire XP hard drive and this problem still ocurs. Presumably its not an XP setup problem. Upgrading samba to 3.0.0 makes no difference. My user name is robert, the client computer is called CLIENT and the server is called SERVER (the names are fictitious). Sorry about putting a Windows question on a Unix newsgroup, but the aim of samba is to allow these systems to speak to each other! My /var/log/samba/CLIENT.log looks like this (as you can see there are some strange entries that are specific to my user name (they don't apply to other users): [2003/12/28 11:03:31, 0] smbd/service.c:make_connection(252) CLIENT (192.168.2.20) couldn't find service robert.dll [2003/12/28 11:10:57, 0] printing/print_cups.c:cups_printername_ok(388) Unable to get printer status for rober - client-error-not-found [2003/12/28 11:10:57, 0] smbd/service.c:make_connection(252) CLIENT (192.168.2.20) couldn't find service rober [2003/12/28 11:10:57, 0] printing/print_cups.c:cups_printername_ok(388) Unable to get printer status for robert.dll - client-error-not-found [2003/12/28 11:10:57, 0] smbd/service.c:make_connection(252) CLIENT (192.168.2.20) couldn't find service robert.dll Here are the relevant parts of my smb.conf: [global] workgroup = HOME netbios name = SERVER server string = Samba Server encrypt passwords = Yes log file = /var/log/samba/%m.log log level = 0 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 lock dir = /var/lock/samba printing = cups printcap name = cups invalid users = root browseable = No [homes] comment = Home Directories path = /home/%S/.documents read only = No create mask = 0700 directory mask = 0700 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba / XP drive listing problems
Welp, I have asked this question numerous times with no responses, so I'll try to rephrase it. I have a very upset client and need an answer soon. How do I configure samba or XP to display the drive listings correctly (shorter) in Windows Explorer? Other versions of Winbloze seem to display the lists of mapped drives just fine. XP displays this: Local Disk (C:) sys on 'Samba Server 2.2.7-security-rollup-fix on Server (Server) f:' Obviously the listing for the F: drive is way too long. How do I get it to display shorter? I have already set the netbios name and server string parameters in the smb.conf file and restarted the service. What else can I do short of recompiling the entire package myself? - Gary -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba XP
Hi, But I need the following details to set up the server:- 1. Samba version When you're a newbe start with the latest stable version, 2.2.8a, you should have searched for that on samba.org, you need nothing else from samba.org 2. Linux kernel version (preferably what distribution and what version) Hmm I am not going to start here. Distro doesn't make a lot of a difference, I prefer Debian, but I could live with any distro. 4. Any more sites that tells me how to setup the XP Pro Clients with the samba server? I used four howto's: This one is the best for XP hassles: http://www.math.temple.edu/computing/samba.html#optimize Search on: samba.idealx.org for their samba-ldap-pdc howto if you're planning on using ldap (if you're planning a domain woth lots of users it might be a good idea) and use this one: http://www.unav.es/cti/ldap-smb/ldap-smb-howto.html And the last thing I used for simple questions was the howto collection and faq's that come with the samba package. Hope to be of help. Regards Bas PS: Most answers are pretty easy to find with google, the documentation on samba.org or the mailinglist archives -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba XP
Hi, (Please reply to this address rather than the one posted previously) I am a newbie when it comes to XP and samba. I am planning to install samba domain controller for XP, 2000 machines. I read a bit about the registry hacking and some documents on the internet. But I need the following details to set up the server:- 1. Samba version 2. Linux kernel version (preferably what distribution and what version) THe lesser the bugs the better. 3. What patch level should I have for the samba 4. Any more sites that tells me how to setup the XP Pro Clients with the samba server? Thanks. adrian -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba XP
> But I need the following details to set up the server:- > 1. Samba version > 2. Linux kernel version (preferably what distribution and > what version) THe lesser the bugs the better. 3. What patch > level should I have for the samba 4. Any more sites that > tells me how to setup the XP Pro Clients with the samba server? RH 8; Samba 2.2.8 from samba org rebuilt as rpm. after reading this http://hr.uoregon.edu/davidrl/samba/samba-pdc.html and this http://us1.samba.org/samba/ftp/docs/htmldocs/Samba-PDC-HOWTO.html and eventually this http://www.math.temple.edu/computing/samba.html I was able to do a samba PDC and join the XP Pro clients to it. Beware it's a long and painfully frustrating journey. ;-) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba XP
Hi, I am a newbie when it comes to XP and samba. I am planning to install samba domain controller for XP, 2000 machines. I read a bit about the registry hacking and some documents on the internet. But I need the following details to set up the server:- 1. Samba version 2. Linux kernel version (preferably what distribution and what version) THe lesser the bugs the better. 3. What patch level should I have for the samba 4. Any more sites that tells me how to setup the XP Pro Clients with the samba server? Thanks. adrian -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba XP
Hi, I am a newbie when it comes to XP and samba. I am planning to install samba domain controller for XP, 2000 machines. I read a bit about the registry hacking and some documents on the internet. But I need the following details to set up the server:- 1. Samba version 2. Linux kernel version (preferably what distribution and what version) THe lesser the bugs the better. 3. What patch level should I have for the samba 4. Any more sites that tells me how to setup the XP Pro Clients with the samba server? Thanks. adrian -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba/XP accessing remotely.
This is what I have been told: There are 5 developers, four running windows 2000 and one running windows XP. When at the office, they can all access the Samba share (running on UNIX) without a problem. The Windows 2000 users say that they can access the Samba Share from home while the XP user says he cannot. Any ideas? ---> Jonathan -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba & XP Professional
I configure the XP for a domain validation "TYC.ES", ask me for USER/PASS root/, the name of the machine that runs SAMBA have the machine account antoniou$, group XPstation, and this user "antoniou$" and root in the samba passwd database, my smb.conf it's something like this: # Global parameters [global] workgroup = tyc.es server string = HAL9000 netbios name = HAL9000 interfaces = eth0 bind interfaces only = yes map to guest = Bad User username map = /etc/users.map password level = 5 keepalive = 30 character set = ISO8859-1 logon path = /usr/lib/samba/netlogon logon script = %U.bat csc policy = disable profile acls = yes # When i run the command "testparm /etc/samba/smb.conf", it tells me that this directive is unknown for samba ¿? domain logons = yes domain master = yes local master = yes preferred master = yes os level = 65 preferred master = True domain master = True kernel oplocks = No create mask = 0660 directory mask = 0770 hosts allow = 192.168.254. EXCEPT 192.168.254.8 wins support = yes encrypt passwords = yes log level = 3 log file = /var/log/samba.log [tmp] path = /tmp browseable = yes writeable = yes [homes] comment = Homes de Usuarios read only = No create mask = 0750 browseable = No [netlogon] path = /usr/lib/samba/netlogon The file i want to run when the XP boots contain various route commands and net time. It has permissions 755 root:root. I try with NAMEOFMACHINE.bat "antoniou.bat" " root.bat Thanks. Kurt Weiss escribió: Antonio Moya Krijer schrieb: Hi, I have a linux SuSE 8.1 with samba 2.2.5 Release 80. I have a Windows XP Professional that is member of a Samba domain, authentication it's OK but i have a profile in /usr/lib/samba/netlogon u mean: a script? (or a roaming profile???) that i want to execute when the XP boots, i don't know what's happening. I have read the "How to" documentation Can you help me, please? Thanks a lot. . -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba & XP Professional
Hi, I have a linux SuSE 8.1 with samba 2.2.5 Release 80. I have a Windows XP Professional that is member of a Samba domain, authentication it's OK but i have a profile in /usr/lib/samba/netlogon that i want to execute when the XP boots, i don't know what's happening. I have read the "How to" documentation Can you help me, please? Thanks a lot. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba xp domain login trouble
here is a snippet from xp after i try to login to the samba domain... any help would be appreciated... dns is working on linux box followed directions for samba PDC setup. The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain RINUXUNIX.COM: The error was: "DNS name does not exist." (error code 0x232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.MINUXUNIX.COM Common causes of this error include the following: - The DNS SRV record is not registered in DNS. - One or more of the following zones do not include delegation to its child zone: MINUXUNIX.COM COM . (the root zone) For information about correcting this problem, click Help. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba xp oddity
Hi, I posted this on the clug list but got no reply. I just recently upgraded to samba 2.2.5 on my SuSE 8.0 box. I compiled samba myself because I needed the ldap stuff. Now someone who uses XP has found that when he copies a file from my samba volume to a webdav volume it always deletes the original file in the samba volume. This is weird and only seems to occur in this exact circumstance - copying in any other way between other mounted filesystems does what you expect. Normally when copying between volumes in XP you get a special cursor that tells you a copy will take place, in this case with a normal drag copy the plus does not appear when the mouse is hovering over the webdav folder. Even attempting to force the copy with the control key or right-drag or copy-paste does not stop the original being deleted. Anyone have any ideas? Is this a known bug? Is there a *simple* samba config option to fix it? Kim -- -- Kim Holburn Network Consultant - Telecommunications Engineering Research School of Information Sciences and Engineering Australian National University - Ph: +61 2 61258620 M: +61 0417820641 Email: [EMAIL PROTECTED] - PGP Public Key on request Life is complex - It has real and imaginary parts. Andrea Leistra (rec.arts.sf.written.Robert-jordan) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba/XP problem solved for my purposes
Hi all System: SuSE 8.1 Samba : 2.2.5 (default in 8.1 box) I can't believe it but the problem was setteled on a complete other "mystery". In SuSE 8.1 the DEFAULT Netware Server settings are set to hostname MARS - what I didn't know before reading it accidentially in the SuSE administrator handbook - and I named, believe it or not, my server also ***mars*** what is taken, without changings, as name for the default netbios settings in smb.conf. That was all the conflict! I assume it's only a SuSE 8.1 specific problem. So I kept the hostname of my server and changed ***only*** the netbios name in the smb.conf: That's it. Now Samba works fine, I even could reset all XP registry settings to M$ defaults! Anyway: Thanks to all who helped! Cheers, Roland > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:samba-admin@;lists.samba.org] Im > Auftrag von Roland Rick > Gesendet: Montag, 21. Oktober 2002 11:17 > An: [EMAIL PROTECTED] > Betreff: [Samba] Samba 2.2.5/XP-Pro with Domain Account > > Hi everybody out there! > > I'm using Samba 2.2.5, coming with SuSE 8.1 and should connect from an > XP-Pro PC, really logged into an W2K PDC with Domain Account, to the > Samba server mentioned above. > > Problem: > Logged from XP-Pro client into W2K PDC account, I can not connect and > always get a "System error 1240" (net use \\SMBSERVER\share) > which I also can not avoid doing all the Microsoft Knowledgebase stuff. > > The problem occurs only when I'm logged into the W2K-PDC domain account. > If I log into a local account on the XP PC I have no problems. > > Please assume, that all accounts are set correct, either on XP client > PC, W2K PDC or on Linux/Samba site. > > Please find attached a level 3 log.smbd what happens while trying to > connect from domain account (does not work) and when connecnting from > local account (***works***). > > On W2K clients - logged into W2K domain account - I don't have any > problems to connect e.g. to Samba 2.2.2 on Solaris 8 hosts. > > I really would appreciate any help! > > Cheers, > Roland > > Trying to connect from domain account, what does not work: > == > [2002/10/21 10:49:54, 3] smbd/oplock.c:init_oplocks(1211) > open_oplock_ipc: opening loopback UDP socket. > [2002/10/21 10:49:54, 3] lib/util_sock.c:open_socket_in(813) > bind succeeded on port 0 > [2002/10/21 10:49:54, 3] > smbd/oplock_linux.c:linux_init_kernel_oplocks(298) > Linux kernel oplocks enabled > [2002/10/21 10:49:54, 3] smbd/oplock.c:init_oplocks(1242) > open_oplock ipc: pid = 15652, global_oplock_port = 32844 > [2002/10/21 10:49:54, 3] smbd/process.c:process_smb(878) > Transaction 0 of length 72 > [2002/10/21 10:49:54, 2] smbd/reply.c:reply_special(92) > netbios connect: name1=MARS name2=VENUS > [2002/10/21 10:49:54, 2] smbd/reply.c:reply_special(111) > netbios connect: local=mars remote=venus > [2002/10/21 10:49:54, 3] smbd/process.c:process_smb(878) > Transaction 1 of length 137 > [2002/10/21 10:49:54, 3] smbd/process.c:switch_message(685) > switch message SMBnegprot (pid 15652) > [2002/10/21 10:49:54, 3] smbd/sec_ctx.c:set_sec_ctx(329) > setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 > [2002/10/21 10:49:54, 3] smbd/negprot.c:reply_negprot(342) > Requested protocol [PC NETWORK PROGRAM 1.0] > [2002/10/21 10:49:54, 3] smbd/negprot.c:reply_negprot(342) > Requested protocol [LANMAN1.0] > [2002/10/21 10:49:54, 3] smbd/negprot.c:reply_negprot(342) > Requested protocol [Windows for Workgroups 3.1a] > [2002/10/21 10:49:54, 3] smbd/negprot.c:reply_negprot(342) > Requested protocol [LM1.2X002] > [2002/10/21 10:49:54, 3] smbd/negprot.c:reply_negprot(342) > Requested protocol [LANMAN2.1] > [2002/10/21 10:49:54, 3] smbd/negprot.c:reply_negprot(342) > Requested protocol [NT LM 0.12] > [2002/10/21 10:49:54, 3] smbd/negprot.c:reply_negprot(426) > Selected protocol NT LM 0.12 > [2002/10/21 10:49:55, 3] smbd/process.c:timeout_processing(1098) > end of file from client > [2002/10/21 10:49:55, 3] smbd/sec_ctx.c:set_sec_ctx(329) > setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 > [2002/10/21 10:49:55, 2] smbd/server.c:exit_server(461) > Closing connections > [2002/10/21 10:49:55, 3] smbd/connection.c:yield_connection(48) > Yielding connection to > [2002/10/21 10:49:55, 3] smbd/server.c:exit_server(495) > Server exit (normal exit) > === End of log "does not work" == > > > > Trying to connect from local account, what ***works***: > === > [2002/10/21 10:56:10, 3] smbd/process.c:process_smb(878) > Transaction 46 of length 39 > [2002/10/21 10:56:10, 3] smbd/process.c:switch_message(685) > switch message SMBtdis (pid 15653) > [2002/10/21 10:56:10, 3] smbd/sec_ctx.c:set_sec_ctx(329) > setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 > [2002/10/21 10:56:10, 3] smbd/sec_ctx.c:set_sec_ctx(329) > setting sec ctx (0, 0) - sec_ctx_stack_ndx =
Re: [Samba] Samba + XP = no go
Yeah, tried all this, XP was a no go. Went to Samba TNG, and its working beautifully now. Ta - Ryan On 4/6/02 2:32 AM, "David W. Chapman Jr." <[EMAIL PROTECTED]> spoke these words: > On Mon, Jun 03, 2002 at 02:30:51PM +1000, xfesty wrote: >> G'day. >> >> I'm having a great time trying to get a whole heap of XP workstations (from >> what I understand, they've been hotfixed+windows updated+whatever else a few >> days ago) to authenticate against Samba running on a FreeBSD 4.5-STABLE box. >> >> Basically, I add user accounts, machine accounts (with both "pw" and >> "smbpasswd"), then I can get the XP machines to successfully join a domain. >> On reboot, they refuse to login. >> >> I've tried editing the registry and changing the "requiresignorseal" key >> from 1 to 0. Doesn't help. > > Have you tried setting it in all the control sets, I think the patch > needs to apply against current controlset but patches against control > set 0 or 1 > > > Just curious, are you using the FreeBSD port? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + XP = no go
On Mon, Jun 03, 2002 at 02:30:51PM +1000, xfesty wrote: > G'day. > > I'm having a great time trying to get a whole heap of XP workstations (from > what I understand, they've been hotfixed+windows updated+whatever else a few > days ago) to authenticate against Samba running on a FreeBSD 4.5-STABLE box. > > Basically, I add user accounts, machine accounts (with both "pw" and > "smbpasswd"), then I can get the XP machines to successfully join a domain. > On reboot, they refuse to login. > > I've tried editing the registry and changing the "requiresignorseal" key > from 1 to 0. Doesn't help. Have you tried setting it in all the control sets, I think the patch needs to apply against current controlset but patches against control set 0 or 1 Just curious, are you using the FreeBSD port? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba + XP = no go
G'day. I'm having a great time trying to get a whole heap of XP workstations (from what I understand, they've been hotfixed+windows updated+whatever else a few days ago) to authenticate against Samba running on a FreeBSD 4.5-STABLE box. Basically, I add user accounts, machine accounts (with both "pw" and "smbpasswd"), then I can get the XP machines to successfully join a domain. On reboot, they refuse to login. I've tried editing the registry and changing the "requiresignorseal" key from 1 to 0. Doesn't help. I was running whatever samba was in freebsd's ports a few days ago (2.2.4 I believe) but I've compiled the latest SAMBA_2_2 branch from CVS last night (2.2.5-pre), but im getting exactly the same problem as before. My SMB.CONF is below. Thanks. - Ryan [global] netbios name = BBSERVER workgroup = BBNETWORK os level = 64 preferred master = yes domain master = yes local master = yes security = user encrypt passwords = yes domain logons = yes server string = Management hosts allow = 10.0.0. 127. dns proxy = no time server = yes hide dot files = yes announce version = 5.2 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 wins support = yes domain admin group = @wheel [netlogon] path = /samba/netlogon read only = yes write list = root -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
