Public bug reported:
Binary package hint: tsclient
Terminal Server Client was working fine until, I accidentaly typed in a wrong
port to connect to: instead of something like mydomain.com:55555 I typed
mydomain.com:55666655, as soon as I pressed enter the tsclient window
dissapeared. I launch it again, try to connect to a correct ip address, but as
soon as I hit connect the window dissapears and no connection. I went into
processes and killed 3 instances of tsclient, but same thing. I also rebooted
my machine but it still refuses to work.
By the way, I was trying to connect to a pc with windows xp proffesional.
Ubuntu 8.04 hardy
tsclient: Installed: 0.150-1ubuntu1
** Affects: tsclient (Ubuntu)
Importance: Undecided
Status: New
** Tags: tsclient
** Description changed:
Binary package hint: tsclient
- Terminal Server Client was working fine until, I accidentaly typed in a
- wrong port to connect to: instead of something like mydomain.com:55555 I
- typed mydomain.com:55666655, as soon as I pressed enter the tsclient
- window dissapeared. I launch it again, try to connect to a correct ip
- address, but as soon as I hit connect the window dissapears and no
- connection. I went into processes and killed 3 instances of tsclient,
- but same thing. I also rebooted my machine but it still refuses to work.
+ Terminal Server Client was working fine until, I accidentaly typed in a wrong
port to connect to: instead of something like mydomain.com:55555 I typed
mydomain.com:55666655, as soon as I pressed enter the tsclient window
dissapeared. I launch it again, try to connect to a correct ip address, but as
soon as I hit connect the window dissapears and no connection. I went into
processes and killed 3 instances of tsclient, but same thing. I also rebooted
my machine but it still refuses to work.
+ By the way, I was trying to connect to a pc with windows xp proffesional.
Ubuntu 8.04 hardy
tsclient: Installed: 0.150-1ubuntu1
--
TSClient nowhere to be found
https://bugs.launchpad.net/bugs/279533
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
