111 replies to this topic

[superleok]

Mmmh. Nice and very suspicious.

I will do a fresh install and check again.

Promisc Mode solved. It was a network patch (ET9000) from Iceware (et-view-support forum). He moved eth0 to the second cpu core and made some IPv4 improvments.

Is there anything new about samba? I will compile a new samba but the box has limited space and samba was growing up in the last two years.

[superleok]

1)
https://bugzilla.sam...bug.cgi?id=8238

2)
KB2536276
Security bulletin MS11-043
Note The use of plain text passwords is no longer supported in Samba.

This problem occurs if the following condition is true:
"bytecount <8" & & encryptkeylength=0

"Bytecount" is the length of the computer's workgroup or domain name. This problem occurs if the workgroup or domain name is less than 8 bytes, including the null terminator.

Try this:

1. Uninstall KB2536276
2. http://www.enterpris...s-7-Clients.htm
3. Create New DWord Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa (Value: 1 / hexadecimal)
4. Disable Ipv6: http://support.microsoft.com/kb/929852
5. Reboot Winows 7 and Reboot Box

Workaround if you can't uninstall KB2536276

To work around this problem, follow these steps: http://support.micro...b/2536276/en-us[list=1]
[*]Disable plain text configuration on both client and server computers.
[list]
[*]To do this on the server computer, add the following line to the configuration file on the affected server:
Encrypt passwords=Yes Note By default, the server configuration file is named "smb.conf."
[*]To do this on the client computer, set the EnablePlainTextPassword registry entry to a value of 0 (zero) and then restart the computer. To configure the EnablePlainTextPassword registry entry, follow these steps:
[list=1]
[*]Click Start, click Run, type regedit in the Open box, and then click OK.
[*]Locate and then click the following subkey in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\LanmanWorkstation\Parameters
[*]Right-click EnablePlainTextPassword, and then click Modify.
[*]In the Value data box, type 0, and then click OK.
[*]Exit Registry Editor, and then restart the computer.
[/list]
[/list]
[/list]

[superleok]

Update:

3: Create New DWord Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa (Value: 1 / hexadecimal)

DWord Key = LmCompatibilityLevel
Value = 1

[superleok]

After Changes the communication between Samba and Win7 works fine. Win7 get Backup List from ET9000.

Attached Files

•  browse_protocol_win7_1_.png   505.53KB   28 downloads

Edited by superleok, 12 February 2013 - 19:12.

[MachIII]

Got this same problem with my Ultimo, startes for about one month ago. Can it be related to the same issue?
I have tried @superleok's suggestions over here, but no luck so far...

[Ivan]

I'm allways using the same workgroup in smb.conf as in my Windows Configuration. And there ist no Problem to find a OpenPLi 3.0 mashine in my Network. If i change the workgroup, i have the same problem.

[superleok]

Got this same problem with my Ultimo, startes for about one month ago. Can it be related to the same issue?
I have tried @superleok's suggestions over here, but no luck so far...

Never give up. Please send smb.conf and tell me your Windows Workgroup. Do you See the box in Network Neighborhood.

Edited by superleok, 13 February 2013 - 19:25.

[MachIII]

It's ok now after I changed workgrup in smb.conf. Wasn't aware of that, thank you!

[superleok]

A suggestion to PLI Team (maybe Openpli 4). The OpenWRT Router Team has patched Samba 3.6.x. to produces smaller binaries.

Some user qoutes:

This full featured Samba 3.6.x version works like a charm with win7 ;-)

I've done some more optimization, uncompressed binary size is now down to 2.7M and it still works fine with Windows 7.

Disscussion:

https://dev.openwrt....ticket/9992#no2

https://dev.openwrt....changeset/30489

[BBsat]

Is the word workgroup in smb.conf case sensitive?
Its written in uppercase (workgroup = WORKGROUP) in my file.

[superleok]

Is the word workgroup in smb.conf case sensitive?
Its written in uppercase (workgroup = WORKGROUP) in my file.

Hello,

Windows uses default Workgroup Name of "WORKGROUP". Normally Workgroup Names are not case sensitive but Windows always use uppercase Format.

e.g.

Windows Workgroup Name: TEST123

smb.conf

workgroup = TEST123

Edited by superleok, 22 February 2013 - 18:24.

[BBsat]

Clear, THNX