Troubleshooting smart bridgit server connections, Symptoms, Solution – Smart Technologies Smart Bridgit 4.5 User Manual

Page 72

Advertising
background image

Microsoft Windows operating systems include the PathPing tool to measure packet loss rate and

latency. PathPing sends packets to each router on the path to a destination for an interval, and then it

computes results based on the packets returned from each hop. Since PathPing shows how much

packet loss is seen for any router or link, you can determine which routers or links are causing

network problems. For more information on using PathPing to determine network latency and packet

loss, see the Microsoft website.

Troubleshooting SMART Bridgit server
connections

This section help you resolve connection issues that are caused by your SMART Bridgit server

software or your network environment.

SMART Bridgit server connection issues can result from an incorrect domain name server (DNS)

configuration for routing to the SMART Bridgit server or from the server computer's domain and IP

address and port forwarding settings on the network servers, routers or firewalls.

Symptoms

l

When a SMART Bridgit client connects to a SMART Bridgit server that’s running on the same

computer, a The <servername.com> server is not available. Try again later or select another

server error message appears.

This error message can also appear when a client's software causes the issue.

When you're unable to connect to SMART Bridgit software server and SMART Bridgit client

software is causing the issue, see

smarttech.com/kb/099567

.

l

An error message appears when you connect to a SMART Bridgit server from an Internet

browser.

Solution

Verify that you're using the latest version of SMART Bridgit Server software. See Upgrading

SMART Bridgit server software on page 20. If the software upgrade doesn’t resolve the issue, try

these procedures:

l

Verifying the network's DNS configuration on the next page

l

Verifying SMART Bridgit server configuration on the next page

l

Manually updating the Windows registry on page 71

A P P E N D I X

A

Troubleshooting

68

Advertising