OCS does allow you to
specify different ports for different services, but this will lead you astray from most of the
published OCS documentation. I have heard of people getting this to work successfully,
but it is certainly not the most straightforward and easily supported method.
Assigning IP Addresses
Our OCS deployment will have three different networks. The Edge Server will touch each one.
As noted earlier, an Edge Server with all three roles installed needs four NICs. Each NIC
should have a single IP address bound to it. Your Edge Server Network Connections window
should look something like the screen shown in Figure 5.3.
Figure 5.3 Network Connections on the Edge
Configuring the Edge Server ??? Chapter 5 141
I recommend renaming all your connections the way I have in Figure 5.4. You will be
working with the network connections quite a bit, and it will help to have more descriptive
names than the default ???LAN Connection 1??? and so forth.
I will explain this further in the ???Dealing with Security Issues??? section later in this chapter,
but for now it??™s important to know that the A/V Edge service must have a public IP address
assigned to it.
Some people will want to put the ???internal??? interface in the DMZ segment; others will
be fi ne with having it connect directly to the internal network. In our setup, I have the Access
Edge and Web Conferencing NICs in the DMZ, with the Internal NIC connected directly
to the internal network segment.
When you assign IP addresses, you are also prompted to enter a default gateway for each
IP address.
Pages:
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199