Cannot ping client, even on LAN

  • Thread starter Thread starter dan
  • Start date Start date
D

dan

I'm going to repost this issue since the my information in the other post
was getting confusing. I have one client on a small LAN that I cannot use
Remote Desktop Connection to access, even fromt the LAN, although I can
access all other clients with no problem. Upon investigation I find I cannot
ping the client from my server (Windows Server 2000) with either IP address
or computer name. If I run pathping, I see the computer name is resolved to
the IP address so DNS is working. Pathping reports 100% loss of packets on
the first hop- failure. I can ping the other way, from client to server,
just fine. I've checked the firewall setting and it appears to unblock TCP
port 3389 as it should. What am I missing? thanks.
 
Hello,

can you make a telnet IPADDRESS 3389 ?
after issuing a ping, do arp -a
do you see the mac address about this ip ?

Check properties in the computer tab of workstation that you can connect
through RDP

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"dan" <dan(removethis)@westerveltconsulting.com> wrote in message
news:uY9Me995HHA.5268@TK2MSFTNGP02.phx.gbl...
> I'm going to repost this issue since the my information in the other post
> was getting confusing. I have one client on a small LAN that I cannot use
> Remote Desktop Connection to access, even fromt the LAN, although I can
> access all other clients with no problem. Upon investigation I find I
> cannot ping the client from my server (Windows Server 2000) with either IP
> address or computer name. If I run pathping, I see the computer name is
> resolved to the IP address so DNS is working. Pathping reports 100% loss
> of packets on the first hop- failure. I can ping the other way, from
> client to server, just fine. I've checked the firewall setting and it
> appears to unblock TCP port 3389 as it should. What am I missing? thanks.
>
 
"Mathieu CHATEAU" <gollum123@free.fr> wrote in message
news:eizvh$95HHA.1208@TK2MSFTNGP05.phx.gbl...
> Hello,
>
> can you make a telnet IPADDRESS 3389 ?
> after issuing a ping, do arp -a
> do you see the mac address about this ip ?
>
> Check properties in the computer tab of workstation that you can connect
> through RDP
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message
> news:uY9Me995HHA.5268@TK2MSFTNGP02.phx.gbl...
>> I'm going to repost this issue since the my information in the other post
>> was getting confusing. I have one client on a small LAN that I cannot use
>> Remote Desktop Connection to access, even fromt the LAN, although I can
>> access all other clients with no problem. Upon investigation I find I
>> cannot ping the client from my server (Windows Server 2000) with either
>> IP address or computer name. If I run pathping, I see the computer name
>> is resolved to the IP address so DNS is working. Pathping reports 100%
>> loss of packets on the first hop- failure. I can ping the other way, from
>> client to server, just fine. I've checked the firewall setting and it
>> appears to unblock TCP port 3389 as it should. What am I missing? thanks.
>>
>
Mathieu, thanks for the quick reply! No, the telnet fails to connect.
What is the exact command for using arp? thanks.
 
Hello,

can you make a telnet IPADDRESS 3389 ?
after issuing a ping, do arp -a
do you see the mac address about this ip ?

Check properties in the computer tab of workstation that you can connect
through RDP

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"dan" <dan(removethis)@westerveltconsulting.com> wrote in message
news:u$FBoS%235HHA.4584@TK2MSFTNGP03.phx.gbl...
>
> "Mathieu CHATEAU" <gollum123@free.fr> wrote in message
> news:eizvh$95HHA.1208@TK2MSFTNGP05.phx.gbl...
>> Hello,
>>
>> can you make a telnet IPADDRESS 3389 ?
>> after issuing a ping, do arp -a
>> do you see the mac address about this ip ?
>>
>> Check properties in the computer tab of workstation that you can connect
>> through RDP
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> http://lordoftheping.blogspot.com
>>
>>
>> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message
>> news:uY9Me995HHA.5268@TK2MSFTNGP02.phx.gbl...
>>> I'm going to repost this issue since the my information in the other
>>> post was getting confusing. I have one client on a small LAN that I
>>> cannot use Remote Desktop Connection to access, even fromt the LAN,
>>> although I can access all other clients with no problem. Upon
>>> investigation I find I cannot ping the client from my server (Windows
>>> Server 2000) with either IP address or computer name. If I run pathping,
>>> I see the computer name is resolved to the IP address so DNS is working.
>>> Pathping reports 100% loss of packets on the first hop- failure. I can
>>> ping the other way, from client to server, just fine. I've checked the
>>> firewall setting and it appears to unblock TCP port 3389 as it should.
>>> What am I missing? thanks.
>>>
>>
> Mathieu, thanks for the quick reply! No, the telnet fails to connect.
> What is the exact command for using arp? thanks.
>
 
arp -a

On te workstation, check that the terminal services is started

until the telnet works, no way to get it working


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"dan" <dan(removethis)@westerveltconsulting.com> wrote in message
news:u$FBoS%235HHA.4584@TK2MSFTNGP03.phx.gbl...
>
> "Mathieu CHATEAU" <gollum123@free.fr> wrote in message
> news:eizvh$95HHA.1208@TK2MSFTNGP05.phx.gbl...
>> Hello,
>>
>> can you make a telnet IPADDRESS 3389 ?
>> after issuing a ping, do arp -a
>> do you see the mac address about this ip ?
>>
>> Check properties in the computer tab of workstation that you can connect
>> through RDP
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> http://lordoftheping.blogspot.com
>>
>>
>> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message
>> news:uY9Me995HHA.5268@TK2MSFTNGP02.phx.gbl...
>>> I'm going to repost this issue since the my information in the other
>>> post was getting confusing. I have one client on a small LAN that I
>>> cannot use Remote Desktop Connection to access, even fromt the LAN,
>>> although I can access all other clients with no problem. Upon
>>> investigation I find I cannot ping the client from my server (Windows
>>> Server 2000) with either IP address or computer name. If I run pathping,
>>> I see the computer name is resolved to the IP address so DNS is working.
>>> Pathping reports 100% loss of packets on the first hop- failure. I can
>>> ping the other way, from client to server, just fine. I've checked the
>>> firewall setting and it appears to unblock TCP port 3389 as it should.
>>> What am I missing? thanks.
>>>
>>
> Mathieu, thanks for the quick reply! No, the telnet fails to connect.
> What is the exact command for using arp? thanks.
>
 
forget, mistake from me with windows mail

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Mathieu CHATEAU" <gollum123@free.fr> wrote in message
news:E8AA0FC6-89B7-42B1-B762-D053790BC393@microsoft.com...
> Hello,
>
> can you make a telnet IPADDRESS 3389 ?
> after issuing a ping, do arp -a
> do you see the mac address about this ip ?
>
> Check properties in the computer tab of workstation that you can connect
> through RDP
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message
> news:u$FBoS%235HHA.4584@TK2MSFTNGP03.phx.gbl...
>>
>> "Mathieu CHATEAU" <gollum123@free.fr> wrote in message
>> news:eizvh$95HHA.1208@TK2MSFTNGP05.phx.gbl...
>>> Hello,
>>>
>>> can you make a telnet IPADDRESS 3389 ?
>>> after issuing a ping, do arp -a
>>> do you see the mac address about this ip ?
>>>
>>> Check properties in the computer tab of workstation that you can connect
>>> through RDP
>>>
>>> --
>>> Cordialement,
>>> Mathieu CHATEAU
>>> http://lordoftheping.blogspot.com
>>>
>>>
>>> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message
>>> news:uY9Me995HHA.5268@TK2MSFTNGP02.phx.gbl...
>>>> I'm going to repost this issue since the my information in the other
>>>> post was getting confusing. I have one client on a small LAN that I
>>>> cannot use Remote Desktop Connection to access, even fromt the LAN,
>>>> although I can access all other clients with no problem. Upon
>>>> investigation I find I cannot ping the client from my server (Windows
>>>> Server 2000) with either IP address or computer name. If I run
>>>> pathping, I see the computer name is resolved to the IP address so DNS
>>>> is working. Pathping reports 100% loss of packets on the first hop-
>>>> failure. I can ping the other way, from client to server, just fine.
>>>> I've checked the firewall setting and it appears to unblock TCP port
>>>> 3389 as it should. What am I missing? thanks.
>>>>
>>>
>> Mathieu, thanks for the quick reply! No, the telnet fails to connect.
>> What is the exact command for using arp? thanks.
>>
>
 
"Mathieu CHATEAU" <gollum123@free.fr> wrote in message
news:49E9A5E5-3447-48B8-8118-CE1ADA9C4B21@microsoft.com...
> arp -a
>
> On te workstation, check that the terminal services is started
>
> until the telnet works, no way to get it working
>
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message
> news:u$FBoS%235HHA.4584@TK2MSFTNGP03.phx.gbl...
>>
>> "Mathieu CHATEAU" <gollum123@free.fr> wrote in message
>> news:eizvh$95HHA.1208@TK2MSFTNGP05.phx.gbl...
>>> Hello,
>>>
>>> can you make a telnet IPADDRESS 3389 ?
>>> after issuing a ping, do arp -a
>>> do you see the mac address about this ip ?
>>>
>>> Check properties in the computer tab of workstation that you can connect
>>> through RDP
>>>
>>> --
>>> Cordialement,
>>> Mathieu CHATEAU
>>> http://lordoftheping.blogspot.com
>>>
>>>
>>> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message
>>> news:uY9Me995HHA.5268@TK2MSFTNGP02.phx.gbl...
>>>> I'm going to repost this issue since the my information in the other
>>>> post was getting confusing. I have one client on a small LAN that I
>>>> cannot use Remote Desktop Connection to access, even fromt the LAN,
>>>> although I can access all other clients with no problem. Upon
>>>> investigation I find I cannot ping the client from my server (Windows
>>>> Server 2000) with either IP address or computer name. If I run
>>>> pathping, I see the computer name is resolved to the IP address so DNS
>>>> is working. Pathping reports 100% loss of packets on the first hop-
>>>> failure. I can ping the other way, from client to server, just fine.
>>>> I've checked the firewall setting and it appears to unblock TCP port
>>>> 3389 as it should. What am I missing? thanks.
>>>>
>>>
>> Mathieu, thanks for the quick reply! No, the telnet fails to connect.
>> What is the exact command for using arp? thanks.
>>

Thanks I'll check that when I get on site to look at the client. The arp -a
does not show the client's IP or MAC address.
 
if just after a ping, you can't get the arp (or 00-00-00-00...) then it's
not alive, at least on this ip

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"dan" <dan(removethis)@westerveltconsulting.com> wrote in message
news:u6a9Gj%235HHA.3740@TK2MSFTNGP02.phx.gbl...
>
> "Mathieu CHATEAU" <gollum123@free.fr> wrote in message
> news:49E9A5E5-3447-48B8-8118-CE1ADA9C4B21@microsoft.com...
>> arp -a
>>
>> On te workstation, check that the terminal services is started
>>
>> until the telnet works, no way to get it working
>>
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> http://lordoftheping.blogspot.com
>>
>>
>> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message
>> news:u$FBoS%235HHA.4584@TK2MSFTNGP03.phx.gbl...
>>>
>>> "Mathieu CHATEAU" <gollum123@free.fr> wrote in message
>>> news:eizvh$95HHA.1208@TK2MSFTNGP05.phx.gbl...
>>>> Hello,
>>>>
>>>> can you make a telnet IPADDRESS 3389 ?
>>>> after issuing a ping, do arp -a
>>>> do you see the mac address about this ip ?
>>>>
>>>> Check properties in the computer tab of workstation that you can
>>>> connect through RDP
>>>>
>>>> --
>>>> Cordialement,
>>>> Mathieu CHATEAU
>>>> http://lordoftheping.blogspot.com
>>>>
>>>>
>>>> "dan" <dan(removethis)@westerveltconsulting.com> wrote in message
>>>> news:uY9Me995HHA.5268@TK2MSFTNGP02.phx.gbl...
>>>>> I'm going to repost this issue since the my information in the other
>>>>> post was getting confusing. I have one client on a small LAN that I
>>>>> cannot use Remote Desktop Connection to access, even fromt the LAN,
>>>>> although I can access all other clients with no problem. Upon
>>>>> investigation I find I cannot ping the client from my server (Windows
>>>>> Server 2000) with either IP address or computer name. If I run
>>>>> pathping, I see the computer name is resolved to the IP address so DNS
>>>>> is working. Pathping reports 100% loss of packets on the first hop-
>>>>> failure. I can ping the other way, from client to server, just fine.
>>>>> I've checked the firewall setting and it appears to unblock TCP port
>>>>> 3389 as it should. What am I missing? thanks.
>>>>>
>>>>
>>> Mathieu, thanks for the quick reply! No, the telnet fails to connect.
>>> What is the exact command for using arp? thanks.
>>>
>
> Thanks I'll check that when I get on site to look at the client. The
> arp -a does not show the client's IP or MAC address.
>
 
hi,
what subnet mask do you have set on client and on server? Do you have set
any TCP filtering on client? what firewall do you use on client machine -
some firewalls have the abbillity to mark some IP addresses as "no access".
--
Dragos CAMARA
MCSA Windows 2003 server


"dan" wrote:

> I'm going to repost this issue since the my information in the other post
> was getting confusing. I have one client on a small LAN that I cannot use
> Remote Desktop Connection to access, even fromt the LAN, although I can
> access all other clients with no problem. Upon investigation I find I cannot
> ping the client from my server (Windows Server 2000) with either IP address
> or computer name. If I run pathping, I see the computer name is resolved to
> the IP address so DNS is working. Pathping reports 100% loss of packets on
> the first hop- failure. I can ping the other way, from client to server,
> just fine. I've checked the firewall setting and it appears to unblock TCP
> port 3389 as it should. What am I missing? thanks.
>
>
>
 
"Dragos CAMARA" <dragos_c@remove-this.hotmail.com> wrote in message
news:9F593074-3544-4CFE-900F-02EB71E230F9@microsoft.com...
> hi,
> what subnet mask do you have set on client and on server? Do you have set
> any TCP filtering on client? what firewall do you use on client machine -
> some firewalls have the abbillity to mark some IP addresses as "no
> access".
> --
> Dragos CAMARA
> MCSA Windows 2003 server
>
>
> "dan" wrote:
>
>> I'm going to repost this issue since the my information in the other post
>> was getting confusing. I have one client on a small LAN that I cannot use
>> Remote Desktop Connection to access, even fromt the LAN, although I can
>> access all other clients with no problem. Upon investigation I find I
>> cannot
>> ping the client from my server (Windows Server 2000) with either IP
>> address
>> or computer name. If I run pathping, I see the computer name is resolved
>> to
>> the IP address so DNS is working. Pathping reports 100% loss of packets
>> on
>> the first hop- failure. I can ping the other way, from client to server,
>> just fine. I've checked the firewall setting and it appears to unblock
>> TCP
>> port 3389 as it should. What am I missing? thanks.
>>
>>
>>
Dragos, it's the standard /24 subnet mask, and the Firewall is XP SP2
version. I'm going to check the firewall settings again (maybe even turn the
firewall off temporarily while I try to figure this out, but I've got to be
on site obviously, since I can't remote in....
 

Similar threads

AWS
September 2023 - Microsoft 365 US Public Sector Roadmap Newsletter
Replies
0
Views
167
AWS
AWS
AWS
Seamless update experience for organizations on Windows 11
Replies
1
Views
384
Tony D
Tony D
AWS
Get the most out of expedited Windows quality updates
Replies
0
Views
174
AWS
AWS
AWS
Tarrask malware uses scheduled tasks for defense evasion
Replies
0
Views
249
AWS
AWS
AWS
The many lives of BlackCat ransomware
Replies
0
Views
274
AWS
AWS
Back
Top