![]() |
Router Network Configuration Checklist |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Kenn's
19980102: Router Network Configuration Checklist
January/1998
|
This note has been updated! See October/2000, Tech Note #9. For the latest information regarding the revisions to DHCP and TCP/IP network addressing necessitated by the transition to ADSL, please see the ADSL Network Config document at the shop ftp site, or contact Information Systems. Setting up a network which has been operating independently to access the Internet via a router requires several essential steps to ensure all components are operational and correctly configured. These same steps may be useful for diagnosing Internet problems, as well. Checklist for configuring a network to access the Internet via a router - a. Make sure all network segments are intact, and all repeaters are functional. (It's sounds obvious, but if a user never accesses the network for anything other than e-mail, their complaint that they can't access their e-mail may be nothing more complicated than a bad T-connector, or an open segment.) b. Ensure the router is powered up, connected to the ISDN line via the "U" port on the router (or NT-1, with the older routers), and connected to the network via the AUI-to-BNC transceiver. If an entire school - which previously had been working correctly - cannot access the Internet, it is a good idea to cycle the power on the router: turn it off for half a minute, then back on. Give the router another minute to complete the boot process. c. At the NT server, use Control Panel/Network to configure both network cards' TCP/IP settings correctly.
- if unsuccessful, re-check local network wiring, repeaters, and router, also check the TCP/IP configuration (ipconfig /all or winipcfg) for IP address, subnet mask, and default gateway; if you get "bad command or file name" install the TCP/IP protocol. e. At the NT server, ping mail.wsd1.org. - if unsuccessful, ping 206.45.96.66; if no system on the network can ping that (the Alpha): power cycle the router, also check with Information Systems to see if the ISDN line is down. - if you can ping 206.45.96.66, but you can't ping mail.wsd1.org, check the TCP/IP configuration (ipconfig /all or winipcfg) for the DNS server list. f. Run DHCP Manager, and check the scopes. There should be one active scope for each network card in the machine (usually two). - Both scopes should show the following global options:
IPCONFIG /RELEASE IPCONFIG /RENEWat the DOS prompt in Windows. In Windows 95, run WINIPCFGh. Check Internet applications on the workstations, and make sure Netscape, Eudora, and (on the administrative LAN) Anzio are functioning correctly. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DISCLAIMER: This document is intended for the reference of computer support personnel within Winnipeg School Division No. 1. There is no warranty or liability if procedures recommended here have an adverse affect on any systems. Use them at your own risk. Any trademarks mentioned are the property of their owners, none of whom have certified any information provided here. Opinions expressed here are personal only and do not represent the policy of Winnipeg School Division No. 1 or any other organization anywhere.
|