Donald, Thanks for the update. That is some great detective work.
Jim McQuillan [EMAIL PROTECTED] On Thu, 21 Oct 2004, Donald Teed wrote: > I have found the source of my problems with rdesktop > and intermittant failures. I tried another Windows server > as the target and it worked reliably. Then I checked the > first test target W 2003 server and noticed it had a firewall > running. A bunch of ICMP features were being blocked. > When the firewall was disabled, the connections became > 100% good. When I enabled it again and allowed all > types of ICMP traffic, I sometimes saw a pause at the > grey screen with the X pointer, but then within a few > seconds it sucessfully arrived at the Windows Login > screen. So my best hunch is that some type of ICMP > message regarding dropped packets or something > similar was not being sent by the Windows server > due to this Windows firewall setting. > > Thanks for the suggestions anyway. > > I've noticed some other people on the mailing list > with reports of rdesktop failing. Perhaps they > can check their Windows firewall as well. > > On Wed, 20 Oct 2004 23:27:40 +0200, Anselm Martin Hoffmeister > <[EMAIL PROTECTED]> wrote: > > Am Mittwoch, 20. Oktober 2004 16:39 schrieb Donald Teed: > > > I have 3 Dell D600 notebooks for testing as clients to connect > > > with a Windows 2003 server using rdesktop. I have a working > > > configuration, but I find that the success in connecting has > > > no logical pattern. It fails to connect about 30% of the time. > > > > [...] > > > > > Does anyone have a suggestion on where the weakness could be? > > > Are there any suggestions on a way to trace the stalled launch > > > of rdesktop? > > > > <rant> I know that "not getting a connection" error from running the M$ > > supplied Win98 Client on a 98 machine (having the terminal client started > > automagically instead of the win-exploder - I guess 30% nearly is the value I > > had on several of those boxes - they wouldn't let me run them as LTSP > > machines (even against a windoze server) anyway cause "linux is so > > obscure"</rant> > > > > I'd check name resolution (put the windoze machine/terminal box IP into the > > hosts file (for the terminal, check /etc/hosts from the shell) and on the > > windoze box), turn off DNS) or use ethereal to see what's different on the > > wire when the machines fail to connect. Might even be a licensing issue > > (those made up about 50% of the working hours on my only ever win TS system); > > check if you have at least one free license all the time to be sure windoze > > won't refuse you because of that. > > In case the network part looks alike in both successful and unsuccesful tries > > to connect, perhaps even the windoze logfile^H^H^H^Hcrap can help. OK, it > > won't help, but at least you should make sure that there's really nothing in > > there that could be worth a look. > > > > Regards, > > Anselm > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _____________________________________________________________________ > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > For additional LTSP help, try #ltsp channel on irc.freenode.net > ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
