Can't connect with XDMCP - Invalid MIT-MAGIC-COOKIE-1 key

[Harold L Hunt II]

Alexander [Skwar],

Wait, let me get this straight.  You DO have two network cards, one in 
the notebook and one in the docking station, right?  Now, are you sure 
that you are using the same network card on both network segments?  That 
is, are you using the built-in network card on both segments and you are 
never using the docking station's network card?  If that is the case, 
then I suspect that you problem is when you are plugged into the docking 
station and XWin.exe thinks that it should use the docking station's 
NIC, which does not have an IP address (thus the 0.0.0.0).

The easiest solution would be to use the -from parameter.

Other possible solutions:

1) Plug into the network at the docking station via the docking 
station's NIC.  XWin.exe wants to use that NIC by default, so XWin.exe 
will work correctly without the -from parameter (probably).

2) Disable the docking station's NIC in your Windows hardware 
configuration.  This will hopefully case XWin.exe to not even see the 
docking station's NIC as an option.

3) Change the binding order or NIC preference (if there even is such a 
thing) in your Windows hardware configuration.  I am going out on a limb 
here... I do not remember if this can be done.

4) Stop using your docking station.

5) See if Alexander Gottwald has any ideas to save the day :)


Harold

Alexander Skwar wrote:

>Alexander,
>
>Zitat von Alexander Gottwald <alexander.gottwald@s1999.tu-chemnitz.de>:
>
>  
>
>>Have you tried the -from <yourhost> parameter? The 0.0.0.0 seems like Xwin
>>can't find the correct interface and uses an uncofigured one (maybe
>>dialup)
>>    
>>
>
>No, I haven't tried -from.  I just now did, and with -from, I can connect.
>
>Do I understand you right?  It's the "fault" of XWin that it sends the 
>0.0.0.0 IP?  Hmm...
>
>[c:\programme\jedit 4.1pre6]ipconfig /all
>
>Windows-IP-Konfiguration
>
>        Hostname. . . . . . . . . . . . . : D8RJRJ0J
>        PrimÀres DNS-Suffix . . . . . . . :
>        Knotentyp . . . . . . . . . . . . : Hybrid
>        IP-Routing aktiviert. . . . . . . : Nein
>        WINS-Proxy aktiviert. . . . . . . : Nein
>
>Ethernetadapter LAN-Verbindung:
>
>        Medienstatus. . . . . . . . . . . : Es besteht keine Verbindung
>
>        Beschreibung. . . . . . . . . . . : 3Com 3C920 Integrated Fast
>Ethernet Controller (3C905C-TX Compatible)
>        Physikalische Adresse . . . . . . : 00-08-74-3E-FD-E2
>
>Ethernetadapter LAN-Verbindung 2:
>
>        Verbindungsspezifisches DNS-Suffix: wup.de.delphiauto.com
>        Beschreibung. . . . . . . . . . . : 3Com 3C920 Integrated Fast
>Ethernet Controller (3C905C-TX Compatible) #2
>        Physikalische Adresse . . . . . . : 00-B0-D0-0C-DF-B5
>        DHCP aktiviert. . . . . . . . . . : Ja
>        Autokonfiguration aktiviert . . . : Ja
>        IP-Adresse. . . . . . . . . . . . : 204.104.237.188
>        Subnetzmaske. . . . . . . . . . . : 255.255.255.0
>        Standardgateway . . . . . . . . . : 204.104.237.250
>        DHCP-Server . . . . . . . . . . . : 204.104.237.181
>        DNS-Server. . . . . . . . . . . . : 205.191.7.228
>                                            192.85.104.90
>        Lease erhalten. . . . . . . . . . : Mittwoch, 27. November 2002
> 07:58:21
>        Lease lÀuft ab. . . . . . . . . . : Donnerstag, 28. November 20
>02 07:58:21
>
>As you can see, I've got two NICs.  The 1st "Ethernetadapter LAN-Verbindung"
>is the built-in NIC in my notebook.  The 2nd "Ethernetadapter LAN-Verbindung
>2" is the one from my docking station.  That might also explain, why the
>Windows NT PC is able to connect w/o -from.  It's a "normal" desktop PC and
>has got only one NIC.
>
>Thanks!
>
>Alexander Skwar
>  
>