PING from client to outside with packet size biger then 1500

is it posible client with is behind MT to ping sites with packets
bigger then 1500 bytes

yes

how to do that?
every try is “Request timed out.”
when no MT is used

C:>ping 172.16.80.1 -l 65000

Pinging 172.16.80.1 with 65000 bytes of data:

Reply from 172.16.80.1: bytes=65000 time=28ms TTL=64
Reply from 172.16.80.1: bytes=65000 time=28ms TTL=64
Reply from 172.16.80.1: bytes=65000 time=28ms TTL=64
Reply from 172.16.80.1: bytes=65000 time=28ms TTL=64

Ping statistics for 172.16.80.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 28ms, Average = 28ms

when is used only I see is " Request timed out. "

OK i make a DMZ NAT and now ping is 14556 bytes bigger

need 65000 bytes ping

NO!

Max size packet of ethernet network (MTU) is 1500b. Larger packet is fragmented to 1500b.

???

ping 172.16.80.1 -l 14556

Pinging 172.16.80.1 with 14556 bytes of data:

Reply from 172.16.80.1: bytes=14556 time=13ms TTL=63
Reply from 172.16.80.1: bytes=14556 time=13ms TTL=63
Reply from 172.16.80.1: bytes=14556 time=14ms TTL=63
Reply from 172.16.80.1: bytes=14556 time=13ms TTL=63

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

i need Ping 65000b
no matter is it fragment or no
just when I type

PING 172.16.80.1 -l 65000

i don’t want to see:

Request timed out.

Verry strange no problem with Windows VISTA
ping to MT box with 65500 no problem
ping to outside too

but under XP, 2000, knoppix and SUN
Request timed out.

were is the problem ???