> There's always VNC: http://www.realvnc.com/ That way Windows won't know
> you're not sitting in front of it, and if you've got to access it from
> across the country on a linux or BSD or MAC box, it still works.
VNC requires additional port to be opened.
I have no free opened ports in W2K se
On Tue, 2006-04-04 at 16:07, Andrus wrote:
> Remote install of Postgres 8.1.3 using Windows installer binary package is
> not working (says that console mode is required) even when RDP client is
> started with
>
> mstsc /console
>
> switch.
>
> However, using installer package, creating cluster
> Second, make sure that you have the correct version of mstsc. mstsc /?
> will tell you if your current client supports the /console parameter.
> (If it doesn't, it'll silently eat it and ignore it)
I think I use mstsc from XP SP2
mstsc /? returns
---
Usage
> >> mstsc /console
> >
> > It should work fine with this switch. I've used it many times.
>
> I ran "mstsc /console" from my XP Proffessional and tried to
> install Postgres 8.1.3 in two different
> servers:
>
> Windows 2003
> Windows 2000
>
> Both cause the following message:
>
> ---
>> mstsc /console
>
> It should work fine with this switch. I've used it many times.
I ran "mstsc /console" from my XP Proffessional and tried to install
Postgres 8.1.3 in two different
servers:
Windows 2003
Windows 2000
Both cause the following message:
---
Internal er
> Remote install of Postgres 8.1.3 using Windows installer
> binary package is not working (says that console mode is
> required) even when RDP client is started with
>
> mstsc /console
>
> switch.
It should work fine with this switch. I've used it many times.
> However, using installer pack
Remote install of Postgres 8.1.3 using Windows installer binary package is
not working (says that console mode is required) even when RDP client is
started with
mstsc /console
switch.
However, using installer package, creating cluster and server process
manually works OK from RDP client!
Any id
