Windows Server 2003

When Topcat is installed on Windows Server 2003 there are some issues to resolve:

	If the Windows Server 2003 is a Domain Controller, clients will not be able to boot and instead will get the Access not allowed (Error number &166B4) error.
	The error: Unable to create files in "LanMan::Armboot.$.!Boot.Resources.!Scrap.ScrapDirs", error returned is "Access not allowed" (Error number &6) may also be observed during booting. The client may continue to boot but will eventually stop with the error: Bad Parameters (Error number &16601).
	For Topcat version 1.4, clients will freeze after booting to the desktop. Topcat v1.4.7 is not compatible with Windows Server 2003 and users should upgrade to Topcat Version 2.
	For Topcat version 2, clients will receive the "Error from Server" message and will not connect. Topcat Update 2.07 or later fixes this problem. To download this update, click here.
	The NetBEUI protocol is not included in the distribution of Windows Server 2003.

Procedure

It is necessary to relax security on Windows Server 2003 Domain Controllers - by default Network access is required to be digitally signed, and Topcat does not support this. Follow the instructions given in the Microsoft Knowledge Base article at: http://support.microsoft.com/default.aspx?scid=kb;en-us;811497 to relax security and allow Topcat clients to connect.
By default the share permissions on Windows Server 2003 are set to Read Only for Everyone. Set the Permissions to Full Control for Everyone for the Topcat$, Armboot$ and Server$ shares.
Install NetBEUI protocol on the Windows Server 2003 using the Windows XP Professional CD. See the Microsoft Knowledge Base article http://support.microsoft.com/default.aspx?scid=kb;en-us;301041 for more information.

[ Home ] [ Up ]