Assuming we use the default ports are these rules correct?
I appreciate some of the services are on one box normally but want to create separate rules from the start
EEOD (Endpoint Encryption Object directory) EES (Endpoint Encryption Server) EEM (Endpoint Encryption Manager Clients) EEPC (Endpoint Encryption PC Clients) WHD (WebHelpDesk) SD (Our Service Desk IP Range)
EEOD > EES Communication what port is this? TCP EES > EEOD what port is this? TCP EES > EEPC 5556 TCP EEPC > EES 5555 TCP EEM > EES/EEOD (does the management console talk to the EEOD or the EES?) what port is this? TCP WHD > EES/EEOD (does the WebHelpDesk talk to the EEOD or the EES?) what port is this? TCP SD > WHD 443 TCP
In the installation scenario thread I posted I mentioned NATd sites where I thought We'd need to install an EES to let those NAT'd clients talk back to our EOD. Are you saying the EES can only talk to the EOD through the file system on a \\ipaddressofourEEODserver\SBADATA$\ share for example?
If we had 30 remote EES nothing would ever get done with the files being locked :eek:
Yes will do that for most schools but there a few who have their own internal range 172/192 etc where I thought we'd have to install an EES on the school ISA server to facilitate communication between the clients and our EEOD