URGENT! Legacy clients logon and connection unstable problem

From: Rumen Yonov (supervisor_at_wss-lovech.bg)
Date: 06/01/03 

Date: Mon, 2 Jun 2003 00:53:23 +0300

<<<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: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: after installing KB011829 OWA is not working anymore
    ... Based on my research, after you install hotfix KB911829, I suggest we ... Profile WMI Provider to each client computer that is running Windows Vista ... If you are running the Premium Edition of Windows Small Business Server ...
    (microsoft.public.exchange.connectivity)
  • Re: DHCP Issues. Very strange
    ... I understand the issue to be: some client computers ... can not obtain IP from SBS server. ... it is most possible a client side issue of Windows ... since you have join it to SBS domain and the Windows XP SP2 ...
    (microsoft.public.windows.server.sbs)
  • Authentication flaw in microsoft SMB protocol
    ... Microsoft uses SMB Protocol for “File and Printer sharing service” in all ... Authentication is used to authenticate the client on the server. ... logged-in user requests for a network share on the server, Windows ...
    (Bugtraq)