Testing your building connection

Test your building connection by opening a command prompt and trying to ping a node outside of your building (i.e. ping 129.79.1.1, to reach the nameserver). On a Windows or Unix based computer, the output should resemble the following:

Unix

unix-based ~ > ping 129.79.1.1
129.79.1.1 is alive

Windows

C:\WINDOWS\Desktop>ping 129.79.1.1

Pinging 129.79.1.1 with 32 bytes of data:

Reply from 129.79.1.1: bytes=32 time<10ms TTL=254
Reply from 129.79.1.1: bytes=32 time<10ms TTL=254
Reply from 129.79.1.1: bytes=32 time<10ms TTL=254
Reply from 129.79.1.1: bytes=32 time<10ms TTL=254

Ping statistics for 129.79.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


Note the "Lost = 0 (0% loss)," output. Report any loss to the IUB-Network Operations Center. Following is an example of output from a ping from a network connection that may be down):

C:\WINDOWS\Desktop>ping 129.79.1.249

Pinging 129.79.1.249 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 129.79.1.249:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Again, note the "Lost = 4 (100% loss),". This indicates that no packets are being echoed back to you and that your buildings network may be down. Notice also that you must ping a node that you know is not down.

Macintosh

To verify a building's network connection from a Macintosh computer, open the Chooser and click on AppleShare. If AppleTalk Zones are displayed, then your building's network connection is likely working properly. This method tests the "AppleTalk" protocol. Another test would be to open an Internet browser, such as Netscape, and try bringing up a URL that you have never visited before.

UITS Home

Telecom Services

Data Network Services