[dnandoo]

Need some help configuring a static route table.

Scenario is:
Dlink router with gateway: 10.10.17.10
Server IP: 10.10.17.75
DNS 10.10.17.75

TEST workstation 1 IP: 10.10.17.100 Gateway 10.10.17.10 DNS 10.10.17.75
TEST workstation 2 IP: 10.10.10.100 Gateway 10.10.10.10. DNS 10.10.10.100

I would like both workstations to be able to see each other.

Can this be done by configuring a static route table?

[chuckhole]

Why are you using the workstation IP addresses as their gateway address? Second, what is the Subnet Mask of your network?

If both workstations are setup as follows, then they can see each other and both route via your Dlink router.

Router LAN Address:
IP Address: 10.10.17.10
Subnet Mask: 255.0.0.0
Gatway: the router WAN address

Server:
IP Address: 10.10.17.75
Subnet Mask: 255.0.0.0
Gateway: 10.10.17.10

TEST1:
IP Address: 10.10.17.100
Subnet Mask: 255.0.0.0
Gateway: 10.10.17.10

TEST2:
IP Address: 10.10.10.100
Subnet Mask: 255.0.0.0
Gateway: 10.10.17.10

As you can see, they all point to the same gateway address and the Subnet Mask defines the network ID for each of your machines as being an 8-bit network starting with 10. Since all of your machine start with 10.10, you could even change this to a 16-bit network with the Subnet Mask 255.255.0.0.

However, to bring up another subject. You are proposing that your computers use your internal DNS server for name resolution. Unless you have set up your ISP DNS Servers as Forwarders in your local server DNS, it will perform name resolution only with what it knows, your local network. Your computers will have a route identified to get to the Internet but they will not be able to perform name resolution. So when you go to a browser and type in www.mywebsite.com, it will not know where to go. It would be best to enable forwarding on your internal DNS or configure your ISP DNS server as your primary DNS.

If your server is an Active Directory server for home testing, then it will have to be configured with DNS and Forwarding.