Table of Contents
Troubleshooting SMISguest client connections
Issues with the SMISguest network generally fall into the following categories:
Failure to authenticate
After connecting to the SMISguest WLAN, the client needs to open a browser window and authenticate to the wireless controller. With some operating systems / browsers, the authentication screen will open automatically upon connecting to the WLAN. With others, the user must launch a browser and navigate to a non-SSL website.
This is common on app-based devices such as iPads and iPhones. Apps which require an internet connection will not operate until the browser-based authentication is completed.
See this guide for authenticating.
A common issue is having the wrong user name / password.
DHCP / DNS issues
To complete authentication via the SMISguest network and for subsequent web browsing, the client must receive an IP address via the DHCP protocol, and must use the St. Mary's DNS servers.
Common issues with this would be the use of a fixed IP address or the use of external proxy servers.
Client-side tests
Client-side tests would include:
- checking for a valid IP address,
- testing DNS resolution (via PING)
- checking for external DNS settings
- checking for an external proxy
Checking for a valid IP address
All SMISguest network client IP addresses will be in one of the following ranges:
- 172.19.0.1 - 172.19.3.255 (North Campus)
- 172.19.100.1 - 172.19.103.255 (South Campus)
Any client IP address not in the above ranges will not be valid.
Mac
- Launch Network Utility (e.g., via Spotlight)
- Click the Info tab
- Select Wi-Fi (enX) via the drop-down list
- Verify the IP address
Windows 7
(Similar for other versions of Windows.)
- Right-click on the wireless signal icon in the Taskbar and choose Open Network and Sharing Center
- Click on Change adapter settings
- Right-click on Wireless Network Connection X and choose Status
- Click on Details
- Verify the IPv4 address
iOS 7
(Similar for iOS 6)
- Go to Settings
- Go to Wi-Fi
- Tap on the active Wi-Fi connection (SMISguest)
- Verify the IP Address
Testing DNS resolution (via PING)
With PING tests, the important point is whether the response contains an IP address. (The wireless controller will block completion of the actual ping.) This signifies that DNS resolution is occurring.
Addresses to PING
- The domain controller at dc03.smis.ac.jp
172.16.1.8 - The St. Mary's webserver at www.smis.ac.jp
172.16.101.36 - An external, non-SSL website
(e.g., www.toyota.co.jp)
In each case, ping the FQDN (e.g., dc03.smis.ac.jp) and look for the IP address (again, e.g., 172.16.1.8) in the response.
Mac
- Launch Network Utility (see above under “Checking for a valid IP address”)
- Click on the Ping tab
- Enter the address and click Ping
Sample response:
PING dc03.smis.ac.jp (172.16.1.8): 56 data bytes
Windows 7
(Similar for other versions of Windows.)
- Launch a command window (e.g., click on the Start orb, type CMD and press Enter)
- Type ping followed by a space and the address, and press Enter
Sample response:
Pinging dc03.smis.ac.jp [172.16.1.8] with 32 bytes of data:
iOS
iOS devices need a utility to ping; e.g., Free Ping or Network Ping Lite. Follow the instructions for the particular app.
Checking for external DNS settings
Use of external DNS will hinder or block use of the SMISguest network. Typically one or more of the PING tests described above will fail to produce an IP address, or will produce a different IP address than the ones shown.
Important note Third-party browsers may have their own DNS settings, independent of the operating system settings. The following settings are for the respective operating systems, and can be assumed to hold for the OS default browser.
smis.ac.jp DNS servers (internal network only)
- DC02.smis.ac.jp
172.16.1.10 - DC03.smis.ac.jp
172.16.1.8
Mac
- Go to System Preferences > Network
- Select Wi-Fi and click Advanced
- Click the DNS tab
- Verify that the expected DNS addresses are shown
Windows 7
(Similar for other versions of Windows.)
- Right-click on the wireless signal icon in the Taskbar and choose Open Network and Sharing Center
- Click on Change adapter settings
- Right-click on Wireless Network Connection X and choose Properties
- Click on Internet Protocol Version 4 (TCP/IPv4) and click the Properties button
- Verify that “Obtain DNS server address automatically” is selected
iOS 7
(Similar for iOS 6)
- Go to Settings
- Go to Wi-Fi
- Tap on the active Wi-Fi connection (SMISguest)
- Verify that the expected DNS addresses are shown
Checking for an external proxy
Use of an external proxy will hinder or block use of the SMISguest network. This may or may not result in a failure of one or more of the PING tests shown above.
Important note Third-party browsers may have their own proxy settings, independent of the operating system settings. The following settings are for the respective operating systems, and can be assumed to hold for the OS default browser.
Mac
- Go to System Preferences > Network
- Select Wi-Fi and click Advanced
- Click the Proxies tab
- Verify that no protocols are selected for proxying
Windows 7
(Similar for other versions of Windows.)
- Open the Internet Options control panel
* Start orb > Control Panel > Network and Internet > Internet Options, or
* Start orb > Control Panel > Internet Options - Click the Connections tab
- Click the LAN settings button
- Verify that Automatically detect settings is checked in the Automatic configuration pane
- Verify that the checkbox under Proxy server is unchecked
iOS 7
(Similar for iOS 6)
- Go to Settings
- Go to Wi-Fi
- Tap on the active Wi-Fi connection (SMISguest)
- Under HTTP PROXY, verify that Off is highlighted
Note Setting the HTTP PROXY to Auto can help the device remain connected when it sleeps. But if there's difficulty connecting, try first with the Off setting.
Disconnection when device sleeps
Many devices (and iPads / iPhones in particular) tend to lose their authorization when they sleep. The user is prompted to authenticate again even though the authentication period (usually 4 hours) has not expired.
Guest ID is expired
The guest ID must be reset by the system administrators every 30 days. If the client has entered the proper user name and password, but receives a “Login error” message, contact the system administrators to reset the guest ID.