I have read in older posts that if you run Domino 6.5.3 server as a service in Windows 2000, then you can’t see the Domino server through Terminal Services. In our case, we too can’t see the Domino console when accessing it through Terminal Services. Domino is set up as a service. We can see it if we go to the server or in Timbuktu.
Are there any workarounds for this issue that I have not heard of? Thanks.
Subject: Terminal Services Client and Domino Console
In Windows2000 there isn’t a workaround. If server is Windows2003 you can open a remote desktop connection by a command line with switches. I’ve not used it though. Search the forum, it’s been posted I think.
Subject: Terminal Services Client and Domino Console
Have you considered using the Java Server controller. This gives you the ability to use a Java console client to connect to the JSC, then you can start and stop the Domino server as required.
Subject: Terminal Services Client and Domino Console
Hi Lori,From prior experience working with Terminal Services, it doesn’t matter if Domino is setup as a service or not. You will not see the console. Terminal Services is not like PC Anywhere or VNC where you are seeing the actual server screen as if you were at the server. It’s really a remote client connecting similar to Telnet. At my former employer we used VNC and Terminal Services. VNC came in handy to see the Domino console and the error generated when it locked up. Terminal Services was used as another option. If security is a concern, just ensure that you always log off after a VNC session so that you still need to login to access the server.
Subject: Terminal Services Client and Domino Console
with windows 2003 server, you can domstsc.exe /console
I make two separate shortcuts for the remote desktop client.
If you’re using Windows 2000, you can configure VNC to allow local loopback.