Re: URGENT! Legacy clients logon and connection unstable problem

From: Sam Salhi [MSFT] (samers_at_online.microsoft.com)
Date: 06/02/03 

Date: Sun, 1 Jun 2003 16:12:54 -0700

The new functional level is native mode, Older versions of windows might not
function properly at this level
(Only Windows 2000, XP and Windows Server 2003) Can work at this level.
Win9x and NT will need the older "Mixed" mode. 

-- 
===========================================================
This posting is provided "AS IS" with no warranties and confers no rights
===========================================================
"Rumen Yonov" <supervisor@wss-lovech.bg> wrote in message
news:OzIs8#IKDHA.2096@TK2MSFTNGP12.phx.gbl...
> I do not have any other servers in the LAN - only clients!
> As I said - It works in Windows 2003 Server functional level - the upper
> one.
> It's NOT the mixed or native mode! It is 2003 specific NEW functional
level!
>
> ---------------------------------
> "Wajihy [MSFT]" <wajihy@online.microsoft.com> wrote in message
> news:u7naHqIKDHA.1612@TK2MSFTNGP11.phx.gbl...
> | what is the functionality level of the new windows 2003 domain? (
native?,
> | mixed?)
> |
> | becasue you will need a mixed mode domain as long as you have some
servers
> | running windows 98 and windows 2000
> |
> | --
> |
> | This posting is provided "AS IS", with NO warranties and confers NO
rights
> | "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: Keeping NT4 servers in 2003 Native Domain
    ... I thought I was pretty clear in describing the NT4 servers as Member servers ... I suspect you are using Windows 2000 mix mode other than Windows 2000 ... native mode since you still keep Windows NT 4.0 BDC. ...
    (microsoft.public.windows.server.migration)
  • Re: Keeping NT4 servers in 2003 Native Domain
    ... The switch to native mode only affects the replication between the NT 4.0 ... BDCs and the AD DCs. ... I thought I was pretty clear in describing the NT4 servers as Member ... I suspect you are using Windows 2000 mix mode other than Windows 2000 ...
    (microsoft.public.windows.server.migration)
  • RE: DFS
    ... Based on my research, to enable all features in DFS Namespaces, you must ... Servers where namespace management tasks are performed must run Windows ... Clients that access namespaces can run any of the supported client ...
    (microsoft.public.windows.server.sbs)
  • Re: NT4 Domain Design Question
    ... You'd need to install your SMS 2003 servers and site systems on Windows 2003 ... You could make your Windows 2003 servers member servers in the NT ... The client is upgrading to windows 2003 active ...
    (microsoft.public.sms.setup)
  • Re: What type of licenses and costs we need to upgrade to Windows 2003 AD?
    ... > We are planning to upgrade to Windows 2003 AD. ... > licenses we need to get us to Windows 2003 Active directory? ... every client who's accessing services on the Windows Servers. ...
    (microsoft.public.windows.server.active_directory)