Remote Desktop

Hi

Often I need to wait quite a long time until I can connect via remote
desktop to a started machine within my domain. Even when the log-on dialog is
ready, rdp-connection needs some more time until it can connect. All machines
are whithin the same office.
Is this just normal, due to the dns-service installed on the dc which needs
some additional seconds to resolve the computername?
Is there a method (dns?) to shorten this initial waiting-time?

Patrick

"Patrick D." <> wrote in message
news:EDB94970-C78C-42FB-8D99-...
> Hi
>
> Often I need to wait quite a long time until I can connect via remote
> desktop to a started machine within my domain. Even when the log-on dialog
> is
> ready, rdp-connection needs some more time until it can connect. All
> machines
> are whithin the same office.
> Is this just normal, due to the dns-service installed on the dc which
> needs
> some additional seconds to resolve the computername?
> Is there a method (dns?) to shorten this initial waiting-time?
>
> Patrick


That would depend on your configuration. If all workstations and servers are
only using the internal DNS server (assuming your DCs), you should not see
any kind of delay with resolution. Now if the workstations are using the
internal and ISP (or some other DNS server that does not host the internal
AD zone or have a reference to it - stubs, secondary, or conditional
forwarder), then I can see there may be a delay.

Another factor is if the internal domain name is a single label name (DNS
domain name being DOMAIN vs domain.local). If this is the case, numerous
resolution problems will occur.

A multihomed DC or the server you are trying to connect to, can also be an
issue.

If you can post an unedited ipconfig /all of a workstation you are trying to
connect from, and a sample DC, as well as if you see any eventID# errors in
the event log, that would help towards a diagnosis.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

hi sir iam siraj patel



Ace Fekay [MVP-DS, MCT] wrote:

That would depend on your configuration.
14-Feb-10

That would depend on your configuration. If all workstations and servers are
only using the internal DNS server (assuming your DCs), you should not see
any kind of delay with resolution. Now if the workstations are using the
internal and ISP (or some other DNS server that does not host the internal
AD zone or have a reference to it - stubs, secondary, or conditional
forwarder), then I can see there may be a delay.

Another factor is if the internal domain name is a single label name (DNS
domain name being DOMAIN vs domain.local). If this is the case, numerous
resolution problems will occur.

A multihomed DC or the server you are trying to connect to, can also be an
issue.

If you can post an unedited ipconfig /all of a workstation you are trying to
connect from, and a sample DC, as well as if you see any eventID# errors in
the event log, that would help towards a diagnosis.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

Previous Posts In This Thread:


Submitted via EggHeadCafe - Software Developer Portal of Choice
Dr. Dotnetsky's Cool .Net Tips and Tricks No. 26
http://www.eggheadcafe.com/tutorials...-cool-net.aspx

"siraj patel" wrote in message
news:2010225101358sirajpatel.networkengg2010@gmail .com...

I'm sorry, I don't understand your response. I saw your name. Was there
additional information contributing to the original poster's issues in your
post that perhaps may have been truncated?

Ace


> hi sir iam siraj patel
>
>
>
> Ace Fekay [MVP-DS, MCT] wrote:
>
> That would depend on your configuration.
> 14-Feb-10
>
> That would depend on your configuration. If all workstations and servers
> are
> only using the internal DNS server (assuming your DCs), you should not see
> any kind of delay with resolution. Now if the workstations are using the
> internal and ISP (or some other DNS server that does not host the internal
> AD zone or have a reference to it - stubs, secondary, or conditional
> forwarder), then I can see there may be a delay.
>
> Another factor is if the internal domain name is a single label name (DNS
> domain name being DOMAIN vs domain.local). If this is the case, numerous
> resolution problems will occur.
>
> A multihomed DC or the server you are trying to connect to, can also be an
> issue.
>
> If you can post an unedited ipconfig /all of a workstation you are trying
> to
> connect from, and a sample DC, as well as if you see any eventID# errors
> in
> the event log, that would help towards a diagnosis.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among
> responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
> MCSA 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
> Microsoft MVP - Directory Services
>
> If you feel this is an urgent issue and require immediate assistance,
> please
> contact Microsoft PSS directly. Please check http://support.microsoft.com
> for regional support phone numbers.
>
> Previous Posts In This Thread:
>
>
> Submitted via EggHeadCafe - Software Developer Portal of Choice
> Dr. Dotnetsky's Cool .Net Tips and Tricks No. 26
> http://www.eggheadcafe.com/tutorials...-cool-net.aspx