I encountered an SCO problem yesterday...

It seems that sco unix is very strange.

I want to try the client of the DNS ON THE openserver machine and add/etc/resolv. conf. Who knows that the gateway can be pinged, but now the ping fails, and the system is dead

Then write the Intranet DNS in resolv. conf on the front and the Internet DNS on the back. You can ping it.

Later, I observed that the ping was not successful, but only one packet was received, which caused a problem.
(1) only one packet is received.
(2) After receiving the first packet, the operating system determines that the host is alive, and then discards the remaining packet.

No way. Come up with my packetyzer, connect SCO to a hub in the notebook, define rules, and take a look.
It is found that every package actually returns, that is, the above (2) Guesses are correct.

But why?

I tried it.
# Ping-N desip
Yes. The-N parameter indicates no reverse solution. If/etc/resolv. conf exists, PingProgramWill try
Use the nameserver to reverse solve the problem. If the reverse solution fails, it will always reverse the problem. It's so stupid openserver...

It turned out to be reversed by default. I guess it's been a long time...