Book now with code EOY2025
flares2 wrote: Kareem, By Personal PC do you mean just a workstation on the network? If so you can stop the users from installing software such as AIM and MSN Mesenger by configuring their accounts or their OU through Active Directory. Your Server team, or whoever controls the firewalls (in my case the DSID) can block specific sites, like MySpace (which we also block) or block any streaming media, so you could get to a site like youtube, just wouldn't be able to watch the videos, pretty much deterring users from going to the sites. If you're actually talking about your end users using personal machines on the network where they have local admin rights, and rights to change the proxy to try to outsmart your company's firewall, you could could just MAC filter your switches so only company computers have access to the network, then follow the consideration in my first paragraph to lock down security. Hope this helps, Flares
kafifi13 wrote: Thanks for your input guys. The more you have send them along. I agree a 100% this is not a good idea. I'm fighting it to the death.
kafifi13 wrote: We are talking around 85 employees and growing. I was just speaking to my direct boss about this and he also says that part of the reason is working from home remotly. Which again doesn't make sense. We log in jusing VPN with no issues. So now they are looking to get rid of VPN and have us log directly into the server. Again makes no sense.
mgeorge27 wrote: The Cisco IOS Firewall can block all this stuff. As well as a PIX or ASA. You would be wasting money upgarding servers to support many users, when you could configure a firewall or router. Group policy can also take care of many of these problems.
Netstudent wrote: So if all the employees surf the web and use those kind of apps now, that means there isn't a policy in place now saying they can't right? Also when you do go live on VoIP, are yall going to use the PRI thats in place or are yall going to switch providers to get the VoIP? When you go live on VoIP you will need a PRI on the router which connects to the PBX. Do yall have a Full T for data? The VoIP shouln't consume bandwidth on the LAN, just the WAN link to your CO. So why not just have the PRI muxed on a T1 and have your data sent across it's own T1? You can bond the T's on the router. That way the VOIP has it's own circuit and you will not have to worry about voice traffic consuming bandwith from the Data traffic.
Use code EOY2025 to receive $250 off your 2025 certification boot camp!