Reg
eXperienced!
- Joined
- 2 Mar 2002
- Messages
- 639
I understand what Zedric is saying as I am currently working with a school network that is using NAT.
See, with SOHO networks, NAT is a beautiful thing. In a large network (big business), NAT can be a mistake. For one, NAT works by switching IP addresses from Local to Public as packets get out to them. This can become a problem because a lot of software used in big businesses do not contain a NAT translator. They simply send out on the line and the router does the rest. ADP software, which is used by most businesses to handle payroll, can not establish a direct connection to the system because the software will only respond to requests at the local address and not the public (this is due to security). You have to have a good understanding on how NAT operates to better understand what goes on.
Most large networks work better with a firewall and public IP's per workstation rather than NAT. While newer protocols such as UPnP and NetBEUI allow for better translation over NAT, the downfalls to it can cause other issues.
See, with SOHO networks, NAT is a beautiful thing. In a large network (big business), NAT can be a mistake. For one, NAT works by switching IP addresses from Local to Public as packets get out to them. This can become a problem because a lot of software used in big businesses do not contain a NAT translator. They simply send out on the line and the router does the rest. ADP software, which is used by most businesses to handle payroll, can not establish a direct connection to the system because the software will only respond to requests at the local address and not the public (this is due to security). You have to have a good understanding on how NAT operates to better understand what goes on.
Most large networks work better with a firewall and public IP's per workstation rather than NAT. While newer protocols such as UPnP and NetBEUI allow for better translation over NAT, the downfalls to it can cause other issues.