Streamyx Cannot Ping Default Ip Gateway
The default gateway IP address is usually the IP address of your router. Here's how to find your default gateway in Windows 10, 8, 7, Vista, or XP.
Hello,I'm a server admin and by no means a network admin.At work I have two networks (10.0.1.) & (172.16.0.)On the 10.0 network all clients and servers can ping the gateway. On the 172.16.0 network none of the servers can ping the gateway. But they still get internet access.Their is a sonicwall firewall which I assume has 2 lans or wans configured and something called jail.My basic question is should a server always be able to ping it's gateway?The difference between the two is the 10.0 is internal and the 172.16 is internet facing. They call it the dmz.Anyway looks like I have some reading to do. I'd appreciate any input.Thanks. 10.0.0.0 is what they call a private network.
These networks cannot talk to the outside world with out the use of NAT or PAT. Which acts as a translator between the public IPs from ISP (internet service providers) and company's private networks. May also be a private network with the only public IP existing on a router or firewall interface.Your question: My basic question is should a server always be able to ping it's gateway?
The simple answer is no, if the server is only concerned about talking to other devices in its LAN local area network it does not need to ping a gateway. However if the server need to access the internet or other networks it does need access to a default gateway. Which in most cases is a router of some kind. As I explained, I don't have hardware in this case; I do have two licenses for Server 2016. And the 'you wouldn't do this in production' is a bit nonsensical - I wouldn't be running UCS or ESXi on a VM in production, but I am because it makes sense for the lab environment.Thanks, all, for the input - unfortunately I see this a lot on this forum; people so stuck on 'why would you do it that way?' They're unwilling (or unable) to work through the issue. Yes it is not best practice, and yes a physical router (while having its own drawbacks) is the way you would do it in production.
But I am sure I am not the first person to use Server as a router, as MS has whitepapers on doing just that.Again, thanks for the replies; think I am going to take this question over to the Virtualization sub-forum as they seem more willing to help people work through issues rather than getting into analysis paralysis as to why you're doing it one way or another. 10.0.0.0 is what they call a private network. These networks cannot talk to the outside world with out the use of NAT or PAT. Which acts as a translator between the public IPs from ISP (internet service providers) and company's private networks. May also be a private network with the only public IP existing on a router or firewall interface.Your question: My basic question is should a server always be able to ping it's gateway? The simple answer is no, if the server is only concerned about talking to other devices in its LAN local area network it does not need to ping a gateway.
Streamyx Cannot Ping Default Ip Gateway Password
However if the server need to access the internet or other networks it does need access to a default gateway. Which in most cases is a router of some kind.