Save yourself the time and effort by sticking to the Microsoft-recommended
(and supported!) method of assigning only one IP address to each NIC.
142 Chapter 5 ??? Confi guring the Edge Server
2. Once the command window opens, type the following command:
C:\route add ??“p 192.168.0.0 MASK 255.255.0.0 192.168.1.1
C:\route add ??“p 172.16.0.0 MASK 255.255.0.0 172.16.1.1
3. Once the routes are added, type the following command:
C:\route print
You will see that the routes we have added appear at the bottom of the route
table. They show up as persistent routes (that??™s what the ??“p switch in the command
does) because they will remain even after a server reboot.
4. Once you add the static routes, reboot the server for the changes to take effect.
When the server comes back, be sure you can connect to servers on all three
networks.
Installing the Software
Now that we??™ve taken great pains to ensure that our underlying networking components are
set up correctly, we can move to the installation of the Edge Server. Note that you should
install the Edge only after you have deployed your OCS front-end and back-end servers
internally. (The only exception to this rule is if you happen to be migrating from LCS
to OCS. In that case, the Edge Server is typically deployed fi rst.)
Install the Edge Server on a Windows Server 2003 or Windows Server 2003 R2 platform.
The machine on which you install the Edge Server should not be a member of the domain,
but rather a stand-alone workgroup.
Pages:
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201