User:Jroth/CM

= Campus Manager Notes =

Steps
The process is generally as follows:

1.     Student first plugs in (a reboot may be required RIGHT after this for Win95, 98 or Linux).

2.     Go to the web. The first registration page should show up (unless they are at something.binghamton.edu).

3.     Read AUP, do updates and install AV if necessary.

4.     Enter username and password to sign in. (this portion is SSL)

5.     Run the SMA tool. Follow directions if you failed.

DNS Issues
If they are in registration and cannot get the registration webpage, they may have static DNS set.

DNS cannot be set statically; it must be used from DHCP.

i.e. DNS server should either be 172.16.224.2, 172.16.240.2, 172.18.224 or 172.18.240.2

No other DNS servers are allowed, they will not work.

Allowed Sites in Registration
While on these networks you can only connect to certain sites. I.e. Windows Update, McAfee, Symantec, Binghamton.

Registering (Username & Passwords)
Pods username and passwords are required for STUDENTS in registration.

If they are a new student their original passwords are available on BUSI. If they do not know their password then they can try to reset it on the BUSI website. RD's should not need to register the machines in their offices. If they receive the registration page then please contact the Helpdesk (so they can notify Joe Roth). RD's machines in their apartments do need to be registered.

Campus Manager Networks
These are the IP ranges of the network used by the Binghamton Network Manager.

Registration IP’s: 172.16.224.x – 172.16.239.x, 172.18.224.x - 172.18.239.x          Remediation (quarantine) IP’s: 172.16.240.x – 172.16.255.x, 172.18.240.x - 172.18.255.x          Dead-end IP's: 172.17.0.x - 172.17.0.63 DNS: 172.17.0.10 No Gateway

What the CSA Tool Does
Checks for valid antivirus (McAfee, AVG, Nortom/Symantec, etc.). for Macs Virex/McAfee, Norton and Sophos are valid. Requires all critical Windows updates. Sets Windows updates to auto. Checks for/removes bridging.

Concerning Hubs, Routers, etc.
When a hub is present in a room, the recommended procedure for registering is to have each client plug into the wall individually and register, then connect the hub.

If an unregistered machine is plugged into a hub, then the ENTIRE hub will be put into registration. This will not happen right away, and may to take up to two hours. All clients on the hub will be in registration after this point UNTIL the rogue machine is registered.

On Windows 2k, XP. Mac and Linux systems the MAC address that is registered is pulled directly from the machine. Meaning that if they are connected to a router the router will not be registered. The client will need to connect directly to the wall.

NOTE: Routers ands WAPs are not permitted in the dorms. If a client has multiple devices that they need to connect, suggest a mini-hub or min-switch.

Other Issues
Linux and some macs may have to reboot RIGHT AFTER first plugging in. This is in order to obtain a new IP.

Rogue Client not found error - This will occur if the system is under a high load and has not read their switch yet. This means that a rogue client record does not actually exist for them. Have them reboot and then wait 10 - 15 minutes.

Gaming Consoles
XBOX’s, PS2’s, GameCubes and network printers will not work by default. A page exists where students can register these themselves. It is linked off of http://resnet.binghamton.edu

Return to Registration
After registering and rebooting, the machine still returns to the registration site

The registration system is based on mac addresses. If the machine is generating multiple mac addresses (spoofing) for any reason it may be placed back into the registration network. Check for bridging on the machine. The mac address of the bridge may be what has been advertised to the Network Manager.

Check the machines IP. If it is a BU network IP (128.226.x.x), then the cache needs to be cleared. Clear the cache and reboot.

If the machine still has a registration IP, make sure that they are not connected to a hub in the room. All machines connected to a hub have to register.

Make sure that the machine is not connected to a router. The system WILL NOT register a router on XP and 2k systems.

Unplug the cable from the machine, wait 5 seconds and then plug the cable back in.

When the registration load is heavy, sometimes it can take up to 5 minutes for the ports network to be switched.

Check the start page of the browser. Make sure that it is not set to anything on the registration site.

Windows Update fails to run
Try running/reinstalling the following:

vbscript installer

xml installer

re-register Windows Updates dll's

Service Pack for .NET Framework does not install
Uninstall .NET Framework 1(.1)? And install .NET 2.0.

Or try the .NET cleanup tool. Thanks smatarese. http://bingweb.binghamton.edu/~jroth/cleanup_tool.exe