Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| faq:faq_desktop_firewall_proxy [2025/07/28 12:37] – grant | faq:faq_desktop_firewall_proxy [2025/07/28 12:46] (current) – [PING] grant | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| * CenturyLink - EQ-CER Range: 69.44.110.0 /24 Mask: 255.255.255.0 | * CenturyLink - EQ-CER Range: 69.44.110.0 /24 Mask: 255.255.255.0 | ||
| - | Our applications use port 80 & 443 on any of those IP’s. From a domain name perspective then you need *.t4login.com, | + | Our applications use port 80 & 443 on any of those IP’s. From a domain name perspective then you need *.t4login.com, |
| If your proxy requires authentication then you will need to allow T4 to bypass it as the Microsoft .Net Framework we use doesn’t support authenticating proxy servers. If your proxy doesn’t require authentication then T4 should work fine, but if it doesn’t then the simplest solution would be to bypass the proxy if that is possible. | If your proxy requires authentication then you will need to allow T4 to bypass it as the Microsoft .Net Framework we use doesn’t support authenticating proxy servers. If your proxy doesn’t require authentication then T4 should work fine, but if it doesn’t then the simplest solution would be to bypass the proxy if that is possible. | ||
| Line 21: | Line 21: | ||
| We don’t enable ping or tracert across our entire system. You can ping 64.74.232.69. It is a device on the edge of our network. | We don’t enable ping or tracert across our entire system. You can ping 64.74.232.69. It is a device on the edge of our network. | ||
| - | <button type=" | + | [[faq|← Back to FAQ page]] |
| + | |||