> Yah ... I get that from Ames, too.  I had heard that MFS Datanet was 
> "looking into it", but I haven't heard anything since.  Bill?  Any new 
> status?

It doesn't look awful much like a MAE-W problem. Since:

 9  mae-east-plusplus.Washington.mci.net (204.70.74.102)
10  Net99-Mae-East01.net99.net (192.41.177.170) 
11  sj-0.SanJose.net99.net (204.157.38.2)
12  mae-west.best.net (198.32.136.36) 
13  netbsd.warped.com

And:

[lola-granola!jhawk] ~> ping -c 1 -p 00000000ffffffff 192.41.177.170
PATTERN: 0x00000000ffffffff
PING 192.41.177.170 (192.41.177.170): 56 data bytes
64 bytes from 192.41.177.170: icmp_seq=0 ttl=246 time=39.079 ms

but:

PATTERN: 0x00000000ffffffff
PING 204.157.38.2 (204.157.38.2): 56 data bytes
64 bytes from 204.157.38.2: icmp_seq=0 ttl=242 time=84.730 ms
wrong data byte #24 should be 0x0 but was 0xff

So it would be an internal net99 issue...

--jhawk