Routing and Remote Access / Troubleshoot RRAS
Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com’s entire library of video tutorials.
Learn More
Subtitles of the Movie
This last module of chapter 4 looks at a couple of troubleshooting scenarios, but really keep in mind as we talk about some of this, that you're best prepared for troubleshooting, by having a full understanding of the technologies that you're working with. There's just nothing that can say. Okay well if you study this module or this chapter or a book, you'll be ready for anything that can be thrown at you in a working environment. You have to know what you are dealing with before you're able to effectively troubleshoot. That being said though, there are a couple of common things we can lookout for that should not slip past us as troubleshooters. And these fall into 2 different categories, we will look at some routing problems and then remote access problems. When we're troubleshooting routing most all of the problems fall into a single category, the router is not forwarding packets. So if it's not or if it's not doing it like you expect it to, then you need look at couple of things. First of all don't miss the obvious, is the server running, is the server configured as a router? To check those things look at remote access MMC snap-in, and make sure that indeed that the server has been configured, that it's running and has not been disabled, and then finally make sure it's been configured as a router. Investigate the properties from the general tab, make sure that this check box is indeed checked. Other things that you should look for, look at the routing tables, are the routing tables correct, are there are incorrect entries. And then finally look at your TCP/IP configuration. That can be the source of or as you'll discover that's going to be the source of may be 60, may be 80% of network communication problems. That there's something wrong with either the IP configuration on the remote access server or probably more likely the IP configuration on the clients themselves. Remember the IP-config utility which can help you investigate those kinds of problems. Quickly shows you your IP configuration, we looked at that in module 2 a little bit. Other types of problems under the category of remote access and those fall into 3 general categories. One we're unable to establish a connection to the RRAS server, two we are unable to access resources beyond the RRAS server, and three callback is not working the way we want it to. If we're unable to establish a connection don't miss the obvious, is the modem working, remember we're going to have to have a modem at both client and receiving side if we're dialing up to a remote access server. Again make sure that the service indeed started. And if you're establishing a VPN connection or a modem connection make sure that ports have been enabled for those inbound connections. Again you investigate those with the ports node of the server and make sure that there are plenty of ports or that the right type of ports have been enabled, and finally that in the configuration of those ports make sure that they are enabled for remote access connections. Those are a couple of things you can do. If you are unable to access resources beyond the RRAS server, what that means is that you connect to the RRAS server, but that RRAS server is not forwarding any packets to the private network. Well that's a function of routing, forwarding packets, so if you're unable to do this then probably what the cause is, is that IP routing is not enabled. Also if you have turned firewall filter software on, make sure that packet filters aren't preventing certain kinds of traffic that you're trying to get through from getting through that private network. So either disable those filters, disable the firewall, or set exceptions so that the traffic you want to pass through can indeed pass through. And then finally if callback is not working that usually comes down to human error and you should verify the properties of call back on the dial-in tab of the user account. Active Directory users and computers if you're using Active Directory, the dial-in tab, you'll also find the dial-in tab from computer management under local users and groups. So just a couple of troubleshooting scenarios and their possible solutions. Things that you should not miss, things that certainly don't cover everything that can be thrown at you in a troubleshooting situation, but you should certainly know these as you start to prepare for the 291.
Tutorial Information
| Course: | Microsoft Windows Server 2003 (70-291) |
| Author: | Brian Culp |
| SKU: | 33478 |
| ISBN: | 193207273X |
| Release Date: | 2004-02-26 |
| Duration: | 8 hrs / 99 lessons |
| Captions: | For Online University members only |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |
VTC Sign up & Benefits
- Unlimited Access
- 98,729 Video Tutorials (23,265 free)
- Video Available as Flash or QuickTime
- Over 1026 Courses
- $30 for One Month Access
- Multi-User Discounts Available
United States 