Skip to main content. Find threads, tags, and users Hi, I've seen this occur twice already when setting up new Windows servers. Thanks, T. Current Visibility: Visible to all users. Hi, Just want to confirm the current situations. Please feel free to let us know if you need further assistance. Best Regards, Candy. Hi , Have you received such error message in Remote Access management console? But today, most computers sold are laptops, and increasing numbers of people take their primary computer with them when they leave the office for the day.
Unfortunately, once people take their computers out of the protected glasshouse that is your internal network, all sorts of bad things can happen to them. Malware, which might have been blocked by the external firewall, will be inadvertently downloaded on the home ADSL connection. Computers that you were able to keep completely healthy when they were under your control are now exposed on a daily basis to all manner of Internet nasties. The question of whether you should use static or dynamic routing is really a question of administrative overhead.
In the end, the result of your network traffic being routed to the correct network should be the same, no matter what method you choose. With static routing, you must make an entry on your Windows Server for every network that will be routed by that server. You could configure it with two simple route add commands. On the other hand, on a network where you want the Windows Server system to route for 25 networks or to exchange routes with a Cisco network that uses RIP, you will want to choose dynamic routing.
Obviously, you do not want to have to key in those 25 networks manually nor can you provide the true dynamic features that RIP provides. Static routing in Windows Server is nothing new. We have been using the route command for years. You can configure static routing in Windows Server using either the route command or using the GUI.
Thus, I highly recommend that if you are going to use static routing in Windows , you just use the route command at the windows command prompt. Showing the static routing table is easy, just use the route print command, as you see in Figure 1 below. In the route print output, the first important thing that you see is the interface list.
Windows Server IP interfaces are labeled with an interface number. The interface numbers in Figure 1 are 16, 14, 1, 15, 20, and These interface numbers are used whenever you add or delete routes to the routing table.
0コメント