I seem to be seeing the same thing with my Feisty install. 2.6.20-15-generic, running on a Panasonic W4 notebook. Happens on both of the two different networks I have tried (interestingly, seems to happen more at my employer's network and less on my simpler home network).
Have tried both the builtin ethernet on this machine and a different ethernet adaptor (a USB dongle), they seem to behave identically. Earlier today I did a wireshark capture on the same machine while trying to do an rdesktop connection out. The rdesktop said "ERROR: connect: Resource temporarily unavailable", and there were no associated packets captured. (Other packets were captured, however, both broadcast traffic I wasn't part of and several packets from an IMAPS session I had open.)
Makes it hard to use this machine. (Any work-around suggestions? Other than booting back from my Dapper install.)
Thanks,
-kb, the Kent who can Dapper, a light Feisty install, or a heavy Feisty install--if that is useful to anyone.
I seem to be seeing the same thing with my Feisty install. 2.6.20-15-generic, running on a Panasonic W4 notebook. Happens on both of the two different networks I have tried (interestingly, seems to happen more at my employer's network and less on my simpler home network).
Have tried both the builtin ethernet on this machine and a different ethernet adaptor (a USB dongle), they seem to behave identically. Earlier today I did a wireshark capture on the same machine while trying to do an rdesktop connection out. The rdesktop said "ERROR: connect: Resource temporarily unavailable", and there were no associated packets captured. (Other packets were captured, however, both broadcast traffic I wasn't part of and several packets from an IMAPS session I had open.)
Makes it hard to use this machine. (Any work-around suggestions? Other than booting back from my Dapper install.)
Thanks,
-kb, the Kent who can Dapper, a light Feisty install, or a heavy Feisty install--if that is useful to anyone.