Re: Best practices for remotely connecting
From: Stijn Verrept (stijn_at_no_s.p.a.n.entrysoft.com)
Date: 01/14/04
- Next message: Peter Kaufman: "Login name is <none>"
- Previous message: Kevin McDonnell [MSFT]: "Re: Best practices for remotely connecting"
- In reply to: Kevin McDonnell [MSFT]: "Re: Best practices for remotely connecting"
- Next in thread: Kevin McDonnell [MSFT]: "Re: Best practices for remotely connecting"
- Reply: Kevin McDonnell [MSFT]: "Re: Best practices for remotely connecting"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 14 Jan 2004 01:53:44 GMT
Kevin McDonnell [MSFT] wrote:
> So, unless the client as a Terminal Server that you can install the
> SQL Client tools, your options are limited.
What do you mean? The client is running a terminal server. And I can
log in on that machine. The problem is that it does not have
Enterprise manager. This is why I need to connect with my enterprise
manager to the terminal server through the net. Isn't this possible?
Why doesn't it want to work?
-- Kind regards, Stijn Verrept.
- Next message: Peter Kaufman: "Login name is <none>"
- Previous message: Kevin McDonnell [MSFT]: "Re: Best practices for remotely connecting"
- In reply to: Kevin McDonnell [MSFT]: "Re: Best practices for remotely connecting"
- Next in thread: Kevin McDonnell [MSFT]: "Re: Best practices for remotely connecting"
- Reply: Kevin McDonnell [MSFT]: "Re: Best practices for remotely connecting"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]