Re: LANS, Terminal Servers, and the internet
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 22 May 2005 07:46:53 -0700
Aaah, so not only can you not connect to your TS once you connect
to your ISP, but any existing connections are disconnected as well?
Then it's not only a DNS problem, as I thought at first.
Check these articles, I think there might be a problem with the
route table and the default gateway, which is changed when you
connect to your ISP.
242051 - RDP Client Can Lose Connection to Terminal Server If
Terminal Server Initiates a RAS Session to a Remote Server
http://support.microsoft.com/?kbid=242051
270857 - How to Use a Modem with Terminal Services
http://support.microsoft.com/?kbid=270857
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
"=?Utf-8?B?UmFuZHkgU2FuZGVycw==?="
<RandySanders@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 22 maj 2005 in
microsoft.public.windows.terminal_services:
> Thanks for responding with your advice. Although you are
> correct, that my ISP probably has its own DNS Servers (NT 4.0
> probably), I also have my own DNS Servers configured properly
> within my own domain. When you asked me if I could connect when
> I use my servers IP number, instead of the name? Did you mean
> connect with ISP or with one of my Terminal servers?
>
> Since my modem is configured to get IP addresses automatically,
> I assume you meant connecting to my Terminal Servers with one of
> my static IP addresses (from NIC Card) and yes I can connect to
> either Terminal Server (using name or IP address) as long as I
> am not connected to the net. As soon as I connect to the net,
> Terminal Services sessions are automatically disconnected. Y
>
> "Vera Noest [MVP]" wrote:
>
>> Check your DNS configuration. When you connect to the Internet,
>> you are probably using your ISPs DNS?
>> Can you connect when you use your servers IP number, in stead
>> of the name?
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> "=?Utf-8?B?UmFuZHkgU2FuZGVycw==?=" <Randy
>> Sanders@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 17 maj 2005 in
>> microsoft.public.windows.terminal_services:
>>
>> > I have a small local area network that presently has two
>> > computers on it. Terminal services works well between the two
>> > computers ( both are configured with Windows 2000 Advanced
>> > Server) whenever I am not connecred to the net. However when
>> > I am connected to the net Terminal services cannot find my
>> > local server. Why? Do i need to configure another port? if so
>> > which one? Is there an easy way to solve this problem without
>> > configuring a port? What is the best solution?
>> > randyswon@xxxxxxxxxxx
.
- Follow-Ups:
- Re: LANS, Terminal Servers, and the internet
- From: Randy Sanders
- Re: LANS, Terminal Servers, and the internet
- References:
- LANS, Terminal Servers, and the internet
- From: Randy Sanders
- Re: LANS, Terminal Servers, and the internet
- From: Vera Noest [MVP]
- Re: LANS, Terminal Servers, and the internet
- From: Randy Sanders
- LANS, Terminal Servers, and the internet
- Prev by Date: cannot save to disk on TS
- Next by Date: Re: LANS, Terminal Servers, and the internet
- Previous by thread: Re: LANS, Terminal Servers, and the internet
- Next by thread: Re: LANS, Terminal Servers, and the internet
- Index(es):
Relevant Pages
|