64 bytes from thevaultinternal (172.16.1.2): icmp_seq=7955.
time=1545415.344 ms
On the Windows side, I see the pings being received and replied
to. This suggests to me it's the same problem described in the
other thread. And if you are right about that, it implies that
even if I could try a different NIC, it might still exhibit this
behavior. What's puzzling is why I can't seem to trigger it by
running multiple rsh threads and why many other users aren't
experiencing it. It's not a new problem. I've seen in way earlier
builds, possibly b110!
Hmm, according to the dtrace output, it takes no more than 1799 ms
for a kernel's ICMP round-trip. But the ping output showed
approaching 100 times longer. It seems to be something wrong
inside the VM. Does somebody else have any ideas?
I should have clarified that the actual ping time is as you say
less than 2 seconds or so, nothing like the crazy million ms being
misreported by OpenSolaris. Presumably, that is part of the bug.
The question is what is causing that and the already slow 1799 ms
response times.
Sorry, I mistook the conversion. 1799000 ns should be 1.799 ms....
Right, the response I am seeing is about 1-2 seconds.
--
Maurice Volaski, [email protected]
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
_______________________________________________
networking-discuss mailing list
[email protected]
