Woellert, Kirk D. wrote: > MIT-SHM extension disabled due to lack of kernel support > XFree86-Bigfont extension local-client optimization disabled due to lack of > shared memory support in the kernel > (==) winConfigKeyboard - Layout: "00000409" (00000409) > (EE) No primary keyboard configured > (==) Using compiletime defaults for keyboard > Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = > "(null)" > winPointerWarpCursor - Discarding first warp: 637 481 > winBlockHandler - Releasing pmServerStarted > winBlockHandler - pthread_mutex_unlock () returned > winDeinitClipboard - Noting shutdown in progress > winDeinitMultiWindowWM - Noting shutdown in progress > winDeinitClipboard - Noting shutdown in progress > winDeinitMultiWindowWM - Noting shutdown in progress > winDeinitMultiWindowWM - Noting shutdown in progress > winDeinitClipboard - Noting shutdown in progress > winDeinitMultiWindowWM - Noting shutdown in progress
There is no evidence why xdmcp failed. Is a firewall (even the winxp builtin) present? Can you check the xdm logfiles on the server? Maybe they contain some information why you can't get access. @Harold: Are the winDeinitClipboard and -MultiWindowWM messages ok? I assume they are called even if the -multiwindow and -clipboard parameters are not supplied. NP: Enya - Shepherd Moons -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
