From: Carmel <car...@ho...> - 2010-12-15 13:39:23
|
This is my first time using "rdesktop". I have the program installed on a FreeBSD-8.2 / amd 64 system. I installed it via the FreeBSD ports system. I am attempting to connect to either of two Windows based machines on my local network. This is really a trail run I suppose. One machine runs WinXP and the other has Vista installed. Both machines are completely up-to-date. Machine one has ZoneAlarm installed as the firewall if that matters. I apparently cannot connect to either machine successfully. WinXP Connecting as regular user: $ rdesktop -f 192.168.1.102 ERROR: 192.168.1.102: unable to connect As root: # rdesktop -u USERNAME -p PASSWORD -f 192.168.1.102 WARNING: Remote desktop does not support colour depth 24; falling back to 16 ERROR: recv: Connection reset by peer Now, when I actually try the second method, the WinXP machine does a new log-in. I have to manually enter my username and password on the WinXP screen to access the PC. Once in, the message above appears on the FreeBSD screen and that is that. I cannot fathom why I have to log-in on the WinXP machine. When I attempt to access the Vista machine, a quick flash appears on the screen of the FreeBSD machine and then the regular prompt returns. The Vista machine is running AVG AV/Firewall software. I have, or at least I think I have port 3389 open on all of the machines. There is no notification on wither of the Windows machines that I am attempting to access them remotely. I believe that I have correctly configured both machines for remote access. They have been accessed remo I am at a total loss as to what i am doing wrong, although it is probably something extremely simple. My goal is to run the WinXP machine headless at some point in the future and access it via rdesktop if that is possible. At present, I would just like to be able to remotely access it via my FreeBSD machine. -- Carmel ✌ car...@ho... Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. __________________________________________________________________ In every non-trivial program there is at least one bug. |
From: Christopher R. <cj...@tr...> - 2010-12-15 16:34:18
|
On Wednesday 15 Dec 2010, Carmel wrote: > This is my first time using "rdesktop". I have the program installed on > a FreeBSD-8.2 / amd 64 system. I installed it via the FreeBSD ports > system. > > I am attempting to connect to either of two Windows based machines on > my local network. This is really a trail run I suppose. One machine > runs WinXP and the other has Vista installed. Both machines are > completely up-to-date. > > Machine one has ZoneAlarm installed as the firewall if that matters. I > apparently cannot connect to either machine successfully. > > WinXP > Connecting as regular user: > $ rdesktop -f 192.168.1.102 > ERROR: 192.168.1.102: unable to connect > > As root: > # rdesktop -u USERNAME -p PASSWORD -f 192.168.1.102 > WARNING: Remote desktop does not support colour depth 24; falling back to > 16 ERROR: recv: Connection reset by peer This is set on the Windows box, but colour depth 16 is the standard for rdp, and shouldn't cause a problem - you can either change the Windows box to allow color depth 24, or add color depth 16 to the rdesktop command line (-a 16 from memory), or just ignore the error. > Now, when I actually try the second method, the WinXP machine does a > new log-in. I have to manually enter my username and password on the > WinXP screen to access the PC. Once in, the message above appears on the > FreeBSD screen and that is that. I cannot fathom why I have to log-in > on the WinXP machine. Is the WinXP machine authenticating via ActiveDirectory, if so you would also need to supply the -d domain. > When I attempt to access the Vista machine, a quick flash appears on the > screen of the FreeBSD machine and then the regular prompt returns. The > Vista machine is running AVG AV/Firewall software. I have never touched Vista, so I don't know what this might be - I suppose it could be ActiveDirectory again? > I have, or at least I think I have port 3389 open on all of the > machines. > > There is no notification on wither of the Windows machines that I am > attempting to access them remotely. I believe that I have correctly > configured both machines for remote access. They have been accessed > remo Have you looked in the Windows event log on each machine? > I am at a total loss as to what i am doing wrong, although it is > probably something extremely simple. My goal is to run the WinXP > machine headless at some point in the future and access it via rdesktop > if that is possible. At present, I would just like to be able to > remotely access it via my FreeBSD machine. I have every confidence that it will work with a little persistence, I've certainly never had an issue in connecting to WinXP and Server 2003 machines. Let us know how you get on. -- Chris Roberts |
From: Carmel <car...@ho...> - 2010-12-15 18:41:25
|
On Wed, 15 Dec 2010 16:16:45 +0000 Christopher Roberts <cj...@tr...> articulated: > On Wednesday 15 Dec 2010, Carmel wrote: > > This is my first time using "rdesktop". I have the program > > installed on a FreeBSD-8.2 / amd 64 system. I installed it via the > > FreeBSD ports system. > > > > I am attempting to connect to either of two Windows based machines > > on my local network. This is really a trail run I suppose. One > > machine runs WinXP and the other has Vista installed. Both machines > > are completely up-to-date. > > > > Machine one has ZoneAlarm installed as the firewall if that > > matters. I apparently cannot connect to either machine successfully. > > > > WinXP > > Connecting as regular user: > > $ rdesktop -f 192.168.1.102 > > ERROR: 192.168.1.102: unable to connect > > > > As root: > > # rdesktop -u USERNAME -p PASSWORD -f 192.168.1.102 > > WARNING: Remote desktop does not support colour depth 24; falling > > back to 16 ERROR: recv: Connection reset by peer > > This is set on the Windows box, but colour depth 16 is the standard > for rdp, and shouldn't cause a problem - you can either change the > Windows box to allow color depth 24, or add color depth 16 to the > rdesktop command line (-a 16 from memory), or just ignore the error. > > > Now, when I actually try the second method, the WinXP machine does a > > new log-in. I have to manually enter my username and password on the > > WinXP screen to access the PC. Once in, the message above appears > > on the FreeBSD screen and that is that. I cannot fathom why I have > > to log-in on the WinXP machine. > > Is the WinXP machine authenticating via ActiveDirectory, if so you > would also need to supply the -d domain. > > > When I attempt to access the Vista machine, a quick flash appears > > on the screen of the FreeBSD machine and then the regular prompt > > returns. The Vista machine is running AVG AV/Firewall software. > > I have never touched Vista, so I don't know what this might be - I > suppose it could be ActiveDirectory again? > > > I have, or at least I think I have port 3389 open on all of the > > machines. > > > > There is no notification on wither of the Windows machines that I am > > attempting to access them remotely. I believe that I have correctly > > configured both machines for remote access. They have been accessed > > remo > > Have you looked in the Windows event log on each machine? > > > I am at a total loss as to what i am doing wrong, although it is > > probably something extremely simple. My goal is to run the WinXP > > machine headless at some point in the future and access it via > > rdesktop if that is possible. At present, I would just like to be > > able to remotely access it via my FreeBSD machine. > > I have every confidence that it will work with a little persistence, > I've certainly never had an issue in connecting to WinXP and Server > 2003 machines. > > Let us know how you get on. OK, I used the "-a" switch and that apparently eliminated one problem. However, I still cannot get control of the WinXP machine from my FreeBSD PC. This is the latest error message: # rdesktop -u USER -p PASSWORD -a 16 laptop.seibercom.net ERROR: recv: Connection reset by peer I am running KDE on the FreeBSD machine. I then switch to terminal and run the above command. A blank window appears on my FreeBSD machine. Now the screen on the WinXP machine goes blank, a quick log-ion screen appears on the FreeBSD machine and then disappears (approx 1/2 second) then a log-in screen appears on the WinXP machine. I log-in and then clink on the blank screen on the FreeBSD machine. That is when the above error message is displayed. I have Samba installed, and it works fine between the two machines. I am able to transfer files without a problem. I have no idea how to debug this. There is no active directory running. The WinXP machine is basically a standalone PC. I am getting absolutely nowhere with the Vista machine. -- Carmel ✌ car...@ho... Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. __________________________________________________________________ |
From: Christopher R. <cj...@tr...> - 2010-12-16 09:04:15
|
On Wed, Dec 15, 2010 at 01:41:16PM -0500, Carmel wrote: > # rdesktop -u USER -p PASSWORD -a 16 laptop.seibercom.net > ERROR: recv: Connection reset by peer You could try adding a "-n clienthostname" switch, this has solved this problem in the past. Without this switch, rdesktop uses the PC's hostname to connect, perhaps you have used the same hostname previously and the Windows box is blocking the reuse of that hostname? I suspect it is a Windows licensing issue. Setting the client hostname manually to something different from the PC hostname may just work. > I am running KDE on the FreeBSD machine. I then switch to terminal and > run the above command. A blank window appears on my FreeBSD machine. > Now the screen on the WinXP machine goes blank, a quick log-ion screen > appears on the FreeBSD machine and then disappears (approx 1/2 second) > then a log-in screen appears on the WinXP machine. I log-in and then > clink on the blank screen on the FreeBSD machine. That is when the > above error message is displayed. > > I have Samba installed, and it works fine between the two machines. I > am able to transfer files without a problem. > > I have no idea how to debug this. There is no active directory running. > The WinXP machine is basically a standalone PC. I am getting absolutely > nowhere with the Vista machine. Perhaps you could try the above and let us know how you get on. Perhaps others on this list have other ideas. -- Chris Roberts |