Client Troubles connecting to Terminal server.

I have some W2K workstations at a remote site that can connect to a W2K
server running Terminal Services. This connection is across an ISDN line
with Ascend Pipeline routers at each end. Remote site subnet is 172.20.31.0.
Main site subnet 172.20.30.0. Remote site workstations actually log on to
the main site network across the ISDN connection. I installed a new Windows
2003 server with Terminal Services at the main site. Now when I try to
connect to the new server I get this message:

The client could not connect to the remote computer or the computer might be
too busy to accept new connections. It is also possible that network problems
are preventing your connection.

I can connect to the new and old terminal server from home without problems
using DSL and vpn connection. We also have DSL at the remote site now and
when using the DSL connection at the remote site instead of the ISDN I can
connect to the new server. But only one computer at a time can connect to
the VPN. The others will time out when trying to establish the VPN
connection. When using the DSL connection at the remote site I removed the
workstions from the Domain and created a workgroup for them.

So my problem is with the ISDN connection the remote computers cannot
connect to the new 2003 Terminal services computer. When I change from the
ISDN connection and drop them from the domain. I can connect one of the
workstation through the VPN to the new and old terminal servers. The other
workstation timeout on the VPN connection.

What have i missed? Am I making this more complicated then it should be?
Any help would be appreciated.
Thanks.

I would check the MTU first. this link may help,

connection issues after 2003 sp1
Q: Connection issues after applying Server 2003 SP1 ... A: It could be the MTU
issue. (Note: check this page for the details ...
www.chicagotech.net/Q&A/2003sp1b.htm
connectivity issues after ms05-019 and 2003 sp1
Connectivity issues after the installation of MS05-019 or Server 2003 SP1 ...
However, an MTU value of 576 should help reduce the effect of the problem ...
http://www.howtonetworking.com/Troub...g/2003sp1a.htm

How to change mtu
How to change MTU settings. By default, Windows Server 2003, 2000 and XP use a
fixed maximum transmission unit (MTU) size of 1500 bytes for all PPP ...
www.howtonetworking.com/VPN/mtu1.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Learning" <(E-Mail Removed)> wrote in message news:5E19E6C9-0F2C-45F4-809C-(E-Mail Removed)...
I have some W2K workstations at a remote site that can connect to a W2K
server running Terminal Services. This connection is across an ISDN line
with Ascend Pipeline routers at each end. Remote site subnet is 172.20.31.0.
Main site subnet 172.20.30.0. Remote site workstations actually log on to
the main site network across the ISDN connection. I installed a new Windows
2003 server with Terminal Services at the main site. Now when I try to
connect to the new server I get this message:

The client could not connect to the remote computer or the computer might be
too busy to accept new connections. It is also possible that network problems
are preventing your connection.

I can connect to the new and old terminal server from home without problems
using DSL and vpn connection. We also have DSL at the remote site now and
when using the DSL connection at the remote site instead of the ISDN I can
connect to the new server. But only one computer at a time can connect to
the VPN. The others will time out when trying to establish the VPN
connection. When using the DSL connection at the remote site I removed the
workstions from the Domain and created a workgroup for them.

So my problem is with the ISDN connection the remote computers cannot
connect to the new 2003 Terminal services computer. When I change from the
ISDN connection and drop them from the domain. I can connect one of the
workstation through the VPN to the new and old terminal servers. The other
workstation timeout on the VPN connection.

What have i missed? Am I making this more complicated then it should be?
Any help would be appreciated.
Thanks.