Thanks for the thoughts - we'd checked routing and they were identical. it was suggested the TCP Chimney offloading might be a cause, but I couldn't replicate issue.

We'll go with the name route (we don't always have name resolution on the servers we look after - hence the use of the IP/port)

Thanks anyway