I believe if you can't ping, then you should be able to do traceroutes too.
these 2 tools are one of the most essential tools you need to troubleshoot
network connectivity.
As far as telnet goes, tell them you need to use this tool in case you need
to test connectivity besides connecting to Telnet daemons such as SMTP,
POP3, IMAP4, LDAP...
"A.Strobel" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> 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]
