I'll have to do that specific IP on monday when I'm back with the server, or if I feel really dedicated (and if I manage to fix my washing machine early enough in the day.. :lol:), I might have a look tomorrow!
However, I did try a tracert on a couple if IPs on the network itself. If I do a tracrt to the server itself, it gets an immediate and correct response. If I do a tracert to any other ip on the network, I get destination unreachable.
If I do the same test, but pinging, the server obviously replies straight away. If I ping another IP, the request times out, but normally one or two of the responses will be the client computer saying Destination Unreachable.
If it is a problem on the client side, then it will be coming from something I have done on the server and what it is allocating to the client. The clients are being assigned everything from the server, if that makes sense? So I'm pretty sure its to do with the routing between the 2 LAN ports on the server - however, I'd be more than happy to be wrong if we can get it sorted!! :lol:
Thanks for the reply :)