I had a chat with Matt this morning regarding VPN.
IT Services staff was actively monitoring VPN connections during the Campus closure last week. Two out of five connections from the MSUNet Realm did not have an MSU IP address assigned. At this time MSUNet Realm
users need to manually launch the Juniper NetConnect client from the VPN screen after login in order to launch the routing tunnel and receive a VPN IP address lease. Some MSU staff do not want the NetConnect client to auto-start, so this is why we have this
extra step. Auto-launch is enabled for most IDs in the CampusAD realm.
This is the first time in a while where we have had a high demand for the Campus VPN, and a review of the procedures is probably needed. The following link should direct you to the location in the (lengthy) Techbase
article detailing the steps needed to connect to the MSU VPN offering.
http://techbase.msu.edu/article.asp?id=8068&service=#s80032
Also, while we did not hit our concurrent connection limit nor run out of IP addresses last week, we have had discussions regarding expanding the IP lease range in the near future. We’ll also discuss the pros/cons
of NetConnect auto-launch to simplify connectivity for a vast majority of our staff.
Thomas Porter, CISSP
IT Services – Network Management
450 Auditorium Rd. Rm. 301
Michigan State University
East Lansing, MI 48824
517-884-3086
From: Stehouwer, Matt [mailto:[log in to unmask]]
Sent: Wednesday, January 15, 2014 9:24 AM
To: [log in to unmask]
Subject: [MSUNAG] VPN
What are others doing with VPN? Do you run your own or use MSU VPN. We are starting to getting more phone calls from our users that the MSU VPN is not working. When users call the help desk they tell the problem. I don’t want to put in
our own VPN but looking more like that’s what I may have to do.
Matt Stehouwer
Technology Manager
Michigan State University
College of Natural Science Deans Office
288 Farm Lane RM 154
East Lansing, MI 48824
517 355-9003 | Email:
[log in to unmask]
Linked-In: www.linkedin.com/in/mattstehouwer/