Guest dan Posted August 23, 2007 Posted August 23, 2007 I'm trying to use Remote Desktop Connection to connect to a client (from the internet, not internal). If I use the client's IP address I succeed, but if I use the client's computer name I fail. Upon further investigation, if I remote into my server first (Windows Server 2000), then try to ping the client, it fails whether I use IP address or computer name. If I look in the forwarding zone of DNS on the server, the record correctly maps 192.168.1.212 to RWWS1, which is the client I'm trying to reach. Where should I look for the root cause of my problem (not being able to RDC to the client with the computer name). The client functions perfectly on the network by the way, this is just a RDC problem. TIA.
Guest Coraleigh Miller Posted August 23, 2007 Posted August 23, 2007 Re: Client OK but can't ping Hi Dan, You arent trying to RDP with the client's internal ip are you? :-) Do you have an externally registered domain name for this company? If yes..check that whoever hosts the external DNS mapping has it correctly set to the external ip with the registered domain name, if that is it has ever worked via ext dns. You basically need a record set which points the external ip to the registered domain name of your clients server which runs the RDC. There are many companies who host dns and domain registration, a google search will find some. Alternatively you could host the ext dns via the clients server but that wold mean opening up more ports and additional configuration, and you would still need a registered domain name. This is a great site for DNS tools to help you troubleshoot. http://www.dnsstuff.com/ Coraleigh Miller "dan" <dan(removethis)@westerveltconsulting.com> wrote in message news:u3QbWed5HHA.5184@TK2MSFTNGP03.phx.gbl... > I'm trying to use Remote Desktop Connection to connect to a client (from > the internet, not internal). If I use the client's IP address I succeed, > but if I use the client's computer name I fail. Upon further > investigation, if I remote into my server first (Windows Server 2000), > then try to ping the client, it fails whether I use IP address or computer > name. If I look in the forwarding zone of DNS on the server, the record > correctly maps 192.168.1.212 to RWWS1, which is the client I'm trying to > reach. Where should I look for the root cause of my problem (not being > able to RDC to the client with the computer name). The client functions > perfectly on the network by the way, this is just a RDC problem. TIA. >
Guest Coraleigh Miller Posted August 23, 2007 Posted August 23, 2007 Re: Client OK but can't ping lol, scrap my first sentence, just re-read your post again. :-) Coraleigh "dan" <dan(removethis)@westerveltconsulting.com> wrote in message news:u3QbWed5HHA.5184@TK2MSFTNGP03.phx.gbl... > I'm trying to use Remote Desktop Connection to connect to a client (from > the internet, not internal). If I use the client's IP address I succeed, > but if I use the client's computer name I fail. Upon further > investigation, if I remote into my server first (Windows Server 2000), > then try to ping the client, it fails whether I use IP address or computer > name. If I look in the forwarding zone of DNS on the server, the record > correctly maps 192.168.1.212 to RWWS1, which is the client I'm trying to > reach. Where should I look for the root cause of my problem (not being > able to RDC to the client with the computer name). The client functions > perfectly on the network by the way, this is just a RDC problem. TIA. >
Guest dan Posted August 24, 2007 Posted August 24, 2007 Re: Client OK but can't ping I see that my post is a little confusing. When I encounter my problem, I already have a secure connection to my network via a Sonicwall SSL-VPN. My problem is with this specific client- I can easily RDC to any other of the clients on the network using their computer name. Since I can access the client using the IP address, it would appear to be a DNS problem, but why can't I ping either the IP address or the computer name from my server, and again, the forward zone correctly maps the IP to name? "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message news:unzdMsd5HHA.2108@TK2MSFTNGP02.phx.gbl... > lol, scrap my first sentence, just re-read your post again. :-) > > Coraleigh > > "dan" <dan(removethis)@westerveltconsulting.com> wrote in message > news:u3QbWed5HHA.5184@TK2MSFTNGP03.phx.gbl... >> I'm trying to use Remote Desktop Connection to connect to a client (from >> the internet, not internal). If I use the client's IP address I succeed, >> but if I use the client's computer name I fail. Upon further >> investigation, if I remote into my server first (Windows Server 2000), >> then try to ping the client, it fails whether I use IP address or >> computer name. If I look in the forwarding zone of DNS on the server, the >> record correctly maps 192.168.1.212 to RWWS1, which is the client I'm >> trying to reach. Where should I look for the root cause of my problem >> (not being able to RDC to the client with the computer name). The client >> functions perfectly on the network by the way, this is just a RDC >> problem. TIA. >> > >
Guest Coraleigh Miller Posted August 24, 2007 Posted August 24, 2007 Re: Client OK but can't ping Hi Dan, Ahh ok thank you for the additional info. :-) Since the issue symptoms are only in connecting with this client, I would start troubleshooting there. Have someone, sitting at the pc, confirm that it is configured set to dhcp with no static entries(assuming that that is how it is supposed to be). Have them do an ipconfig /flushdns as well as an ipconfig /release, and then you manually delete the dns record for their pc off the server. Also flush the DNS cache of the DNS server. Have them reboot and then confirm they picked up an ip, also check that there is a new dns entry on the server for them, if not then they should do an ipconfig /renew and a ipconfig /registerdns. Lets start with that and see what happens. Coraleigh Miller "dan" <dan(removethis)@westerveltconsulting.com> wrote in message news:efl1fSe5HHA.5316@TK2MSFTNGP04.phx.gbl... >I see that my post is a little confusing. When I encounter my problem, I >already have a secure connection to my network via a Sonicwall SSL-VPN. My >problem is with this specific client- I can easily RDC to any other of the >clients on the network using their computer name. Since I can access the >client using the IP address, it would appear to be a DNS problem, but why >can't I ping either the IP address or the computer name from my server, and >again, the forward zone correctly maps the IP to name? > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message > news:unzdMsd5HHA.2108@TK2MSFTNGP02.phx.gbl... >> lol, scrap my first sentence, just re-read your post again. :-) >> >> Coraleigh >> >> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message >> news:u3QbWed5HHA.5184@TK2MSFTNGP03.phx.gbl... >>> I'm trying to use Remote Desktop Connection to connect to a client (from >>> the internet, not internal). If I use the client's IP address I succeed, >>> but if I use the client's computer name I fail. Upon further >>> investigation, if I remote into my server first (Windows Server 2000), >>> then try to ping the client, it fails whether I use IP address or >>> computer name. If I look in the forwarding zone of DNS on the server, >>> the record correctly maps 192.168.1.212 to RWWS1, which is the client >>> I'm trying to reach. Where should I look for the root cause of my >>> problem (not being able to RDC to the client with the computer name). >>> The client functions perfectly on the network by the way, this is just a >>> RDC problem. TIA. >>> >> >> > >
Guest Coraleigh Miller Posted August 24, 2007 Posted August 24, 2007 Re: Client OK but can't ping Another question.. do you happen to use vlan in this network? Also try doing a pathping to this pc and we can see where it fails. Coraleigh "dan" <dan(removethis)@westerveltconsulting.com> wrote in message news:efl1fSe5HHA.5316@TK2MSFTNGP04.phx.gbl... >I see that my post is a little confusing. When I encounter my problem, I >already have a secure connection to my network via a Sonicwall SSL-VPN. My >problem is with this specific client- I can easily RDC to any other of the >clients on the network using their computer name. Since I can access the >client using the IP address, it would appear to be a DNS problem, but why >can't I ping either the IP address or the computer name from my server, and >again, the forward zone correctly maps the IP to name? > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message > news:unzdMsd5HHA.2108@TK2MSFTNGP02.phx.gbl... >> lol, scrap my first sentence, just re-read your post again. :-) >> >> Coraleigh >> >> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message >> news:u3QbWed5HHA.5184@TK2MSFTNGP03.phx.gbl... >>> I'm trying to use Remote Desktop Connection to connect to a client (from >>> the internet, not internal). If I use the client's IP address I succeed, >>> but if I use the client's computer name I fail. Upon further >>> investigation, if I remote into my server first (Windows Server 2000), >>> then try to ping the client, it fails whether I use IP address or >>> computer name. If I look in the forwarding zone of DNS on the server, >>> the record correctly maps 192.168.1.212 to RWWS1, which is the client >>> I'm trying to reach. Where should I look for the root cause of my >>> problem (not being able to RDC to the client with the computer name). >>> The client functions perfectly on the network by the way, this is just a >>> RDC problem. TIA. >>> >> >> > >
Guest Coraleigh Miller Posted August 24, 2007 Posted August 24, 2007 Re: Client OK but can't ping Also you could try changing the switch port the pc is on. Coraleigh Miller "dan" <dan(removethis)@westerveltconsulting.com> wrote in message news:efl1fSe5HHA.5316@TK2MSFTNGP04.phx.gbl... >I see that my post is a little confusing. When I encounter my problem, I >already have a secure connection to my network via a Sonicwall SSL-VPN. My >problem is with this specific client- I can easily RDC to any other of the >clients on the network using their computer name. Since I can access the >client using the IP address, it would appear to be a DNS problem, but why >can't I ping either the IP address or the computer name from my server, and >again, the forward zone correctly maps the IP to name? > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message > news:unzdMsd5HHA.2108@TK2MSFTNGP02.phx.gbl... >> lol, scrap my first sentence, just re-read your post again. :-) >> >> Coraleigh >> >> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message >> news:u3QbWed5HHA.5184@TK2MSFTNGP03.phx.gbl... >>> I'm trying to use Remote Desktop Connection to connect to a client (from >>> the internet, not internal). If I use the client's IP address I succeed, >>> but if I use the client's computer name I fail. Upon further >>> investigation, if I remote into my server first (Windows Server 2000), >>> then try to ping the client, it fails whether I use IP address or >>> computer name. If I look in the forwarding zone of DNS on the server, >>> the record correctly maps 192.168.1.212 to RWWS1, which is the client >>> I'm trying to reach. Where should I look for the root cause of my >>> problem (not being able to RDC to the client with the computer name). >>> The client functions perfectly on the network by the way, this is just a >>> RDC problem. TIA. >>> >> >> > >
Guest Dragos CAMARA Posted August 24, 2007 Posted August 24, 2007 Re: Client OK but can't ping hi, when you ping -a IP it's show the name of computer, on ping by name it shows the IP or is a error? check the status of dns, the registration of the computer and run a clear cache on DNS servers. also check on the server and on that client the "route print" to see what routing table do you have and may be that IP is routed elsewhere. -- Dragos CAMARA MCSA Windows 2003 server "dan" wrote: > I see that my post is a little confusing. When I encounter my problem, I > already have a secure connection to my network via a Sonicwall SSL-VPN. My > problem is with this specific client- I can easily RDC to any other of the > clients on the network using their computer name. Since I can access the > client using the IP address, it would appear to be a DNS problem, but why > can't I ping either the IP address or the computer name from my server, and > again, the forward zone correctly maps the IP to name? > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message > news:unzdMsd5HHA.2108@TK2MSFTNGP02.phx.gbl... > > lol, scrap my first sentence, just re-read your post again. :-) > > > > Coraleigh > > > > "dan" <dan(removethis)@westerveltconsulting.com> wrote in message > > news:u3QbWed5HHA.5184@TK2MSFTNGP03.phx.gbl... > >> I'm trying to use Remote Desktop Connection to connect to a client (from > >> the internet, not internal). If I use the client's IP address I succeed, > >> but if I use the client's computer name I fail. Upon further > >> investigation, if I remote into my server first (Windows Server 2000), > >> then try to ping the client, it fails whether I use IP address or > >> computer name. If I look in the forwarding zone of DNS on the server, the > >> record correctly maps 192.168.1.212 to RWWS1, which is the client I'm > >> trying to reach. Where should I look for the root cause of my problem > >> (not being able to RDC to the client with the computer name). The client > >> functions perfectly on the network by the way, this is just a RDC > >> problem. TIA. > >> > > > > > > >
Guest dan Posted August 24, 2007 Posted August 24, 2007 Re: Client OK but can't ping Thanks I'll give these a try. "dan" <dan(removethis)@westerveltconsulting.com> wrote in message news:efl1fSe5HHA.5316@TK2MSFTNGP04.phx.gbl... >I see that my post is a little confusing. When I encounter my problem, I >already have a secure connection to my network via a Sonicwall SSL-VPN. My >problem is with this specific client- I can easily RDC to any other of the >clients on the network using their computer name. Since I can access the >client using the IP address, it would appear to be a DNS problem, but why >can't I ping either the IP address or the computer name from my server, and >again, the forward zone correctly maps the IP to name? > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message > news:unzdMsd5HHA.2108@TK2MSFTNGP02.phx.gbl... >> lol, scrap my first sentence, just re-read your post again. :-) >> >> Coraleigh >> >> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message >> news:u3QbWed5HHA.5184@TK2MSFTNGP03.phx.gbl... >>> I'm trying to use Remote Desktop Connection to connect to a client (from >>> the internet, not internal). If I use the client's IP address I succeed, >>> but if I use the client's computer name I fail. Upon further >>> investigation, if I remote into my server first (Windows Server 2000), >>> then try to ping the client, it fails whether I use IP address or >>> computer name. If I look in the forwarding zone of DNS on the server, >>> the record correctly maps 192.168.1.212 to RWWS1, which is the client >>> I'm trying to reach. Where should I look for the root cause of my >>> problem (not being able to RDC to the client with the computer name). >>> The client functions perfectly on the network by the way, this is just a >>> RDC problem. TIA. >>> >> >> > >
Recommended Posts