• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Communication with the JamKazam network service timed out.
#1
MacBook Pro 6,1 macOS 10.13.6
JK 1.0.1.0.4001
Connected via DLink 8-port switch to Linksys EA3500 router, then to Technicolor TC4350 cable modem, 150 mbps service. No WiFi involved.

Running the network test, I first get:

"Unable to Determine Network Type
We are unable to determine if your computer is connected to your network using WiFi."

Running test anyway seems to work sometimes, other times I get:

"Communication with the JamKazam network service timed out."

Also tried direct connect Ethernet cable to router -- no difference. Sad
  Reply
#2
stuzogMacBook Pro 6,1 macOS 10.13.6
JK 1.0.1.0.4001
Connected via DLink 8-port switch to Linksys EA3500 router, then to Technicolor TC4350 cable modem, 150 mbps service. No WiFi involved.

Running the network test, I first get:

"Unable to Determine Network Type
We are unable to determine if your computer is connected to your network using WiFi."

Running test anyway seems to work sometimes, other times I get:

"Communication with the JamKazam network service timed out."

Also tried direct connect Ethernet cable to router -- no difference. Sad


Same Issue here.. Maybe has to do with the new update?
  Reply
#3
Same problem with my wideband cable connection: (>100 Mb/s download; 5 to 47 Mb/s upload); direct ethernet connection to the router.

Ping statistics for 8.8.8.8:
Packets: Sent = 5030, Received = 5030, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 46ms, Average = 20ms

The  connection to Virgin Media cable was error free for 5,030 seconds (1 hour and 24 mins). I then stopped running the test!
  Reply
#4
Same issue here. I found this while trying to figure out if I needed to manually poke a port hole in my router....
  Reply
#5
I read on one of the other forums that the "network test" server keeps cra$ng. THey reboot it once an hour, but often it crashes quickly because so many are trying to use it. Said they were working on a more robust solution.
  Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)