On the Edge Server, enter a default gateway only on your A/V Edge service. For the
rest of your addresses, do not add a default gateway; this will cause the Windows routing table
to behave erratically and you will defi nitely have problems getting the Edge Server to work.
To be able to route to the rest of your segments, you will need to create static routes on
the Edge Server.
Creating Static Routes on the Edge Server
Because the Edge Server will use addresses on three networks but will have only one default
gateway, you will need to confi gure a couple of static routes on your Edge Server for it to be
able to reach all the necessary networks.
As I said in the prior section, the A/V Edge will have a default gateway, so it??™s the other
two networks that need the static routes. In our scenario, these networks are in the 192.168.1.0
and 172.16.1.0 range. To confi gure static routes to these networks follow these steps:
1. Open a command prompt on your Edge Server by selecting Start | Run and
typing cmd.
WARNING
Do not try to assign multiple IP addresses to the same NIC; this can have
strange and unpredictable results on the Edge Server. Although many other
applications seem to have no trouble using several IP addresses bound to the
same NIC, many times I have seen OCS in general and the Edge Server in
particular not functioning reliably with this confi guration.
For example, if you assign the internal and external IP addresses to the
same NIC, the Edge Server will not allow any external OCS clients to log in.
Pages:
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200