> Hello,
> I have recently had to swap two machines HDD to accomadate new employee
> setups, and we run a WIN 2003 domain with a DC. I have the strangest issues
> with RDP now, even inside the network. Remote worked on both machines
> previously. Now if I type in the name for PC46, it goes to PC6, and if I
> type in PC6 it just flat refuses the connection. Suspecting an issue with
> the computer accounts in AD, I deleted their computere accounts, and unoined
> and rejoined them to the domain. Same behavior after the change. Any
> thoughts as to what's causing this? I am finding we are doing more and more
> of these swaps and I need to have remoted desktop working for all our
> machines! I originally posted this under desktop deployment group, and was advised that this sounded like a DNS issue, so I am now reposting this here.
> --
> Thanks for your time.
>
> -Kettle

--
Thanks for your time.

-Kettle

Read inline please.

In news:2FBEB763-CF53-4A09-9E75-063917964431@microsoft.com,
kettlnaut <kettlnaut@discussions.microsoft.com> typed:
>> Hello,
>> I have recently had to swap two machines HDD to accomadate new
>> employee
>> setups, and we run a WIN 2003 domain with a DC. I have the
>> strangest issues
>> with RDP now, even inside the network. Remote worked on both
>> machines
>> previously. Now if I type in the name for PC46, it goes to PC6, and
>> if I
>> type in PC6 it just flat refuses the connection. Suspecting an
>> issue with
>> the computer accounts in AD, I deleted their computere accounts, and
>> unoined
>> and rejoined them to the domain. Same behavior after the change.
>> Any
>> thoughts as to what's causing this? I am finding we are doing more
>> and more
>> of these swaps and I need to have remoted desktop working for all our
>> machines! I originally posted this under desktop deployment group,
>> and was advised that this sounded like a DNS issue, so I am now
>> reposting this here. --
>> Thanks for your time.
>>
>> -Kettle

It could very well be that PC46 still resolves to the PC6 IP address, and
that PC6 is not even registered in DNS. does nslookup pc46 return the IP
address of pc46, and does nslookup pc6 return its IP address?
Try running ipconfig /registerdns in a command prompt, to see if each
machine registers its addresses in DNS.
Check register the connection's addresses in DNS in TCP/IP properties.
Run ipconfig /all to make sure each has the connect Primary DNS suffix, it
should match the AD domain name.




--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================

Whoops, I guess I shot my mouth off in my other post (I said no one replied
to this thread). I have gotten a fair grasp on the problem as I have made
some changes in DNS that have resolved the issue, as well as found a way
around it by using IPs as host names in RDP. See my other post Titled
"Outdated Zone host records and RDP issues", at this link:

http://www.microsoft.com/communities...r=US&sloc=&p=1

That post has much more detail and I had a better grasp on the situation
when I wrote it. As for the commands, I am just starting to learn about
nslookup, and I was unaware of the switches for ipconfig listed here. I will
use these commands on some of the problematic machines and see how that info
compares to a machine that doesn't have RDP issues. Thanks for the tips
Kevin.

--

-Kettle


"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Read inline please.
>
> In news:2FBEB763-CF53-4A09-9E75-063917964431@microsoft.com,
> kettlnaut <kettlnaut@discussions.microsoft.com> typed:
> >> Hello,
> >> I have recently had to swap two machines HDD to accomadate new
> >> employee
> >> setups, and we run a WIN 2003 domain with a DC. I have the
> >> strangest issues
> >> with RDP now, even inside the network. Remote worked on both
> >> machines
> >> previously. Now if I type in the name for PC46, it goes to PC6, and
> >> if I
> >> type in PC6 it just flat refuses the connection. Suspecting an
> >> issue with
> >> the computer accounts in AD, I deleted their computere accounts, and
> >> unoined
> >> and rejoined them to the domain. Same behavior after the change.
> >> Any
> >> thoughts as to what's causing this? I am finding we are doing more
> >> and more
> >> of these swaps and I need to have remoted desktop working for all our
> >> machines! I originally posted this under desktop deployment group,
> >> and was advised that this sounded like a DNS issue, so I am now
> >> reposting this here. --
> >> Thanks for your time.
> >>
> >> -Kettle
>
> It could very well be that PC46 still resolves to the PC6 IP address, and
> that PC6 is not even registered in DNS. does nslookup pc46 return the IP
> address of pc46, and does nslookup pc6 return its IP address?
> Try running ipconfig /registerdns in a command prompt, to see if each
> machine registers its addresses in DNS.
> Check register the connection's addresses in DNS in TCP/IP properties.
> Run ipconfig /all to make sure each has the connect Primary DNS suffix, it
> should match the AD domain name.
>
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This s
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oe.com/OEBackup/Default.aspx
> ===================================
>
>
>

Read inline please.

In news:7CE620E3-8118-431C-9043-E805167E0363@microsoft.com,
kettlnaut <kettlnaut@discussions.microsoft.com> typed:
> Whoops, I guess I shot my mouth off in my other post (I said no one
> replied
> to this thread). I have gotten a fair grasp on the problem as I have
> made
> some changes in DNS that have resolved the issue, as well as found a
> way
> around it by using IPs as host names in RDP. See my other post Titled
> "Outdated Zone host records and RDP issues", at this link:
>
> http://www.microsoft.com/communities...r=US&sloc=&p=1
>
> That post has much more detail and I had a better grasp on the
> situation
> when I wrote it. As for the commands, I am just starting to learn
> about
> nslookup, and I was unaware of the switches for ipconfig listed here.
> I will
> use these commands on some of the problematic machines and see how
> that info
> compares to a machine that doesn't have RDP issues. Thanks for the
> tips
> Kevin.

I have one more tip, set up Outlook Express or some other newsreader to make
and read posts. You'll get a faster response and threads that are much
easier to follow.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================