G*2MyPC

If said program would make it easier for me to connect a heavy duty UNIX based graphics production printer on a large network to an NT based PC on a private network that is buried within that larger network, I might consider it for a few moments.But outside of that, I would do my best to make sure that I have enough horror stories about such connections to make anybody feel very nervous about allowing such activities.

If the horror stories don't work, I'd consider opening up the use of such activities to those people who complain the most about needing it. But I would also make sure that they are aware that I would be monitoring security on their systems and be tracking breeches and the amount of time spent handling them.

The only access to our company network from outside the company premises is by Dial-Up Network Server (running on a Windows 98 machine). The modem is on an unlisted number, and uses CLI (caller line identification) as well as password checking to authenticate access. Only two calling numbers are authorised to allow 24/7 access and they are both mine! Should anyone else in the company need to access data on the network, say, if they have shot off to a meeting somewhere and left their Powerpoint presentation at the office, then they can call the office and we'll e-mail the files to them. Other than me in my capacity as software engineer and Admin, no one else can use the system outside office hours...end of story!