Re: URGENT! Legacy clients logon and connection unstable problem

From: Conrad Pfleging (cj_at_NOSPAMpflpfarm.com)
Date: 06/02/03 

Date: Sun, 1 Jun 2003 18:51:17 -0500

All those distinctions between native and mixed are nice, but what I think
the poster is trying to say is that he's talking about clients, not DC's. A
native mode domain can have pre win2k clients. It just can't have pre Win2K
domain controllers. Native v. Mixed is really not relevant to the clients.
My domain is native mode, and I have several Win 98SE clients with no
problems.

I know absolutely nothing about SQL so I really can't help him, but I think
you all are misunderstanding his situation and letting the native/mixed
thing lead you in the wrong direction.

"Rumen Yonov" <supervisor@wss-lovech.bg> wrote in message
news:OPbh7gIKDHA.1216@TK2MSFTNGP11.phx.gbl...
> <<<PLEASE REPLY TO SENDER'S ADDRESS>>>
>
> Hi,
>
> I just migrated from Windows 2000 Server PDC to Windows 2003 Server
> (Enterprise)
> I build the domain from scratch - i.e. enter computer & user accounts
> manualy.
>
> It works in Windows 2003 Server functional level - the upper one.
>
> I found several disadvantages with shared folders -
> I think because of new domain identity (in spite of the same NetBIOS name)
> and new accounts identities (in spite of the same NetBIOS names)
> it is impossible to use previous shared permissions -
> I ReCreated them again on every mashine :-(((
>
> I read that it is a must to install DSCLIENT.EXE on every legacy client
> machine to make possible to logon on to domain.
> OK - it was done!
>
> The MAIN PROBLEM is:
> Windows 9x clients do NOT enter domain every time - sometime enter
> but sometime do not (then in logon dialod box do not appear domain name)!?
> When I restart the machine - generally logon screen apperars with domain
> name.
>
> BUT THEN FOLLOWS MOST CONFUSE situation:
> Most of applications when try to make trusted (Windows authenticated)
> connection to an SQL Server 2000 (SP3) - installed on the same PDC,
> DO NOT succeed to open connections - BUT It is NOT permanent situation -
> sometimes the can, sometimes - do not :-(((
>
> I found that several minutes after the client machine starts I can browse
it
> from the PDC, if and if only if user can logon the domain!?
> But when all looks OK, after several minutes and several successful
> connections, client application is constantly refused from future
> connections
> and the only way to get access again to shared resources (SQL Server is
> only one of problems) on the network -
> looks like it is not still in the domain!? The machine remains
unaccessable
> from PDC, too - when try to access asks for password for \\HOST\IPC$ !?
>
> Please help me to solve this problem with legacy clients in the
> Windows 2003 Server domain. Are there any special features with
> WINS, DNS and other services configuration?
>
> May help to say that LAN is 10MB/s Ethernet BUS topology
>
> Thank you in advance for cooperation,
> Rumen Yonov
>
> PS: Please include some directions for MS-DOS 6.2 cleints - I have :-(((
>
> <<<PLEASE REPLY TO SENDER'S ADDRESS>>>
>
>
>

Relevant Pages

  • Re: Terminal Service - default log-on to domain vs local client
    ... all clients, you can perform the following steps: ... This newsgroup only focuses on SBS technical issues. ... you may want to contact Microsoft CSS directly. ... the "Logon to" box will disappear the latest logon ...
    (microsoft.public.windows.server.sbs)
  • RE: Login Script problem
    ... Welcome to SBS newsgroup. ... default mail clients from exchange to ISP on client via logon script. ... Exchange account on clients computer on SBS domain, ... User wizard is assigned a logon script SBS_LOGIN_SCRIPT.bat. ...
    (microsoft.public.windows.server.sbs)
  • Re: Clients often have to logon twice - What can be done?
    ... These are domain joined clients? ... And the dialogue box presented both times is the one generated by MSGINA? ... If you enable logon failure auditing on the local security policy, do you see any events in the Windows Security event log? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cached logon for multiple domain
    ... We have x no. of clients, say 10 and y no. of domain, say 2. ... clients need to logon. ... starts their VPN before connecting to their ... This seems to have problems with the DNS. ...
    (microsoft.public.windows.server.general)
  • Re: Remove SMS2 from Domain, Server and Clients
    ... then wait until logon server manager has removed all bits from all the ... After that happens, you can de-install your hierarchy from the bottom up, ... and a few clients. ... "Rosenberg David" wrote in ...
    (microsoft.public.sms.setup)