SOLVED - Samba and Windows 7 conflict

[goldfish777]

I have one desktop that has Windows 7 on it, one regular laptop with Windows 7, one gaming laptop with Windows 7, one laptop with Vista and another laptop with XP all on the same network. I also have a small home server with Linux on it and Samba shares.

My desktop has no problem accessing the shares. The same goes for the regular laptop with 7, the one with Vista and the one with XP. They all work fine with no problems. The issue is with the gaming laptop. it cannot access the Samba shares, most of the time.

If the server were to get rebooted while the gaming laptop was on the network than it can access the shares. If the laptop were to be turned on while the server is active than it cant access the shares. An error pops up that says it cant connect.

The shares are protected with a username and password. I am running samba 3.5. Here is my config file:

[global]
workgroup = AV1611
netbios name = breeze
os level = 100
encrypt passwords = yes
announce version = 9.0
socket options = TCP_NODELAY IPTOS_LOWDELAY
SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192
security = user
null passwords = true
preferred master = auto
domain master = yes
local master = yes
wins support = yes

[doug]
path = /shares/doug
read only = no
browsable = yes

[backupcds]
path = /media/data1/backupcds
read only = no
browsable = yes

[mp3]
path = /media/data1/mp3share
read only = no
browsable = yes
public = yes
write list = wind, stream, root

[sherah]
path = /shares/sherah
read only = no
browsable = yes

[Data]
path = /media/data2
read only = no
browsable = yes

[john]
path = /shares/john
read only = no
browsable = yes

Why am I having these problems?

[goldfish777]

Well I found the solution. What you need to do if a windows machine cant access the shares, then map the shares either as a network location or a network drive. Either one will work. This is all assuming that your samba config file is setup properly. As for why one laptop worked and the other didn't, I have no idea.


Moderators you may mark this as SOLVED.