Solved

Problem while loading profile in Windows XP while logging on to a samba server

Posted on 2008-10-24
6
1,196 Views
Last Modified: 2013-12-16
Oct 24 15:44:05 mainserver samba(pam_unix)[32338]: session opened for user magesh.prabhu by (uid=0)
Oct 24 15:44:22 mainserver samba(pam_unix)[32346]: session opened for user sujatha.p by (uid=0)
Oct 24 15:44:33 mainserver smbd[32351]: [2008/10/24 15:44:33, 0] lib/util_sock.c:get_peer_addr(1224)
Oct 24 15:44:34 mainserver smbd[32351]:   getpeername failed. Error was Transport endpoint is not connected
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/access.c:check_access(327)
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/util_sock.c:get_peer_addr(1224)
Oct 24 15:44:34 mainserver smbd[32351]:   getpeername failed. Error was Transport endpoint is not connected
Oct 24 15:44:34 mainserver smbd[32351]:   Denied connection from  (0.0.0.0)
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/util_sock.c:get_peer_addr(1224)
Oct 24 15:44:34 mainserver smbd[32351]:   getpeername failed. Error was Transport endpoint is not connected
Oct 24 15:44:34 mainserver smbd[32351]:   Connection denied from 0.0.0.0
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/util_sock.c:write_data(562)
Oct 24 15:44:34 mainserver smbd[32351]:   write_data: write failure in writing to client 192.168.10.140. Error Connection reset by peer
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/util_sock.c:send_smb(761)
Oct 24 15:44:34 mainserver smbd[32351]:   Error writing 5 bytes to client. -1. (Connection reset by peer)
Oct 24 15:44:34 mainserver samba(pam_unix)[32352]: session opened for user selva.kumar by (uid=0)
Oct 24 15:44:34 mainserver samba(pam_unix)[24942]: session closed for user selva.kumar
Oct 24 15:44:34 mainserver samba(pam_unix)[25527]: session closed for user magesh.prabhu
Oct 24 15:44:34 mainserver samba(pam_unix)[25205]: session closed for user sujatha.p

Above is a sample of logs from the "messages" log file.  We have a network with Windows XP systems (SP2) and patched for all critical updates.

The distribution of Linux we run is Red Hat Enterprise ES 4.0.  The samba server has been configured as a domain controller (without LDAP).  Of late we have observed that Windows XP client systems are posing problems while logging on to the domain.  After entering the username and password, some client systems get stuck at the stage of "Loading Personal profile" and do not proceed further.  Of course, we have figured a way out by unplugging the network cord and logging on and then connecting the cord so that the server can be accessed.

Can someone provide a hint or a solution to solve this problem?
0
Comment
Question by:hariprasad74
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 20

Expert Comment

by:nedvis
ID: 22804525
Please refer to this answer fromone of our experts:
http://www.experts-exchange.com/Networking/Linux_Networking/Q_22997189.html?eeSearch=true

I think your Windows XP clients and RedHat samba server are trying to negotiate protocols using different and mismatching ports  
and that's why you have to unplug and reconnect network cables
in order to skip protocol negotiation ( Error: getpeername failed. Error was Transport endpoint is not connected )

Also , try adding the following to your smb.conf file:
 smb ports = 445
(the default is smbports = 445 139).

 Among the new ports used by Windows 2000, Windows XP and Windows Server 2003, is TCP port 445 which is used for SMB over TCP.

The SMB (Server Message Block) protocol is used among other things for file sharing in Windows NT/2000/XP. In Windows NT it ran on top of NetBT (NetBIOS over TCP/IP), which used the famous ports 137, 138 (UDP) and 139 (TCP).
 In Windows 2000/XP/2003, Microsoft added the possibility to run SMB directly over TCP/IP, without the extra layer of NetBT. For this they use TCP port 445.
0
 

Author Comment

by:hariprasad74
ID: 22839240
The error messages got cleared out.  But the original problem of Windows XP hanging while loading the profile continues.  

Below is the smb.conf file for reference:

[global]
        workgroup = XXXXXXXXX
        server string = server of xxxxxxx Domain
        interfaces = 192.168.10.221/24
        obey pam restrictions = Yes
        password server = None
        passdb backend = tdbsam
        pam password change = Yes
        unix password sync = Yes
        client NTLMv2 auth = Yes
        log level = 1
        log file = /var/log/samba/%m.log
        max log size = 1024
        smb ports = 445
        time server = Yes
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        add user script = /usr/sbin/useradd -d /home/'%u' -M '%u'
        delete user script = /usr/local/sbin/userdel '%u'
        add group script = /usr/local/sbin/groupadd '%g'
        delete group script = /usr/local/sbin/groupdel '%g'
        logon script = logon.bat
        logon path =
        logon drive = Z:
        logon home =
        domain logons = Yes
        os level = 99
        preferred master = Yes
        domain master = Yes
        dns proxy = No
        wins support = Yes
        ldap ssl = no
        idmap uid = 16777216-33554431
        idmap gid = 16777216-33554431
        admin users = root
        hosts allow = 192.168.10., 127.
        cups options = raw

[homes]
        comment = Home Directories
        read only = No
        browseable = No

[netlogon]
        comment = Network Logon Service
        path = /home/netlogon
        guest ok = Yes
        browseable = No
        share modes = No

[sysvol]
        path = /home/policy
        guest ok = Yes
        browseable = No
        share modes = No

[printers]
        comment = All Printers
        path = /var/spool/samba
        printable = Yes
        browseable = No
0
 
LVL 20

Expert Comment

by:nedvis
ID: 22860107
Sure there's problem.
You have to define user profile location on your samba server, so Windows XP
will try to locate user profile (data stored in NTUSER.DAT ) on the server.
A user profile (userprofile, or simply profile is configurated when used in-context) is a feature of the Microsoft Windows operating system, comprising a given user's collection of personal documents and settings on that computer. At first logon, a folder will typically be created under "Documents and Settings" matching the logon-name of the user.
So you need to add {profile} seciton in your samba configuration file.
In the [profiles] section the path variable tells where the profiles are to be placed and make sure the directories are created with right names and permissions.

[profiles]
create mode = 0600
directory mode = 0700
path = /home/samba/profiles/
profile acls = yes
read only = no
writable = yes

Also you may want to tweak a liitle bit more {homes} section of the config file
In the [homes] section the following entries are important :

[homes]
comment = Home Directories
browseable = no
writable = yes
valid users = %S
read only = no
create mode = 0600
directory mode = 0700

logon home = \\your_samba_server\%U //  (This tells where is the user home directory )

hide files = /*.pst/

========================================================
Here's a good article on joining Win XP machines to Samba domain
http://w3t.org/u/82js
=======================================================

0
Simple, centralized multimedia control

Watch and learn to see how ATEN provided an easy and effective way for three jointly-owned pubs to control the 60 televisions located across their three venues utilizing the ATEN Control System, Modular Matrix Switch and HDBaseT extenders.

 

Author Comment

by:hariprasad74
ID: 22883669
Nope, I tried adding those sections in the smb.conf file.  But this simply did not work.  Any other suggestions?  Do you require any logs or other information to troubleshoot further?
0
 

Accepted Solution

by:
hariprasad74 earned 0 total points
ID: 22919962
I was able to figure out the problem.  The NTUSER.DAT file under the netlogon folder had a problem.  I have replaced the file and things are working fine now.
0
 
LVL 20

Expert Comment

by:nedvis
ID: 22923267
Very good,
now you can close question.
At least we tried our best.
sincerely '
nedvis
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

SSH (Secure Shell) - Tips and Tricks As you all know SSH(Secure Shell) is a network protocol, which we use to access/transfer files securely between two networked devices. SSH was actually designed as a replacement for insecure protocols that sen…
Fine Tune your automatic Updates for Ubuntu / Debian
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question