When pinging to a device for the first time the first ping times out while
the last network device (router) arps for the hardware address of the host
(server). (I'm assuming that the server is at a remote location from you.)
The router should then maintain the ip to MAC translation in its arp table
for a specified time. The arp table timeout (due to inactivity) on Cisco
routers is four hours. I think that we can assume that the server is busy
enough that it should maintain its entry in the routers arp cache. The
router seems ok because it works fine with other servers - hopefully on the
same subnet. That points to the server. I believe that you posted this
question the other day and indicated then that the problem had just started
happening. The question then is "Who messed with the server recently?" and
"What did they do?" What configuration problem on a host computer can
disallow a router from maintaining its entry in an arp cache - even though
the host is active? I can't state a definitive answer for that -- but I'd
sure want to check the subnet mask and default gateway values on that
server.
Please post your solution to the list.

> -----Original Message-----
> From: Sim, CT (Chee Tong) [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 19, 2002 12:46 AM
> To: [EMAIL PROTECTED]
> Subject: can't map before ping first? [7:53599]
> 
> 
> I have a server which always has problem mapping to other PC 
> across the WAN
> (other branch network).  But it works after I ping to 
> overseas PC (as shown
> below).  Do you know what might be the problem.  My other 
> server don't have
> this problem and it is still the same after I switch it to 
> another switch
> port.
> 
>  
> 
> C:\>net use * \\w2k01\c$
> 
> System error 53 has occurred.
> 
>  
> 
> The network path was not found.
> 
>  
> 
>  
> 
> C:\>net use * \\100.100.100.19\c$
> 
> System error 53 has occurred.
> 
>  
> 
> The network path was not found.
> 
>  
> 
>  
> 
> C:\>ping w2k01
> 
>  
> 
> Pinging w2k01 [100.100.100.19] with 32 bytes of data:
> 
>  
> 
> Request timed out.
> 
> Reply from 100.100.100.19: bytes=32 time=109ms TTL=124
> 
> Reply from 100.100.100.19: bytes=32 time=110ms TTL=124
> 
> Reply from 100.100.100.19: bytes=32 time=110ms TTL=124
> 
>  
> 
> C:\>net use * \\100.100.100.19\c$
> 
> Drive G: is now connected to \\100.100.100.19\c$.
> 
>  
> 
> The command completed successfully.
> 
> 
> ==================================================================
> De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
> is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
> onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en 
> de afzender direct te informeren door het bericht te retourneren. 
> ==================================================================
> The information contained in this message may be confidential 
> and is intended to be exclusively for the addressee. Should you 
> receive this message unintentionally, please do not use the contents 
> herein and notify the sender immediately by return e-mail.
> 
> 
> ==================================================================




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=53623&t=53599
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to