General discussion

Locked

Win2K NAT

By armand ·
We're running a Win2K Advanced Server for NAT. We've got 3 NIC's installed. 1 for our internal network and 2 Intel Adapters teamed for our public addresses. I've assigned 3 public IP's to the adapter team and assigned these to the NAT public interface pool.
Our application/exchange server is on a public network as such users have to go through the NAT box to download sofware or emails. This works fine for small apps but as soon as you start downloading big apps or email attachments it times out or gives a message stating that the network path is no longer available. Any ideas how to work around this as I don't have enough public IP's to give everyone and NAT looked like the ideal solution.
Thanks
Armand

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
Thread display: Collapse - | Expand +

All Comments

Collapse -

Win2K NAT

by rwscc In reply to Win2K NAT

NAT requires a lookup table that is constantly changing to map the connection port numbers and ip addresses. This table must reside in memory to proccess the packets without running into timeouts. If this table gets swapped to the pagefile someone is likely to loose there connection waiting for it to get swapped back into memory. If you have other apps on the server that allow "partioning" of memory, be sure you leave a big chunk for the OS.

The other posibility is congestion on the public network. You may have two 100meg NICs dedicated to it but it may drop down to a multiple t1 segment a little farther down the road.

Collapse -

Win2K NAT

by armand In reply to Win2K NAT

The question was auto-closed by TechRepublic

Collapse -

Win2K NAT

by Michael Roark - CCNA/DA MCP 3CSA In reply to Win2K NAT

If your Exchange server is on the public side, why don't you dual-hone it? if one of your NIC's goes to the public side, for laptops and employees in the field, and the other one is on the intranet, you have less of a chance of timeouts through the NAT, because you could tell everyone's outlook to go straight to the server on the intranet side...
OR... If you have a 802.1q capable NIC in the Exchange server, and a VLAN tagging capable switch, you could swing the IP's that way, but you're asking for the cheap way that way, and the port/NIC may get bogged down (depending on traffic)
Good Luck,

Collapse -

Win2K NAT

by armand In reply to Win2K NAT

The question was auto-closed by TechRepublic

Collapse -

Win2K NAT

by armand In reply to Win2K NAT

This question was auto closed due to inactivity

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums