windbg - kernel debugging problem

hi all
i know plenty of similar questions have been posted before, but after 
reading, i'm still having a problem on debugging my device driver from a host 
computer.
both my host and targets computers are vista sp1. (if it matters the target 
is a laptop and host is desktop)
i'm using com1 on both host and target machines. 
in the target machine i have added a debug entry 
(as explained in this article: ->  
http://www.microsoft.com/whdc/driver/tips/debug_vista.mspx )
from the host i run windbg by command line like this:
"windbg -y xxxMySymbolPathxxx -k com:port=\\.\com1"
the windbg runs and is "waiting" for a connection
then, i boot my target machine and. after a while (pretty slow i must say) 
the machine fully loads vista os but in the windbg i get the following output:




Microsoft (R) Windows Debugger  Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \\.\com1
Waiting to reconnect...
Connected to Windows Vista 6000 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: C:\Windows\Symbols
Executable search path is: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for 
ntkrnlmp.exe - 
Windows Vista Kernel Version 6000 MP (1 procs) Free x86 compatible
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81800000 PsLoadedModuleList = 0x81908ad0
System Uptime: not available
ZwQuerySystemInformation (1) did not return STATUS_BUFFER_TOO_SMALL 
(0xc0000023), instead NTSTATUS 0xc0000225


(the last line appeared a bit after the others and not consistantly)
in the command line of windbg i see "not connected" as well
the result happend while i tested 2 differant targets and 2 differant hosts

i read in another topic that its ok, and that a should kill windbg and run 
kd by the following : kd -k com:port=1 ... and do the following tests : 
1. ctrl+c 
2. ctrl+d
3. Print-Screen from the target to break KD
all tests succeeded and seems kd is connected
now the topic says to remote KD, and attach to the remoted session with 
windbg but i dont understand wat it means (i tried the "attach to
process" in 
the windbg menu, but didnt understand what happend and if its wat i need)