Topic: Samba/workgroup error with 2 servers

[Beast]

Hi

Have 2 servers on the same sub-net (different names and ip).
One of them is configured as a domain/workgroup controller and DHCP server (not the other one)

The problem is that when I browse the network from Windows I can see both servers but when I access the workgroup controller unit I only see the shares from the other server (also files from the other server when I enter a share).

What can be wrong?

If I enter the ip directly in stead of the server name it works correctly.

Thanks in advance

[brianr]

Not sure what you mean by "workgroup controller unit".

[Beast]

In the server-manager under workgroup there is an option to enable "Workgroup and Domain Controller" and one of the servers have this option enabled.

[brianr]

ok, so that is the domain controller,  so far so good.

Now please explain how you examine the network from the domain controller and can't "see" the network.  I would not normally expect you to access the network from the domain controller, as it is a samba network which is designed  to be access from Windows machines (which you say CAN see the shares).   Are you using the smbclient program?  If so, please let us know what parameters you are giving it.

[Beast]

I am just browsing the network from a windows client computer (set up for workgroup). If I go to the Network Neigborhood (or what the name is in the English version) I can see 2 SME server with different names (this is also what I expect). The problem is that when I enter the shares of the SME server that act as domain and workgroup controller I see the shares from the other SME server (under the name of the other server). If I see the shares for the other server (the one that do not act as a domain controller) I see the correct shares (the same as the other one show).

To put it short - I simply see the same shares under 2 different server names. The one I see belong to the server that do not act as a Domain and Workgroup controller?

If I enter the IP address instead of the servername in the address line of the browser window it shows the correct shares for both servers. So some how the names get mixed up - but how?

[brianr]

ok, now i see the problem.  This could be a bug, perhaps in SME or perhaps in Samba.

Or even perhaps in your Windows box - is it on XP and up to date?

I have used multiple SMEservers, and have not seen this problem, but I do not have anything at the moment I can really check on.

Suggest you document it in the bug tracker, so that people more skilled than me can help you out.

[Beast]

Using XP and it is up to date etc.

Nobody reply in the bug tracker - no use to post

BUT - it work right now after the latest update to the samba lib (today) from the automatic SME updater!

So something was wrong!

[phvdkley]

Don't understand that you updating the sambalib soved the problem.

just typed an idea bases on our experience with more than one SME on the same lan. Maybe it's still of some use to you so here it is

Have you setup Hostnames and adresses in server-manager/configuration?
When you install two SME-servers within the same domain like "mydomain.org", with hostnames as www1 and www2, You'll get some conflicts in the mentioned configurationarea of server-manager.
On server www1 there will be a ftp.mydomain.org with the IP of www1.
On server www2 there will also be a ftp.mydomain.org with the IP of www2.
AND for mail..... proxy.... wpad.....and www......

Your DNS on both servers may have a conflict because of this resulting in the strange filesharing behaviour.

Depending on the services you use, modify them to the correct IP or delete the entries.

In our situation VPN, supported by the mainserver failed becouse of the dubbel entries.

CU

[Beast]

Do not think there will be a conflict because they have different domain/server names. This means that ftp.xxx.yy the x is a unique name on the servers!

Only some of the shares will have the same name!