Check the userc.C file to ensure that your internal networks are listed. When you create a new site, information about the encryption domain will be downloaded to the system and stored in a file called userc.C on the client. A simple Telnet from a client without SecureClient installed should validate whether or not this is being blocked at the firewall. If you get the error message "Connection to site x.y.z.w has failed," ensure that your SecuRemote client can communicate to that IP via TCP port 264. You should not have TCP/IP bound to your Ethernet adapter or your PPPoE adapter. The bindings for PPPoE and SecuRemote look something like this:Įthernet adapter PPPoE adapter FW1 adapter FW1 protocol TCP/IP This means that SecuRemote either will not bind to the PPPoE stack properly or will experience performance problems due to encapsulation (see FAQ 12.15). However, it adds additional protocols and virtual adapters to the TCP/IP stack, not to mention additional overhead due to the PPP encapsulation. PPPoE effectively treats your connection to the Internet like a dial-up connection. It is becoming increasingly common, particularly with cable or DSL providers, to require PPP over Ethernet (PPPoE) to connect. This situation applies to anyone who uses anything other than a standard Ethernet NIC or Microsoft's Dial-up Adapter to connect to the Internet. 12.12 ISP Uses a Custom Adapter to Connect See FAQ 12.4 for the list of ports and protocols that might need to be enabled. 12.11 SecuRemote Communication Ports Are Blocked Many problems with SecuRemote are a result of bad interactions with Windows, although there are also plenty of ways to misconfigure settings. Troubleshooting SecuRemote can be somewhat tricky.
0 kommentar(er)
