User Guide

• NetDB Template Requests & Modifications
• Data Flow
• Health Check Tool Actions
• FAQ

Project Documents

• Functional Specification
• General Use Case
• Use Case Scenarios
• Wire Frame Diagram
• Background
• List All Documents

Related Pages

• Net DB

• IT Services
• Stanford Network Self-Registration

Stanford Network Self-Registration

Overview

The Stanford Network Self-Registration service combines a web-based self registration application and a health check tool to be run on the registering host computer. It is designed to make the process of network registration easier and to improve desktop security and network records accuracy. The system accommodates some custom configuration — on a network segment basis — by local network administrators (LNAs).

IT Services provides the software, associated documentation, and support of the system are provided as a general service to the Stanford community. (This service finishes the job started by the initial Host Self-Registration — or “HostReg” — project.)

Stanford Network Self-Registration is offered as a per-network opt-in service.

The Stanford Network Self-Registration service is designed for ’round-the-clock use, but support for HelpSU or 5-HELP requests is limited to business hours: Monday–Friday, 8 AM to 5 PM.

Opting-In to Stanford Network Self-Registration

An LNA wishing to opt-in should contact a Department Network Engineer and ask that the network record be modified. The Department Network Engineer will provide the LNA with an IP address range to use.

Request assistance from a Department Network Engineer via HelpSU.

The network record will be modified to include the following options:

1. non-routable address space
2. roaming addresses
3. DHCP options:
   domain-name-servers=hostreg.stanford.edu
   permit=only-unknown-clients

More information about the opt-in process, including example NetDB screens and optional Custom Fields settings, see Requesting and Configuring a Hostreg-Netname Template.

What Departments Have Opted-In?

The software is currently used on the following University subnets: