RDP timeout with DNS enabled

[Damon]

Hi. Our older clients--Win 9.x PCs and CE<4.0 thin clients--timeout when
trying to connect to a Windows 2003 Terminal Server. When DNS is disabled and
they are given a static IP, Subnet, and Gateway, they connect fine. DHCP is
handled by Windows 2000 Domain Controllers. AD and DNS are installed on a
Windows 2000 Server. I'm not sure where to start with this...

 

[Damon]

RE: RDP timeout with DNS enabled

Some more info: These same clients can connect just fine to Windows 2000
Terminal Servers. Also, licensing mode for the Windows 2003 Terminal Servers
is Per User.


"Damon" wrote:

> Hi. Our older clients--Win 9.x PCs and CE<4.0 thin clients--timeout when
> trying to connect to a Windows 2003 Terminal Server. When DNS is disabled and
> they are given a static IP, Subnet, and Gateway, they connect fine. DHCP is
> handled by Windows 2000 Domain Controllers. AD and DNS are installed on a
> Windows 2000 Server. I'm not sure where to start with this...

 

[OxygeN]

Re: RDP timeout with DNS enabled

Damon ha scritto:
> Hi. Our older clients--Win 9.x PCs and CE<4.0 thin clients--timeout when
> trying to connect to a Windows 2003 Terminal Server. When DNS is disabled and
> they are given a static IP, Subnet, and Gateway, they connect fine. DHCP is
> handled by Windows 2000 Domain Controllers. AD and DNS are installed on a
> Windows 2000 Server. I'm not sure where to start with this...

Hi there... what do you mean with "DNS is disabled"?

As you may read in my post, I'm facing a similar problem, tough not all
Win95 clients get timed out...

Any clues?

 

[Damon]

Re: RDP timeout with DNS enabled

The DNS settings of the clients must be disabled when TCP/IP is configured
manually in order for them to connect to the Windows 2003 Terminal Servers.
If DNS is populated by DHCP or added manually then these older clients cannot
connect to the Windows 2003 Terminal Servers. They can, however, connect fine
to Windows 2000 Terminal Servers with DNS enabled on them.


"OxygeN" wrote:

> Damon ha scritto:
> > Hi. Our older clients--Win 9.x PCs and CE<4.0 thin clients--timeout when
> > trying to connect to a Windows 2003 Terminal Server. When DNS is disabled and
> > they are given a static IP, Subnet, and Gateway, they connect fine. DHCP is
> > handled by Windows 2000 Domain Controllers. AD and DNS are installed on a
> > Windows 2000 Server. I'm not sure where to start with this...
>
> Hi there... what do you mean with "DNS is disabled"?
>
> As you may read in my post, I'm facing a similar problem, tough not all
> Win95 clients get timed out...
>
> Any clues?
>

 

[OxygeN]

Re: RDP timeout with DNS enabled

Damon ha scritto:
> The DNS settings of the clients must be disabled when TCP/IP is configured
> manually in order for them to connect to the Windows 2003 Terminal Servers.
> If DNS is populated by DHCP or added manually then these older clients cannot
> connect to the Windows 2003 Terminal Servers. They can, however, connect fine
> to Windows 2000 Terminal Servers with DNS enabled on them.

Wow, that sounds weird! But how may these PCs be surfing the web if I
disable DNS configuration?

 

[OxygeN]

Re: RDP timeout with DNS enabled

Damon ha scritto:
> The DNS settings of the clients must be disabled when TCP/IP is configured
> manually in order for them to connect to the Windows 2003 Terminal Servers.
> If DNS is populated by DHCP or added manually then these older clients cannot
> connect to the Windows 2003 Terminal Servers. They can, however, connect fine
> to Windows 2000 Terminal Servers with DNS enabled on them.

Got my hands on one config of that Win95 client: it has "DNS disabled"!

Other suggestions to solve my issue?