| field. |
| 3. Click Update. |
|
|
Cause 2 | The user normally connects to the Internet through |
| their corporate network, which is behind a firewall. |
|
|
Resolution | In this instance, users must tunnel into their |
2 | corporate network in order to receive e−mail. See |
| Resolution 1 in order to only allow the users to |
| send mail. |
|
|
IIS Proxy LAT Setup (BBSM 5.0 only)
Proxy Local Address Tables (LAT) add routes to the RRAS tables. These LAT table settings are needed for proper BBSM operation.
| ∙ Clients are only able to connect with the | |
|
| Proxy Server. |
| ∙ Clients are able to ping the external | |
|
| Network Interface Card (NIC), but not the |
Symptoms |
| internal NIC. |
| ∙ Clients are unable to access the Report | |
|
| pages from the internal NIC, but can reach |
|
| the pages from the external NIC. |
| ∙ The client gets a Page cannot be | |
|
| displayed error message with no proxy |
|
| setup in the browser. |
|
| |
Cause | The LAT tables in IIS under Web Proxy are not set | |
| up correctly. | |
|
|
|
Resolution |
|
|
| 1. | Click Start > Programs > Microsoft |
|
| Proxy Server > Microsoft Management |
|
| Console. |
| 2. | In the left window, click + , the plus sign, |
|
| next to BBSM. |
| 3. | Right−click Web Proxy and choose |
|
| Properties. |
| 4. | With the Service tab selected, click the |
|
| Local Address Table button. |
| 5. | Click the Construct Table button. |
| 6. | Uncheck the Add the private ranges box. |
| 7. | Make sure Load from NT Internal |
|
| Routing Table and Load known address |
|
| ranges from all IP Interface cards are |
|
| both selected. |
| 8. | Click OK. |
| 9. | Click OK again in order to confirm |
|
| changes to the LAT tables. |
| 10. | Make sure the ranges now include: |
|
| Internal network IP addresses External |
|
|
|
Cisco − Level Two Technical Support for BBSM
