In fact I've just tried found this command to run from cmd: ping -f -l MTU_size default_gateway_IP_address
If the MTU_size causes return an error indicating that the message is fagmented then the MTU is too high. The test needs with reducing MTU_size until no 'fragmented' error occurs. In my case, 1492 is to big - it needs to be 1472 As follows..... C:\>ping -f -l 1474 192.168.0.1 Pinging 192.168.0.1 with 1474 bytes of data: Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\>ping -f -l 1472 192.168.0.1 Pinging 192.168.0.1 with 1472 bytes of data: Reply from 192.168.0.1: bytes=1472 time=2ms TTL=64 Reply from 192.168.0.1: bytes=1472 time=2ms TTL=64 Reply from 192.168.0.1: bytes=1472 time=2ms TTL=64 Reply from 192.168.0.1: bytes=1472 time=2ms TTL=64 Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 2ms, Average = 2ms I'll set it to 1472 and give it a try. Bob -- bobertuk 1 x Duet - SC 7.3.3 - SSOTS v3.17 Lavry DA-10 DAC QNAP TS-509 3.1.0 b529T Starfish Pre-amp : Based on NAIM Heavily modified NAIM NAP 250 Power-amp Behringer DEQ2496 Linn Isobarik DMS ------------------------------------------------------------------------ bobertuk's Profile: http://forums.slimdevices.com/member.php?userid=30376 View this thread: http://forums.slimdevices.com/showthread.php?t=63880 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
