Windows 2003 and NAT

I have set routing with NAT translating.
It is working fine but problems starts when there are lot conections to
that server - seems there are limit somewhere. It is not letting some
clients to connect to public network if there is someone who for
example have P2P turned on.

How to disable that limit, if you could help me i will be very
gratefull

Thanx in advance

Don't think its a connection limit issue if you are running Windows 2003
Server. It is a server, so in theory, there is an unlimited amount of
connections that it can handle. Maybe the problem is something else.
Can't say what it is however.

Luki wrote:
> I have set routing with NAT translating.
> It is working fine but problems starts when there are lot conections to
> that server - seems there are limit somewhere. It is not letting some
> clients to connect to public network if there is someone who for
> example have P2P turned on.
>
> How to disable that limit, if you could help me i will be very
> gratefull
>
> Thanx in advance
>

On Dec 15, 6:07 pm, Kirrin Jones <kirrinjo...@gmail.com> wrote:
> Don't think its a connection limit issue if you are running Windows 2003
> Server. It is a server, so in theory, there is an unlimited amount of
> connections that it can handle. Maybe the problem is something else.
> Can't say what it is however.

Well why some clients start to getting access to public network after I
turn off that connections from P2P?
If mappings on public interface is low - all is ok. But if there are
like 200-300 mappings some clients cant get out

In news:(E-Mail Removed) oups.com,
Luki <(E-Mail Removed)> stated, which I commented on below:
> On Dec 15, 6:07 pm, Kirrin Jones <kirrinjo...@gmail.com> wrote:
>> Don't think its a connection limit issue if you are running Windows
>> 2003 Server. It is a server, so in theory, there is an unlimited
>> amount of connections that it can handle. Maybe the problem is
>> something else. Can't say what it is however.
>
> Well why some clients start to getting access to public network after
> I turn off that connections from P2P?
> If mappings on public interface is low - all is ok. But if there are
> like 200-300 mappings some clients cant get out

This is not a server limit, but it is probably taxing the server since you
are using it as a gateway. P2P is a heavy traffic utilizer. I wouldn't even
allow it in a production enviornment.

If the server you are using for NAT is a DC, I would honeslty consider to
purchase a router to use instead of using the DC for this function, for two
reasons: 1) exposing the DC to the internet, 2), multihomed DCs are very
problematic without configuring them properly and altering their default
functionality to work in this scenario.

--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

On Dec 16, 10:53 pm, "Ace Fekay [MVP]" <PleaseAs...@SomeDomain.com>
wrote:
> This is not a server limit, but it is probably taxing the server since you
> are using it as a gateway. P2P is a heavy traffic utilizer. I wouldn't even
> allow it in a production enviornment.
> If the server you are using for NAT is a DC, I would honeslty consider to
> purchase a router to use instead of using the DC for this function, for two
> reasons: 1) exposing the DC to the internet, 2), multihomed DCs are very
> problematic without configuring them properly and altering their default
> functionality to work in this scenario.

Im noob at networking :P

Well i removed addictional IPs from NAT pool and when it works on only
server IP it is ok, still it is strange...

In news:(E-Mail Removed) oups.com,
Luki <(E-Mail Removed)> stated, which I commented on below:

> Im noob at networking :P
>
> Well i removed addictional IPs from NAT pool and when it works on only
> server IP it is ok, still it is strange...

Not from the NAT pool, I mean to disable the additional NIC completely and
just use the internal NIC. Multihomed Active Directory domain controllers
are very problematic. Use a Router for internet connectivity to your ISP.

Ace