Marisa H. Pfalzgraf writes:
> SOCKSified software from an internal machine. There is no improvement in
> response if an IP address is used in the commands in place of a site name.
> The lag in the response occurs AFTER the "Connected to site.name. Escape
> character it '^]'." message. Pings to remote systems from the firewall
> give a normal reponse time.
Two diagnostic suggestions:
- run a client from within truss(1) and watch the output in realtime.
This sometimes gives insight as to which calls are "stalling".
- put a packet sniffer (or use snoop(1M)) on the line and see if
something is timing out. I recently saw a problem where a flaky
router would stall on the first few packets to be routed to a "new"
host. (Took a while to load a new entry into the arp table.)