Masterclock GMR1000 - WinDiscovery and Device Issues



MasterclockGMRUserManualv2–2016.12
64
8. Unfortunately,somerouterswillnotforwardUDPbroadcastsacrossnetworks,butWinDiscoveryrequires
this.Ifyouarerunningapersonalfirewallproduct,orthebuilt‐inWindowsfirewall,youmayneedtoadjust
theirconfigurationstopassthrough(inbothdirections)UDPtrafficonport6163.
9. Verifythat
thehub/router/switchiscapableofsupportingthe10/100MBspeedtheGMRrequires.
10. VerifythataDHCPserverispresentonthenetwork.IftheGMRhasbeenconfiguredtouseDHCPfornetwork
configuration,butnoneispresent,theGMRmaynotrespondtodiscoveryrequestsforupto
twentyseconds
afterpower‐on.
11. ResettheGMRtoinitiateanewDHCPIPaddressrequest,orusethestaticIPaddressmode.
12. ConsultyournetworksystemadministratortoobtainalistorrangeofavailableIPaddresses.
Note:DHCPconfigurationisenabledasafactory‐default.Inaddition,
theclockwillresetitsaddress(during
fallback)toadefaultaddresswithinthelink‐localaddressspace(169.254.xxx.xxx)whennoDHCPserverispresent
orisnotabletobereached.

PROBLEMS:
 WinDiscoveryfindstheGMR,butthestatusdisplayisintermittentornotupdating.
 TheGMRclockisnotrespondingtoconfigurationchangesmadeinWinDiscovery.
 NowthattheGMRishookedupotherdevice(s)donotappearinWinDiscovery.
 Thestatusorsettingscharactersaregarbled.
POSSIBLEREASONS/SOLUTIONS:
1. WinDiscoverymayhavebeenleftopentoolongandtheGMR’sconfigurationmayhavechangedduringthe
session.ThiscanoccuriftheDHCPserverhasissuedneworrefreshedaddresseswithoutalertingyou.
Remedy:closeandrestartWinDiscovery.
2. Thediscoveryprocesswasnotcompletebeforeselectingyourdevice.
AfterclickingtheDiscoverbutton,
pleasewaituntilthestatusindicates100%completion.
3. VerifythatthephysicalnetworkcablesandequipmentandconfigurationforUDPhavenotchanged.
4. VerifythatyouarecurrentlytheonlyuseraccessingthedeviceviaWinDiscovery,SSHorTelnet.
5. Heavynetworktraffic
reducesthebandwidthand/orcausescollisionswiththeUDPmessages/packets.Heavy
trafficcancauseWinDiscoverytoshowoutdatedorgarbledinformation.Remedy:PresstheDiscoverbutton
againandwaituntiltheprocesscompletestorefreshWinDiscovery.
6. Takestepstoincreasethebandwidthand/orreducenetworktraffic.Ifthisisan
ongoingproblem,consider
theSSHorTelnetmethodormovetheGMRtoanisolatedLAN.

PROBLEMS:
 GMRnameappearsinREDintheWinDiscovery.
 GMRassignedanIPaddressof169.254.xxx.xxx.
 GMRisnotmaintainingitsassignedIPaddress.
 Functioniserratic.Appearstoperiodicallyreset.
