XP and Samba 2.2.1a on RH 7.2 not working...

XP and Samba 2.2.1a on RH 7.2 not working...

Post by Jan Svarre » Mon, 08 Jul 2002 06:38:46



Hi there all you freindly Samba-wizards! :-)

I have the problem that I can't access my Samba services from WinXP! However
though I CAN se the Samba server next to the other SM workgroup pc's - but
clicking the Samba Server only gives me a dialog-box saying something like
(it's in danish - so I translated it) : "No service operating at
networkendpoint on the remote system"

All tests made with smbclient etc.. are working on the Linux.

However I cannot make an:

c:\nbtstat -A 192.168.1.10       (thats on the client towards the server)

See my smb.conf below:

Best regards
Jan

#======================= Global Settings =============================#
[global]

# workgroup = NT-Domain-Name or Workgroup-Name
   workgroup = SM

   server string = Samba Server

   hosts allow = 192.168.1. 127.

   security = user

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /tmp/samba/%m.log
   log level = 2

[tmp]
   comment = Temporary file space
   path = /tmp
   read only = no
   public = yes

[jansdir]
   comment = Jan's service
   path = /home/jan
   valid users = jan
   public = no
   writable = yes
   printable = no

 
 
 

XP and Samba 2.2.1a on RH 7.2 not working...

Post by Shaun Marol » Mon, 08 Jul 2002 07:15:36


Update to Samba 2.2.5 as it has the protocols for Windows XP.

--Shaun


Quote:> Hi there all you freindly Samba-wizards! :-)

> I have the problem that I can't access my Samba services from WinXP!
However
> though I CAN se the Samba server next to the other SM workgroup pc's - but
> clicking the Samba Server only gives me a dialog-box saying something like
> (it's in danish - so I translated it) : "No service operating at
> networkendpoint on the remote system"

> All tests made with smbclient etc.. are working on the Linux.

> However I cannot make an:

> c:\nbtstat -A 192.168.1.10       (thats on the client towards the server)

> See my smb.conf below:

> Best regards
> Jan

> #======================= Global Settings =============================#
> [global]

> # workgroup = NT-Domain-Name or Workgroup-Name
>    workgroup = SM

>    server string = Samba Server

>    hosts allow = 192.168.1. 127.

>    security = user

> # this tells Samba to use a separate log file for each machine
> # that connects
>    log file = /tmp/samba/%m.log
>    log level = 2

> [tmp]
>    comment = Temporary file space
>    path = /tmp
>    read only = no
>    public = yes

> [jansdir]
>    comment = Jan's service
>    path = /home/jan
>    valid users = jan
>    public = no
>    writable = yes
>    printable = no


 
 
 

XP and Samba 2.2.1a on RH 7.2 not working...

Post by Jan Svarre » Mon, 08 Jul 2002 15:05:07


Hi Shaun! Thanks for the hint!

I just updated to 2.2.5 as you suggested - but still no luck (guess luck
does not have anything to do with it). I have the feeling that it is the XP
client which is causing me prob's. Any idea to where to find in-depth
description on how to setup Windows clients

Nearly bald Jan


> Update to Samba 2.2.5 as it has the protocols for Windows XP.

> --Shaun



> > Hi there all you freindly Samba-wizards! :-)

> > I have the problem that I can't access my Samba services from WinXP!
> However
> > though I CAN se the Samba server next to the other SM workgroup pc's -
but
> > clicking the Samba Server only gives me a dialog-box saying something
like
> > (it's in danish - so I translated it) : "No service operating at
> > networkendpoint on the remote system"

> > All tests made with smbclient etc.. are working on the Linux.

> > However I cannot make an:

> > c:\nbtstat -A 192.168.1.10       (thats on the client towards the
server)

> > See my smb.conf below:

> > Best regards
> > Jan

> > #======================= Global Settings =============================#
> > [global]

> > # workgroup = NT-Domain-Name or Workgroup-Name
> >    workgroup = SM

> >    server string = Samba Server

> >    hosts allow = 192.168.1. 127.

> >    security = user

> > # this tells Samba to use a separate log file for each machine
> > # that connects
> >    log file = /tmp/samba/%m.log
> >    log level = 2

> > [tmp]
> >    comment = Temporary file space
> >    path = /tmp
> >    read only = no
> >    public = yes

> > [jansdir]
> >    comment = Jan's service
> >    path = /home/jan
> >    valid users = jan
> >    public = no
> >    writable = yes
> >    printable = no

 
 
 

XP and Samba 2.2.1a on RH 7.2 not working...

Post by Dr Matthew William » Mon, 08 Jul 2002 22:41:31


Hi,

I had  trouble with XP and Samba, and a couple of people on this list pointed
out that a regedit/config change was required, more in a bit! However, I found
the following extremely useful when setting up a Windows 2000 client:

http://samba.mirror.ac.uk/samba/docs/man/Samba-HOWTO-Collection.html#...

Back to XP! This may not be the answer to your problem but it worked for
me.....

1. Run gpedit.msc
2. Find Local Computer Policy
3. Open Computer Configuration
4. Open Windows Settings
5. Open Security Settings
6. Open Local Policies
7. Click Security Option
8. Find Domain Member : Digitally Encrypt or sign secure channel data (always)
9. Click then right click, then select properties
10. Set it to disabled and click OK
11. Close program.

I can't remember but I am sure it asks for a reboot, but I would do that
anyway!

Hope this helps!

Matthew.


> Hi Shaun! Thanks for the hint!

> I just updated to 2.2.5 as you suggested - but still no luck (guess luck
> does not have anything to do with it). I have the feeling that it is the XP
> client which is causing me prob's. Any idea to where to find in-depth
> description on how to setup Windows clients

> Nearly bald Jan



> > Update to Samba 2.2.5 as it has the protocols for Windows XP.

> > --Shaun



> > > Hi there all you freindly Samba-wizards! :-)

> > > I have the problem that I can't access my Samba services from WinXP!
> > However
> > > though I CAN se the Samba server next to the other SM workgroup pc's -
> but
> > > clicking the Samba Server only gives me a dialog-box saying something
> like
> > > (it's in danish - so I translated it) : "No service operating at
> > > networkendpoint on the remote system"

> > > All tests made with smbclient etc.. are working on the Linux.

> > > However I cannot make an:

> > > c:\nbtstat -A 192.168.1.10       (thats on the client towards the
> server)

> > > See my smb.conf below:

> > > Best regards
> > > Jan

> > > #======================= Global Settings =============================#
> > > [global]

> > > # workgroup = NT-Domain-Name or Workgroup-Name
> > >    workgroup = SM

> > >    server string = Samba Server

> > >    hosts allow = 192.168.1. 127.

> > >    security = user

> > > # this tells Samba to use a separate log file for each machine
> > > # that connects
> > >    log file = /tmp/samba/%m.log
> > >    log level = 2

> > > [tmp]
> > >    comment = Temporary file space
> > >    path = /tmp
> > >    read only = no
> > >    public = yes

> > > [jansdir]
> > >    comment = Jan's service
> > >    path = /home/jan
> > >    valid users = jan
> > >    public = no
> > >    writable = yes
> > >    printable = no

--

Dr Matthew Williams
You're despicable - Daffy Duck

 
 
 

XP and Samba 2.2.1a on RH 7.2 not working...

Post by Shaun Marol » Tue, 09 Jul 2002 01:00:40


Well the first step was to get you on a version of Samba that will work
correctly with XP having done that there are a few things. First is to do a
registry fix look for the 'requiresignorseal' entry and set its value to 0
instead of 1. Even if you aren't running Samba as a PDC this helps a lot.
Now you need to setup XP system as if its a NT/2000 machine.
http://samba.netfirms.com has all the info you need there to do this. Follow
the simple instructions there and it should work fine.

--Shaun


> Hi Shaun! Thanks for the hint!

> I just updated to 2.2.5 as you suggested - but still no luck (guess luck
> does not have anything to do with it). I have the feeling that it is the
XP
> client which is causing me prob's. Any idea to where to find in-depth
> description on how to setup Windows clients

> Nearly bald Jan



> > Update to Samba 2.2.5 as it has the protocols for Windows XP.

> > --Shaun



> > > Hi there all you freindly Samba-wizards! :-)

> > > I have the problem that I can't access my Samba services from WinXP!
> > However
> > > though I CAN se the Samba server next to the other SM workgroup pc's -
> but
> > > clicking the Samba Server only gives me a dialog-box saying something
> like
> > > (it's in danish - so I translated it) : "No service operating at
> > > networkendpoint on the remote system"

> > > All tests made with smbclient etc.. are working on the Linux.

> > > However I cannot make an:

> > > c:\nbtstat -A 192.168.1.10       (thats on the client towards the
> server)

> > > See my smb.conf below:

> > > Best regards
> > > Jan

> > > #======================= Global Settings

=============================#

- Show quoted text -

Quote:> > > [global]

> > > # workgroup = NT-Domain-Name or Workgroup-Name
> > >    workgroup = SM

> > >    server string = Samba Server

> > >    hosts allow = 192.168.1. 127.

> > >    security = user

> > > # this tells Samba to use a separate log file for each machine
> > > # that connects
> > >    log file = /tmp/samba/%m.log
> > >    log level = 2

> > > [tmp]
> > >    comment = Temporary file space
> > >    path = /tmp
> > >    read only = no
> > >    public = yes

> > > [jansdir]
> > >    comment = Jan's service
> > >    path = /home/jan
> > >    valid users = jan
> > >    public = no
> > >    writable = yes
> > >    printable = no

 
 
 

XP and Samba 2.2.1a on RH 7.2 not working...

Post by Jan Svarrer S?lvste » Wed, 10 Jul 2002 02:47:39


Hmmm My problem turned out to be ipchains configuration....

Thnx for your help !!!!

/jan



Quote:> Hi there all you freindly Samba-wizards! :-)

> I have the problem that I can't access my Samba services from WinXP!
However
> though I CAN se the Samba server next to the other SM workgroup pc's - but
> clicking the Samba Server only gives me a dialog-box saying something like
> (it's in danish - so I translated it) : "No service operating at
> networkendpoint on the remote system"

> All tests made with smbclient etc.. are working on the Linux.

> However I cannot make an:

> c:\nbtstat -A 192.168.1.10       (thats on the client towards the server)

> See my smb.conf below:

> Best regards
> Jan

> #======================= Global Settings =============================#
> [global]

> # workgroup = NT-Domain-Name or Workgroup-Name
>    workgroup = SM

>    server string = Samba Server

>    hosts allow = 192.168.1. 127.

>    security = user

> # this tells Samba to use a separate log file for each machine
> # that connects
>    log file = /tmp/samba/%m.log
>    log level = 2

> [tmp]
>    comment = Temporary file space
>    path = /tmp
>    read only = no
>    public = yes

> [jansdir]
>    comment = Jan's service
>    path = /home/jan
>    valid users = jan
>    public = no
>    writable = yes
>    printable = no

 
 
 

1. tons of oplock errors [RH 7.2 + Samba 2.2.1a-4]

I am trying to move files from a Windows 2000 Server to a Redhat Linux
7.2 server running Samba 2.2.1a-4.

My problem is that while copying, I get timeouts on the Windows 2000
machine, and if I cancel the transfer, my user's smbd PID hits 100%
CPU Utilization. Here's a snip of my user's log:

<snip>

[2002/02/12 02:41:22, 0] smbd/nttrans.c:call_nt_transact_ioctl(1798)
  call_nt_transact_ioctl: Currently not implemented.
[2002/02/12 02:49:34, 0] smbd/oplock.c:request_oplock_break(997)
  request_oplock_break: no response received to oplock break request
to pid 2664 on port 32786 for dev = 4808, inode = 262147
  for dev = 4808, inode = 262147, tv_sec = 3c68c8c7, tv_usec = 12ef5
[2002/02/12 02:50:06, 0] smbd/oplock.c:request_oplock_break(997)
  request_oplock_break: no response received to oplock break request
to pid 2664 on port 32786 for dev = 4808, inode = 262147
  for dev = 4808, inode = 262147, tv_sec = 3c68c8c7, tv_usec = 12ef5
[2002/02/12 02:50:38, 0] smbd/oplock.c:request_oplock_break(997)
  request_oplock_break: no response received to oplock break request
to pid 2664 on port 32786 for dev = 4808, inode = 262147
  for dev = 4808, inode = 262147, tv_sec = 3c68c8c7, tv_usec = 12ef5
[2002/02/12 02:50:52, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 6028. Error = Interrupted system
call
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(356)
  process_local_message: Received unsolicited break reply - dumping
info.
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(371)
  process_local_message: unsolicited oplock break reply from pid 2669,
port 32786, dev = 4808, inode = 262147
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(356)
  process_local_message: Received unsolicited break reply - dumping
info.
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(371)
  process_local_message: unsolicited oplock break reply from pid 2669,
port 32786, dev = 4808, inode = 262147
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(356)
  process_local_message: Received unsolicited break reply - dumping
info.
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(371)
  process_local_message: unsolicited oplock break reply from pid 2669,
port 32786, dev = 4808, inode = 262147

<snip>

Here's my PID:

2670 ndelong   14   0  1880 1880  1544 R    99.6  0.5   0:17 smbd

I've gone and grabbed the latest Redhat 7.2 rpm from samba.org, but it
barks at me about samba-common and samba-client mismatches (where can
I find the latest rpms for those? - the ones I found on rpmfind.net
are currently the ones I have installed, and are not 2.2.3a)

Anyway, my question is what should I be looking for? I have
TCP_NODELAY set, and so_sndbuf=8192 , so_rcvbuf=8192 ...

Any direction would be much appreciated.

Nate D.

2. Invalid command

3. nmblookup (Samba 2.2.1a RedHat 7.2) can't find netbios names (newbie problem)

4. Easy-CD Pro 95 -- final attempt to post

5. Samba Server Installation 2.2.1a under Red Hat 7.2

6. PostgreSQL Performance issues

7. Unable to get server password authentication working - samba 2.2.1a & RH 7.1

8. Distilled Urls

9. Printing problems with RedHat 7.2 and Samba 2.2.3a

10. SAMBA 2.2.3a on RedHat 7.2 as PDC for Win2k

11. Samba 2.2.3a-1 on RedHat 7.2

12. Installing Samba 2.2.3a on Red Hat 7.2

13. Problem browsing in Win2k to RH 7.2 running samba