On my domain I have at my disposal 8 public static IP addresses as well as the domain range that I use.
Let's say, for example, that my server is at 192.168.0.1 and that is running DHCP. All seems well on the network.
I now connect my network to the internet via a router - the router is at 192.168.0.2 (for example) - and I change the DHCP scope options to give all PCs that gateway. All is well - and now everyone can connect to the internet.
On my server, I assign it another IP address (on the same NIC) - lets say 1.2.3.4 and this is the public IP address that I have. I have also assigned 1.2.3.5 as the public IP address to the router. So now my server has 1.2.3.4 with gateway 1.2.3.5 was well as 192.168.0.1 etc - and all is well - I can now host websites and collect SMTP directly on my server.
However when I access the net - the the IP header that my server gives out is that of the router - (as it is using that as the gateway and the 192.168.0.1 is the main IP address of the server) - and this is correct. However, I want internet sites to recognise the IP address of my server when it makes web access - so I change the order of the IP addresses (and gateways) round on the server - such that 1.2.3.4 is now the primary address.
All seems to be well - however now the DHCP server stops serving. PCs booting up do not get given an IP address from the DHCP server - indeed they seem not to see it at all. It seems that the server is now trying to bind to 1.2.3.4 - but I want it to bind to 192.168.0.1
Any suggestions folks?
Hollingside Technologies, Making Technology work for you.
Let's say, for example, that my server is at 192.168.0.1 and that is running DHCP. All seems well on the network.
I now connect my network to the internet via a router - the router is at 192.168.0.2 (for example) - and I change the DHCP scope options to give all PCs that gateway. All is well - and now everyone can connect to the internet.
On my server, I assign it another IP address (on the same NIC) - lets say 1.2.3.4 and this is the public IP address that I have. I have also assigned 1.2.3.5 as the public IP address to the router. So now my server has 1.2.3.4 with gateway 1.2.3.5 was well as 192.168.0.1 etc - and all is well - I can now host websites and collect SMTP directly on my server.
However when I access the net - the the IP header that my server gives out is that of the router - (as it is using that as the gateway and the 192.168.0.1 is the main IP address of the server) - and this is correct. However, I want internet sites to recognise the IP address of my server when it makes web access - so I change the order of the IP addresses (and gateways) round on the server - such that 1.2.3.4 is now the primary address.
All seems to be well - however now the DHCP server stops serving. PCs booting up do not get given an IP address from the DHCP server - indeed they seem not to see it at all. It seems that the server is now trying to bind to 1.2.3.4 - but I want it to bind to 192.168.0.1
Any suggestions folks?
Hollingside Technologies, Making Technology work for you.