Are you responsible for traffic leaving your network? If so, how else
would you test connectivity to ensure your network was working
properly. Pinging or telneting in is one thing, restricting pings or
telnets out is the work of an NT moron that doesn't understand the
protocols.
andy
On 3 Jan 2001, A.Strobel wrote:
> Working for an enterperise has its disadvantages. Based on the new policy, now
> I (network engineer) am unable to ping the outside world nor telnet to the
> outside world.
>
> Although my main job is taking care of Cisco gear inside the enterprise, I
> hate the fact that someone with a half brain sitting at a proxy server
> dictates me what I can do and what I can not do.
>
> I might have a chance in removing these restrictions if I can justify that I
> need to ping or telnet the ouside world.
> Can you guys think of any justification?
>
> TIA,
> A. Strobel
>
>
>
>
>
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.amexmail.com/?A=1
>
> _________________________________
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
