On Fri, 27 Apr 2007 16:46:24 -0400, Wayne Driscoll <[EMAIL PROTECTED]> wrote:
>Ok, time for me to spend some time on the soap box. What is the >TECHNICAL reason for not allowing the Mainframe to access the network? >I don't understand this at all. Every PC in your company probably can >access the internet, allowing employees to spend time browsing the web, >yet the mainframe can't be connected to the internet to allow for you to >QUICKLY get maintenance? ... Sorry to be late to a "sopbox" sub-thread ... especially one on a favorite topic of mine. Wayne must have limited experience with corporate paranoia. Every PC in our company probably DOES have access to the internet, but only through a proxy and only for well-known HTTP ports. No FTP. No news servers. No anything but HTTP & HTTPS. Some of use have access to an unathorized wireless access point that is not on our LAN, but we have software that disables wireless communication if an ethernet connection is active. And all of the PCs are "locked down" so that we cannot change such things. (All software is downloaded from a corporate server.) We can freely FTP between mainframes and PCs but have to go "off LAN" to transfer to/from remote sites. It's a royal pain! Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
