<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: Michael Da Cova <mdacova,AT,equiinet,DOT,com>
Subject: Re: CIPE XP
From: Carsten Emde <ce,AT,ceag,DOT,ch>
Date: Fri, 20 Jun 2003 01:19:10 +0200
Cc: "'cipe-l,AT,inka,DOT,de'" <cipe-l,AT,inka,DOT,de>
In-reply-to: <193F46660487D3119850009027D0CEF5F9526D@EQUIINET01>
Organization: CE Computer Experts AG
References: <193F46660487D3119850009027D0CEF5F9526D@EQUIINET01>

Michael,

What I am trying to do is on boot up of XP pro you have a option to login to
a NT domain over a dialup,
This feature is normally not required. You need first to logon to your domain using a normal network link (XP caches the domain data locally). When you then logon at another place where you do not have a LAN link to your domain controller and you plan to use a dialup connection, login as if the controller were available. By default, Windows XP (in contrast to NT and 2k) will *not* complain that the domain controller is not available but let you logon - any network shares, obviously, will not be available. You may then start your dialup connection to the Internet. At the first attempt to open a file or a folder on a network share, the share becomes available. If you have enabled CIPE's key encryption, you must provide the pass phrase and re-enable CIPE manually. This is an important feature to protect the LAN behind CIPE against unauthorized access and justifies its inconvenience in most environments.

Is your server an NT server with SP prior to SP6a? Then Windows NT 4.0 SP6a Is Recommended for Windows XP Clients in a Windows NT 4.0 Domain (http://support.microsoft.com/default.aspx?scid=kb;en-us;313384) may be important for you.

The following text snippet was taken from http://www.microsoft.com/mspress/books/sampchap/5566e.asp:
To speed the startup and logon process, Windows XP Professional does not
require that the network be fully initialized before a client computer
can start up or before a user can log on. If a user has previously
logged on to a particular client computer, he or she is subsequently
logged on using credentials cached on that computer.
When a user switches from using a local profile to using a roaming
profile, Windows XP Professional copies relevant portions of the user's
registry from the server instead of from the local computer, to prevent
an older local copy from overwriting the server copy. Thereafter,
whenever the roaming user logs on, the computer always waits for the
network, so the profile can be downloaded from the server.
When fast network logon is enabled (as it is by default in Windows XP
Professional), if administrators remove the profile path from a user's
object, it is recommended that they also either rename or delete the
corresponding profile folder. If they do not, and an administrator later
reenters the same path, the user will receive the older copy of the
registry from the server.


What I cant get to work now is to have the DKW adapter Service start
automatically I have is set it on start-up type = automatic
It works here without any problem. You may click with the right mouse button on CIPE panel's title bar (About CIPE ...) and check whether the server is running or not.

Carsten Emde.


<< | Thread Index | >> ]    [ << | Date Index | >> ]