"XDM: too many retransmissions" Error.

Question

Hi,
I try to connect my Mac to a distant linux server using the command:
" xhost +"
"X :1 -query HOSTID"
from the X11 application.
Its open Xquark and say that it creates a display. But, nothing appear on my monitor. I wait few minute and it returns the error message:
"XDM: too many retransmissions, declaring session dead"
I try also with "Xnest", but the problem is similar. It creat a window and nothing appears insinde.
Somebody know solutions to my problem ?

Answer 1

Andamion,
ssh and X11 is generally binary. Either a window (xterm for example) opens remotely or it does not.
Does anything work - at all? If so - these are not the cause of the retransmission errors. (I was under the impression that you have everything working except xnest and occasionally some retransmission errors)
I would tent to go with Andy's diagnosis that it really is a network issue and you have an unreliable transport. If even some of the time X11 works fine - then you can rule out any sort of confugiration issue.
To use an analogy - think of the packets as physicsal letters and the network as the post. You appear to be addressing everything correctly, paying the correct postage, using the correct zip code (or whatever the French equivalent of a postal code is - I hope you are not saddled with zip codes - you are doing nothing wrong (other than having too high expectations perhaps).
If it is a network problem - you can learn to diagnose it (knowing that you will only know the root cause - but probably not be able to change it) - or you can pay for a different carrier or pay for a higher level of service with some guarantee of reliability or uptime.
Now to your speficic questions - no cache is simply a warning that you have not pre-shared cryptgraphic keys or certificates on both sides. SSH will work just fine without this as long as another authentication method is allowed and succeeds (a correct user/password for example)
The xauth warning is also benign (as long as at lease one X function works) - this is a legacy method of validating remote connections - most X setups avoid xauth these days and ssh is being nice to warn you that xauth is not fully set up - so it is "faking" it on one end to allow your secure connection to work.
Cheers!
Mike
P.S. Xnest could certainly be the problem. I have not ever needed to use it - but I have heard of lots of people that had problems understanding it or getting it to work. Unfortunately - you'll have to wait for someone with experience with Xnest to help if it is a configuration issue for that program... (I'm 95% convinced you have no X11 issue at this point)