Discussion Locked

Use of Instant Messaging as a support tool

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am looking for an easy way of communicating with desktops at work from home. Some of the desktops I need to contact are *insecure* and so my initial idea of an instant messaging package are frowned upon by my superiors.

The problems are as follows:

1. Security of sending and reciveing files (although this is a required feature, we need some way of ensuring the security)
2. We don't want to open these unsecure desktops and allow internet access (in truth, these desktops can access the internet, but we have fooled them (the users) into thinking they can't)
3. We don't want the users to be allowed to spend all day and night chatting to thier friends with IM instead of working

We do have a firewall which controls all the traffic in and out of the building. What I envisage is some sort of 'managed' IM package which I can control who they talk to and what they send (mainly files in and out).

Any ideas?

6 replies

by lumberjack

connecting securely to a PC for file transfer and admin- have you tried Norton's PC Anywhere?
For desktop sharing - can use MS Net Meeting

restricting files being sent etc - if using exchange can be done there; or for outlook there is Lookout!

by scarecrow71

I don't want to 'take control' of the users PC (although it would be a useful option), rather I would like to be able to talk to them and give them instructions. (before you say it, a lot of these workstations are nowhere near a phone!)

The problem I have found with PC Anywhere and the like is that they are just about useable on a DSL connection, heaven forbid you should try it on a dialup!!

by voldar

Hi there. You don't specify what environment you have, so I suppose it's a W2K based one and I suggest you some base-lines to take into consideration:
1. - Security - install a VPN server (RRAS) and create policies/rights to the outdors users to what computer to connect to. Implement L2TP with IPsec so that only authorized users can connect and the data flow (in and out) to be securized. Use strong NTFS permissions and don't let anything else than needed to be accessed.
2.& 3. - Block the Internet Explorer or any other program for internet browsing by using the GPO policies. Also, you can block the port 80 (http), 20 and 21 (ftp). Deny the use of IM also. You can do that very simple if you have an AD structure implemented.

3. Create e-mail accounts so that they can chat/"share" documents by using e-mail. If you have an e-mail antivirus you'll be much confident about your network security to viruses attacks.

by voldar

Hi there. You don't specify what environment you have, so I suppose it's a W2K based one and I suggest you some base-lines to take into consideration:
1. - Security - install a VPN server (RRAS) and create policies/rights to the outdors users to what computer to connect to. Implement L2TP with IPsec so that only authorized users can connect and the data flow (in and out) to be securized. Use strong NTFS permissions and don't let anything else than needed to be accessed.
2.& 3. - Block the Internet Explorer or any other program for internet browsing by using the GPO policies. Also, you can block the port 80 (http), 20 and 21 (ftp). Deny the use of IM also. You can do that very simple if you have an AD structure implemented.

3. Create e-mail accounts so that they can chat/"share" documents by using e-mail. If you have an e-mail antivirus you'll be much confident about your network security to viruses attacks.

by scarecrow71

I'm not sure you understood my need.

The situation is that I have unskilled people operating machinery which is controlled by a W2K pc. There are no phones near the PC's. When I get a phone call saying that the application has faulted in some way, I tell them to go to the pc and write the error (for example) down and read it to me. They come back with and say "it says something like...". I give them a diagnostic test to do, they go away. When they come back I get "it says something like..." and so the cycle begins again.

If I can cut out the walk between the shop floor and the phone in the office, perhaps the error messages will be more detailed. I will also get faster results of diagnostic tests.

That is why I initially thought of IM. The question of securing the environment is not too much of a problem, but I cannot easily allow IM without potentially opening up other 'doors'. It weould be ideal if there was some managed IM package which allowed me to set permnissions, and control who they spoke to, and who spoke to them, and what files they sent in and out.

'Total control' packages like PC Anywhere are overkill.

by cirodejah

1- What kind of MIS connection do you have going to the server? You said a firewall at the server (WIN2K), you also mentioned not preferring Symantec PCAnywhere going over dial-up since even DSL is somewhat "unuseable"?.
2- You mention the desktops having internet capability...I assume through the server?
3- What kind of Firewall are you talking about...software and/or hardware?
4- What OS at the desktops and what hardware specs? This since you say that PCAnywhere would be overkill.
5- So you have an Exchange server? What version is it? The kind of IM you would want works at the intranet level with minimum W2k and Exchange Server2K

I have a couple of NT servers at the office and a DSL connection at home...all works fine connecting with PCAnywhere to any of my WIN98 workstations or my NT4 servers. Chatting at the office and controlling that? Use e-mail accounts
File sharing at the office and controlling that? Use e-mail for up to 2MB sizes and then have specify shared folders off of the workstations or on a file server.

I would still want to see your answers to the questions before believing those could be your solutions.

This discussion is closed to new replies.