Jump to content

Samba and WinXP network


Guest BlackWolf
 Share

Recommended Posts

Guest BlackWolf

Hi,

 

I'm using Mandrake 10.1 Community.

 

I have a network composed of one WinXP Pro box and a Linux MDK Box.

 

On the Linux Box, I installed Samba and Linneighborhood.

 

On the Linux box, I tried to connect to the WinXp box by Linneighborhood, but it didn't worked. I was only able to see the Linux box on my domain. But I was able to mount a share from the WinXp box by using Konqueror with smb://thecomputer/theshare or by using smbmount.

 

On the WinXP box, I wasn't able to see anything in the domain. It gave me an error saying the domain is not available or maybe I don't have the rights...

 

So I put the log screen on in Linneighborhood and saw the command used. I duplicated these commands in a Konsole to see the status.

 

In the Konsole, with the option used by Linneighborhood for the nmblookup command, only the Linux Box is seen. When I remove the Master Browser option, both machine are seen but still only the Linux box status is displayed.

 

After the nmblookup command, Linneighborhood issue a smbclient command using the info from the status so it only sees the Linux box.

 

Then I had to boot my linux box in WinXp to get my email. I checked to see if the other WinXp box was seeing me now. And It did see me as usual. So I boot back my Linux box in MDK and Voila!!! the WinXp Box is now able to see the Linux Box and vice-versa. I checked the shares and everything was working fine in Linneighborhood. But one thing is strange, the WinXP box is logged with my username and if I look at the available share on the Linux Box, I see the home directory of another user (the person usually using this box), not mine.

 

So I rebooted the Linux Box to see what would happen and of course, It came back to the beggining. The WinXP Box don't see anything on the domain and Linneighborhood on the Linux Box only sees the Linux Box itself. But again, I'm able to mount the shares by explicitely giving their address on both box.

 

I know that once in a while, when both machine was running WinXp, it happens that we were not able to see a machine on the domain.

 

Can someone help me resolve that problem?

 

Thanks

Link to comment
Share on other sites

Guest BlackWolf

Hi SoulSe,

 

Here is my smb.conf file:

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2004/11/05 11:10:55

# Global parameters
[global]
       workgroup = TOTO
       server string = Samba Server %v
       map to guest = Bad User
       obey pam restrictions = Yes
       guest account = smbguest
       passwd program = /usr/bin/passwd %u
       passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n
       log file = /var/log/samba/log.%m
       max log size = 50
       socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
       dns proxy = No
       ldap ssl = no
       printer admin = @adm

[homes]
       comment = Home Directories
       read only = No
       create mask = 0750
       directory mask = 0750
       browseable = No

[Partage]
       comment = Partage
       path = /home/partage
       valid users = user1, user2
       write list = user1, user2

[HPPSC2210]
       comment = HP PSC 2210
       path = /var/spool/samba
       read only = No
       create mask = 0700
       guest ok = Yes
       printable = Yes
       printer name = HPPSC2210
       use client driver = Yes
       browseable = No
       oplocks = No
       share modes = No

 

I also include the ifconfig:

eth0      Lien encap:Ethernet  HWaddr 00:E0:18:97:6F:9D
         inet adr:169.254.215.136  Bcast:169.254.255.255  Masque:255.255.0.0
         adr inet6: fe80::2e0:18ff:fe97:6f9d/64 Scope:Lien
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:854 errors:0 dropped:0 overruns:0 frame:0
         TX packets:970 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 lg file transmission:1000
         RX bytes:282501 (275.8 Kb)  TX bytes:131935 (128.8 Kb)
         Interruption:9 Adresse de base:0x8800

lo        Lien encap:Boucle locale
         inet adr:127.0.0.1  Masque:255.0.0.0
         adr inet6: ::1/128 Scope:Hôte
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:1114 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1114 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 lg file transmission:0
         RX bytes:86288 (84.2 Kb)  TX bytes:86288 (84.2 Kb)

ppp0      Lien encap:Protocole Point-à-Point
         inet adr:69.157.248.121  P-t-P:64.230.254.63  Masque:255.255.255.255
         UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
         RX packets:622 errors:0 dropped:0 overruns:0 frame:0
         TX packets:749 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 lg file transmission:3
         RX bytes:240332 (234.6 Kb)  TX bytes:94197 (91.9 Kb)

 

And the route:

Table de routage IP du noyau
Destination     Passerelle      Genmask         Indic Metric Ref    Use Iface
64.230.254.63   *               255.255.255.255 UH    0      0        0 ppp0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         64.230.254.63   0.0.0.0         UG    0      0        0 ppp0

 

Some days ago I was able to see the network fine with the same smb.conf file, but when I tried to mount a share from the WinXP box, it didn't worked and I discovered it was because my password used ponctuation and was ending with a comma/B]. The smbmount command send its information separeted by a comma/B], so the two comma/B] with nothing in between mess up the smbmount command and it returned me an error like: 9251: session setup failed : ERRDOS - ERRnoaccess.

 

So I changed the password in samba and I was then able to mount shares from the WinXP box and I was still seeing the network.

 

But the next day, I changed the password on the Linux Box to not use ponctuation anymore, since it was possible to have problems with it. I changed the root and my user password.

 

After that I stopped seeing the full network.

 

I have the feeling the problem is caused by the fact that the windows network is using dynamic IP address. I setup the Linux box to use static address because it didn't worked when I had dynamic address.

 

Could it be that when I boot my Linux box in Windows, the WinXP box finds the IP address of what is available on the network and remembers it. When I boot back the Linux box in MDK 10.1, the Linux box gets the IP address back from the WinXP box so everything works fine. But if I reboot the Linux box I don't get the IP address anymore.

 

In Linneighborhood, when I'm not able to see the WinXP box, it says my Linux box is a master without browse list.

 

I'm going nuts, please help me.

 

Thanks

Link to comment
Share on other sites

  • 2 weeks later...

set all ip addresses to static, or have the linux box static, and set up DHCP so it assigns addresses to the windows machine.

 

Or - see if you can ping from windows to linux when your network neighbourhood doesn't work, then you'll know it's more likely to be a samba issue.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...