APLawrence - Information and Resources for Unix and Linux Systems, Bloggers and the self-employed
RSS Feeds Get APLawrence.com by RSS











(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Home > Unix Articles > Windows 2000 and RIP
Printer Friendly Version






Windows 2000 and RIP

By Scott Clowers

We have about 42 franchises scattered across the US that connect to the home office via a mixture of frame-relay and VPN's. All of these franchises have at least one server running SCO OpenServer 5.0.4. The majority of workstations are running on Win98, but we have Windows 2000 starting to show up as these franchises upgrade to new equipment.

Last week I got a call from a user at one of the franchises who had a new system running Win 2000. The problem he reported was that several times a day, he and another user (that was also using Win 2000) could not retrieve email or access the Internet. (We house the E-Mail server for the whole company here at headquarters, and provide access to the Internet for all the frame-relay connected franchises). He stated that he could reboot these machines and everything would work for a short period of time and then the same problem re-appeared. He further stated that when this problem existed, he could establish a dial-up connection to the Internet (AOL, Mindspring, etc.) and access the Internet just fine. He thought the problem was related to our company DNS server. He was experiencing the problem when he called me, so I did some trouble-shooting. His DNS resolution checked out OK, and he could ping everything on his local network, but could not ping anything here at the home office. However I could ping other nodes on their LAN from headquarters and the computers on their LAN that were running Win98 showed no sign of trouble. I had him bring up a command prompt and run "route print". I have included a screen shot of the results that he sent me over his dial-up connection.



I was very surprised to see that there were 2 routes listed for every destination network. One route was correct and pointed to their router as the gateway. The second route pointed to their SCO OpenServer machine with a metric of 2 or 3. All of the franchises have only one router and the SCO machine uses that same router as it's gateway, so this made no sense to me. I have no experience with Win 2000 yet so I turned to the Microsoft Knowledge Base to research routing issues in Win 2000. Several articles seemed to indicate that in Win 2000, if RRAS is installed, so is RIP. However, we only run RIP on the router(192.168.x.5) at our franchises so that didn't explain where the routes pointing to the SCO machine(192.168.x.1) came from. So I decided that the SCO machine must be running RIP. A little research (I read the SCO man page for routed) revealed that if the SCO machine was configured as a gateway, it automatically enabled RIP. Since our SCO servers only have one NIC in them, we don't configure them to be gateways, but I took a look at this one anyway. Low and behold it had mistakenly been configured as a gateway. I deselected this option, did a kernel relink and rebooted it. I had my user reboot his Win 2000 machine and do another "route print" and the dual routes were gone. This seems to have solved his problem.


If this page was useful to you, please click to help others find it:  
Your +1's can help friends, contacts, and others on the web find the best stuff when they search.


Comments?




More Articles by Scott Clowers



Click here to add your comments



Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



LOD Communications, Inc.

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.


My Troubleshooting E-Book will show you how to solve tough problems on Linux and Unix systems!


book graphic unix and linux troubleshooting guide




Buy Kerio from a dealer who knows tech: I sell and support

Kerio Connect Mail server, Control, Workspace and Operator licenses and subscription renewals
g_face.jpg

This post tagged:

       - Administration
       - Microsoft
       - Networking




Unix/Linux Consultants

Skills Tests

Guest Post Here