On-Premise Streaming - Troubleshooting Connectivity Issues

Summary

This article is designed to provide assistance for troubleshooting connectivity problems that may arise between a client device and the Swank Streaming Server. It aims to guide users through the various steps and considerations necessary to identify and resolve issues preventing successful streaming from the server to the client device.

Client Issues

1. Try restarting your client device. Restarting can help refresh the system, clear temporary glitches, and restore normal operation. Simply power off your device completely, wait for about 10 seconds, and then turn it back on. This process often resolves minor software issues and improves overall performance.
2. Test a different client device on the same network
   • Assists in determining whether the issue originates from the client device or another element.

Server Issues

1. Confirm Power and Boot Status
   • Make sure the streaming server is powered on and fully booted.
2. Verify Physical Connections
   •  Ensure Ethernet cables are securely plugged in on the server and network port.
   •  Check for link lights on network ports.
   • Test with a known working network cable.
3. Check Network Configuration
   •  Verify IP addresses, subnet masks, and gateways are correctly configured.
4. Try Restarting the Server
   • Restarting can help refresh the system, clear temporary glitches, and restore normal operation. Simply power down the server completely, wait for about 10 seconds, and then turn it back on. This process often resolves minor software issues and improves overall performance.

 

Network Issues

1. Basic Connectivity Tests
   1. Ping Test
      • From the client, ping the server’s IP address.
      • If it fails, try pinging the client from the server.
   2. Traceroute
      • Run `tracert` (Windows) or `traceroute` (Linux/macOS) to identify where the connection fails.
   3. Check DNS Resolution
      • Try pinging the server by hostname.
      • If it fails, run nslookup to confirm the DNS entry is accurate.
      • Flush DNS and ARP Cache
        • Run `ipconfig /flushdns` and `arp -d` on Windows or equivalent on Linux/macOS.
2. Firewall and Security
   • Confirm firewalls are not blocking traffic.
3. Check Antivirus or Security Software
   • Ensure security software is not interfering with network traffic.
4. If your organization is using IP Restrictions, confirm the appropriate IPs are allowed. Additional details about this can be found here: IP Restrictions

SSL Certificate Issues

Confirm your SSL certificate has not expired