Hi,
I moved sql 2000 server from server that is a Domain Controller to new
machine that is a Domain Member.
Now my clients using XP HOME cannot connect to new server: "login failed
for user null"...
1. on the client user login = domain login and user passwd = domain
password.
2. It works with old server that is running on domain controller.
3. on the station we use NT authentication
4. new server is added to active directory, is running as domain\user
with administrative grants.
5. computers that are in domain (xp pro) and win98 works without any
problem.
6. server accept connection in mixed mode (nt + sql)
I use sql 2000 sp3 (for now) and win2000 server sp4
Is anyone who found this problem?
What can cause that error?
Re: Client performance problem windows 2003 server... ... >Subject: Re: Client performance problem windows 2003 server...... >Deploying Active Directory for Branch Office Environments... >results from not having a domain controller in a particular site. ... incorrectly applied site coverage will be bad for clients... (microsoft.public.windows.server.networking)
Re: Client performance problem windows 2003 server... ...Testing server: Verkstadsgatan\VERKTYG ... Deploying Active Directory for Branch Office Environments... results from not having a domain controller in a particular site. ... incorrectly applied site coverage will be bad for clients... (microsoft.public.windows.server.networking)
Netlogon 5783 ... For about there mounts I<m having small network problem, with clients, that ... The session setup to the Windows NT or Windows 2000 Domain Controller... On DC1r there is Exchange 2000 server, witch is Exchange system manager is ... The failure code from authentication protocol Kerberos... (microsoft.public.win2000.networking)
Re: Getting tons of topology discovery errors. ... I've since converted the exchange server into an active ... All Domain Controller... >>>"NSPI Proxy can contact Global Catalog... New clients will be refused ... (microsoft.public.exchange.admin)
