Google Cast for Education There Was an Error Saving Settings. Please Try Again.

Notation

We'd strongly recommend users to employ Google Cast but on Chromebook, Google Pixel phone via wePresent WiCS-2100.

Description of Google Bandage:

• Users ordinarily can use the Google Cast characteristic from the devices listed below:
  • Chromebook (dominant player in the US educational activity market place; at that place are many different brands of Chromebooks, such as Google Pixelbook, Asus, Samsung, Dell, Acer, HP Chromebook),
  • Chrome browser (Windows Chrome browser, macOS Chrome browser, etc.)
  • Android Home app - Home app is developed past Google. It can be downloaded and installed on Android devices for screen & audio sharing.
  • Google Pixel phone - Pixel phone uses Google Cast every bit the native bandage protocol after Android 8.0

Troubleshooting for Google Cast

• Required Port Listing
  • TCP 8008 / 8009, Direction: both, Primary Google Cast communication
  • UDP: 5353, Management: outbound, Google Cast device discovery
  • UDP: all, Management: both, Google Cast uses a random UDP port on which to get-go an RTP server
• Time Sync
  • Real-time sync is required for Google Bandage connection. Both the sender side and receiver side (WiCS-2100) should be checked.
  • Please become to WiCS-2100 Web Admin Page, and bank check the "current fourth dimension" in Date & Time (under the System & Service tab).
  • Delight set up the correct "time zone" and "NTP server" in Engagement & Time to get the current time. If no internet is available, attempt connecting your sender device to the WiCS-2100 via MirrorOp Sender first (in order to practice the time sync).
  • Brand sure the time difference betwixt your Google Cast sender & WiCS-2100 is less than 10 mins ( suggested by Google).
• Suggest using the newest version of sender device
  • Example: Update your chrome browser / Chromebook to a newer version; Google as well fixed some connectedness problems in its new release.
• Cheque Chromecast Help:
  • https://support.google.com/chromecast/respond/3249268
  • (Google provided their recommended troubleshooting steps.)
• Compare with Chromecast receiver
  • Set up a Chromecast receiver in your surroundings. If your chrome sender is unable to observe & cast to the Chromecast receiver, there might be network related issues.

 Diagnostics & Solution

Description	Crusade	Diagnostics	Solution
Tin't Observe Receiver Device	Host unreachable The network connection failed betwixt the WiCS-2100 and the sender.	one. Ping the WiCS-2100.	1. Check network configuration. two. Check firewall settings.
Can't Find Receiver Device / Can't connect to Receiver Device	Wrong time Organization time of the WiCS-2100 and/or the sender is wrong.	ane. Bank check the WiCS-2100'south organisation time from the web page. ii. Cheque the sender's organisation fourth dimension.	1. Set the sender'south arrangement time if incorrect. two. Set up a valid NTP server for the WiCS-2100 from the web page. 3. Or, connect your sender to the WiCS-2100 via MirrorOp Sender. It will right WiCS-2100's system time. 4. After the time is synced, please check if port 8009 is reachable.
Can't Find Receiver Device / Can't connect to Receiver Device	mDNS discovery failed Sender cannot receive mDNS response from the WiCS-2100.	1. Use the Bonjour browser to cheque if the WiCS-2100 is detectable. 2. Or, open up the link (chrome://inspect/#devices) in the chrome browser and wait for 1 infinitesimal. Cheque if the WiCS-2100 is shown in the list.	1. Check firewall settings. 2. If AP is used, check if AP isolation is turned off.
Can't Find Receiver Device	Port 8009 is unreachable. Port 8009 on the receiver side (WiCS-2100) may get unreachable after time is synced.	1. Apply Telnet to connect to the WiCS-2100's port 8009 to check if it is reachable.	1. Bank check firewall settings. ii. Try to restart the WiCS-2100.
Can't connect to Receiver Device	Sender does non initiate the handshake Due to some unknown mechanism, the sender side will non initiate the handshake.	ane. Every time the sender is started, the receiver listing may show dissimilar results. two. Use a sniffer to cheque the sender's packets. mDNS response is received but the sender does not even try to connect to the WiCS-2100's port 8009.	1.Effort to restart the sender. (e.g., re-open the browser or Domicile app)

 Note. WiCS-2100 Date & Fourth dimension setting

• Delight set the correct "time zone" and "NTP server" in Date & Time to get the current time. If no internet is bachelor, try connecting your sender device to the WiCS-2100 via MirrorOp Sender first (in order to do the fourth dimension sync).
• Make sure the fourth dimension departure between your Google Cast sender & WiCS-2100 is less than 10 mins ( suggested by Google).

Note: Bonjour Browser To make certain Chrome Sender can receive mDNS response from the WiCS-2100, yous tin use Bonjour browser to verify it. In Bonjour browser, y'all shall be able to find "WiCS-2100-30" under "_googleacast._tcp." If y'all can't observe it, please bank check firewall / AP settings

Note: Chrome Inspect Open Chrome Browser and Input: chrome://inspect/#devices Wait for 1 minute and check if the WiCS-2100 is shown in the list

Backdrop

[KB8023]

Last updated Jan 06 2021

Was this information helpful?

lugostions.blogspot.com

Source: https://www.barco.com/en/support/wepresent-wics-2100/knowledge-base/KB8023

Share this post