Topic: SME as domain name controller !?!??

[Alex]

I have set up SME to be master Domain name controller and when user try to connect there is a message: No domain controller was available to confirm your password, maybe some of network resources will be unavailable...bla bla

All network resources are available only this stupid mesage that comes twice is quite disturbing. If you have any ideas you are welcome. I have searched this forums and find: nothing.

BTW. OS-es that we are using are Windows Millenium, have not tried with 98 or XP and for now I'm not planning to.


Regards,
Alexa

[Steve Brock]

Is the client getting an IP properly? can you ping the IP of your SME server from the client you're trying to connect from?
Correct me if I'm wrong, but doesn't ME (like xp) need registry changes?

[Alex]

Hi,

Thanks for your replay, I have found solution with restarting SME and it works fine now. And about your question NO win ME does not need registry change the only reg. change that 98 and ME needs is connected with password caching, probably this is for security reasons no other use of that.

Sorry for bothering this forum

Bye,

Steve Brock wrote:
>
> Is the client getting an IP properly? can you ping the IP of
> your SME server from the client you're trying to connect from?
> Correct me if I'm wrong, but doesn't ME (like xp) need
> registry changes?

[Tim Burgess]

hi,
i have nothing to offer in the way of a solution, however, i have 2 win98 clients that have developed the same problem in the last 2 weeks. if you click ok, you can ping the server and connect to network shares just fine. 3 other win98 clients are working fine. simply no domain login.

On the faulty machine NO user can access the domain.
i have tried removing network adapter and reinstalling - nothing.

TimB

[Alex]

Hi,

Maybe you should do same as I did, remove that clients from samba's config and add them again as described in forums here, or you should just reboot the server and maybe it will work (as I did)

[Tim Burgess]

After puting my 2cents worth in yesterday - I thought I had better come and reveal my solution - which has worked for nearly 24 hours now.

On ALL windows clients I had to add the e-smith servers ip to the wins tab in the tcpip properties.

I had a weird day. After I did this to the first problem machine, slowly each other client in the network failed during the day. WINS fixed every one of them. Why? The only thing I have to add is that the one lone XP workstation (which used to be the 'server') was turned off.

I am dying to read any explanation.  :-}

[Boris]

I guess that XP computer had the highest windows version number in your workgroup and used to win the election for  “Browse Master” role. Now every computer is asking your server for NetBIOS name resolution and it works.
If you were using SME as a DHCP server and "Domain or Workgroup controller" option was checked, it would point all the clients to itself as WINS server and raise its own "windows version number" to become the Browse Master automaticaly.  This would make correct name resolution transparent for you and your users. Unless you have good reason to do otherwise that would be default and preffered way of configuring Single SME in the small network to simplify administration of the clients.

[Tim Burgess]

Of course! now the penny drops - Normally I use the sme box as dhcp but there is an cisco box doing a vpn - from another state that was configured to hand out ip's. That day I had problems - there wasnt enough power points so I disconnected the XP box - for the first time ever!

Yes your right about the elections - I had assumed the sme box would always win but I overlooked the dhcp connection.

thanks for solving that mistery

As life and luck would have it - I am removing the cisco box next weekend for ever and making the sme do dhcp - this has been planned for the  last 3 months. Timing!