We get wrong data of our traffic when NAT service is working

[Sage]

We get wrong data of our traffic when NAT service is working.
There are mixed data of incom and outcom traffic in the users' properties and logs.
I suppose that everything would be good if all the rest services would work properly together.
Please do me a favour from technical support to consider this problem.
We Ask the gentlemen from technical support to consider the givenned question.

Thank you for advance.

[genie]

What kind of traffic did you see? Was it HTTP page corrupted or broken file data while copying?

[Sage]

Your program confuses data of incom and outcom ip traffic in the log files and in the page of user properties "accounting" -> "Bytes recived for client" ("Bytes send to client").

My WinGate version is 5.10

[genie]

How big was the difference? Also, what kind of other accounting software you were using to compare this data?

[Sage]

For example i download file (6 Mb) using NAT service, after this I look at the user properties in "Accounting" page and see "Bytes recived for client"=1000 bytes; "Bytes recived from client"=6291456. The same situation with log files!!!

[genie]

Ok, thanks for letting us now - just one more question:
I take it you downloade this file using FTP? If this was the case, what FTP mode did you use: active or passive? or what kind of client did you use?

[Sage]

I don't use "WinGate client", there is Windows 2000 with SP2 or higher on our client stations.
WinGate server is installed on Windows 2000 Server with SP4 (with sevice pack 2 before).

[Sage]

It is not depend on what protocol I use, the situation is the same.

[adrien]

OK, thanks for this info - Gene's question came about because with FTP, if you use PASV, then the data connection is made by the client to the server, however if you use FTP with normal (PORT) connection, then the server connects to the client for the data... if you had been using FTP to download this file, then it could have made a difference how your FTP client software was configured.

Thanks

Adrien

[genie]

Aye, this was my point exactly - Slava, any additional info would greately help us solve this problem.

[mikebos]

Hi Adrien and Genie,
Found the exact same problem as Slava, with major inability to charge client for downloaded traffic.
My clients are using Kazaa with the default settings which uses NAT.
In all cases Server Recv data is reported as Server Send in accounting and logs, and we are talking GB's. Here is one client log.
Timestamp Username Client Send (b) Client Recv (b) Server Send (b) Server Recv (b)
11/01/2003 0:00 Alvin 151,364,342 1,623,324,195 1,623,182,250 150,053,636
Regards
Mike Bos

[genie]

The problem is fixed in the new release....

[Sage]

OK!!! Thanks!!!

[mikebos]

Hi,

So ENS-NAT can distinguish between client settings for PASV and PORT traffic and reports it correctly regardless?

Regards
Mike Bos

[genie]

Erm.... Mike, FTP might be a bit of a pain. We still have things to do there.

[mikebos]

Genie,

I presume Kazaa is using some form of FTP protocol leading to the reporting error, so that when you say it's fixed, it is.

So in traffic reporting what exactly has the latest version fixed.

regards
Mike bos.