| Author |
Message |
Pierrot Robert
Guest
|
 Posted:
Tue Nov 01, 2005 5:50 pm Post subject:
Slow connection to Terminal Server |
|
|
I have a Windows Server 2003 machine with Terminal Services in application
mode. All the client are Windows XP SP2.
Everything was going well but since yesterday some clients have a very long
delay before the logon screen. Sometimes it times out, sometimes it connects
after about 1 minute. Other clients connect instantly.
All the clients are on the same subnet, same switch than the server. Once
connected, application performance is good.
4 days ago, I changed the firewall from a multi-homed computer to a Cisco
router. I don't see how this could be related to this problem because the
client do not go through the firewall to connect to this server.
Typing the IP address (10.1.1.17) instead of the server name does not
resolve the problem, so it is not a name resolution issue.
Any ideas ?
Pierrot |
|
| Back to top |
|
 |
Pierrot Robert
Guest
|
| Posted:
Tue Nov 01, 2005 5:50 pm Post subject:
Re: Slow connection to Terminal Server |
|
|
10.x.x.x are private IP addresses.
"CJT" <abujlehc@prodigy.net> wrote:
| Quote: | Pierrot Robert wrote:
I have a Windows Server 2003 machine with Terminal Services in
application mode. All the client are Windows XP SP2.
Everything was going well but since yesterday some clients have a very
long delay before the logon screen. Sometimes it times out, sometimes it
connects after about 1 minute. Other clients connect instantly.
All the clients are on the same subnet, same switch than the server. Once
connected, application performance is good.
4 days ago, I changed the firewall from a multi-homed computer to a Cisco
router. I don't see how this could be related to this problem because the
client do not go through the firewall to connect to this server.
Typing the IP address (10.1.1.17) instead of the server name does not
resolve the problem, so it is not a name resolution issue.
Any ideas ?
Pierrot
Is that an appropriate IP address? Who assigned it?
--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net. |
|
|
| Back to top |
|
|
CJT
Guest
|
| Posted:
Tue Nov 01, 2005 5:50 pm Post subject:
Re: Slow connection to Terminal Server |
|
|
Pierrot Robert wrote:
| Quote: | I have a Windows Server 2003 machine with Terminal Services in application
mode. All the client are Windows XP SP2.
Everything was going well but since yesterday some clients have a very long
delay before the logon screen. Sometimes it times out, sometimes it connects
after about 1 minute. Other clients connect instantly.
All the clients are on the same subnet, same switch than the server. Once
connected, application performance is good.
4 days ago, I changed the firewall from a multi-homed computer to a Cisco
router. I don't see how this could be related to this problem because the
client do not go through the firewall to connect to this server.
Typing the IP address (10.1.1.17) instead of the server name does not
resolve the problem, so it is not a name resolution issue.
Any ideas ?
Pierrot
Is that an appropriate IP address? Who assigned it? |
--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net. |
|
| Back to top |
|
|
CJT
Guest
|
| Posted:
Wed Nov 02, 2005 9:39 am Post subject:
Re: Slow connection to Terminal Server |
|
|
Pierrot Robert wrote:
| Quote: | 10.x.x.x are private IP addresses.
|
D'oh! I don't know what I was thinking.
| Quote: |
"CJT" <abujlehc@prodigy.net> wrote:
Pierrot Robert wrote:
I have a Windows Server 2003 machine with Terminal Services in
application mode. All the client are Windows XP SP2.
Everything was going well but since yesterday some clients have a very
long delay before the logon screen. Sometimes it times out, sometimes it
connects after about 1 minute. Other clients connect instantly.
All the clients are on the same subnet, same switch than the server. Once
connected, application performance is good.
4 days ago, I changed the firewall from a multi-homed computer to a Cisco
router. I don't see how this could be related to this problem because the
client do not go through the firewall to connect to this server.
Typing the IP address (10.1.1.17) instead of the server name does not
resolve the problem, so it is not a name resolution issue.
Any ideas ?
Pierrot
Is that an appropriate IP address? Who assigned it?
--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.
|
--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in