Resolving Computer Names for RDC

Hi, I used to be able to connect via remote desktop between computers at work
using their computer name, but now I can only do it via IP. This is a problem
on a dhcp network. The computers are listening on 3389, and I can connect via
ip. Their names just wont resolve. This seems to be a familir problem with
the new terminal serives 6.0. Help?

Can you ping remote computer by name? If not, please post back with the
results of ipconfig /all on both computers.

--
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
"Brent" <Brent@discussions.microsoft.com> wrote in message
news:6B52C045-7AE0-4D36-901E-D7DF12FAAAD1@microsoft.com...
> Hi, I used to be able to connect via remote desktop between computers at
> work
> using their computer name, but now I can only do it via IP. This is a
> problem
> on a dhcp network. The computers are listening on 3389, and I can connect
> via
> ip. Their names just wont resolve. This seems to be a familir problem with
> the new terminal serives 6.0. Help?

Yes, I can ping between both computers. ipconfig shows both as Node Type
unknown, NetBIOS is on.

"Robert L. (MS-MVP)" wrote:

> Can you ping remote computer by name? If not, please post back with the
> results of ipconfig /all on both computers.
>
> --
> 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
> "Brent" <Brent@discussions.microsoft.com> wrote in message
> news:6B52C045-7AE0-4D36-901E-D7DF12FAAAD1@microsoft.com...
> > Hi, I used to be able to connect via remote desktop between computers at
> > work
> > using their computer name, but now I can only do it via IP. This is a
> > problem
> > on a dhcp network. The computers are listening on 3389, and I can connect
> > via
> > ip. Their names just wont resolve. This seems to be a familir problem with
> > the new terminal serives 6.0. Help?
>
>