barba version 7 on win32

May 25, 2013 at 1:18 PM
Hi Dear Coder
congratulations for releasing version 7
how can it be installed on win32
thx
Coordinator
May 25, 2013 at 1:30 PM
Just install it same as other version.
Is there any issue on win32?
Regards
May 25, 2013 at 1:42 PM
in my client which is win64 it installed without any error but in my server which is win 2003 32 it says barbamonitor is not a valid win32 application
Coordinator
May 25, 2013 at 1:47 PM
Hi,
You could not use BarbaMonitor and BarbaService in Windows XP & 2003 because .NET 4.5 could not be installed in these platforms but they are just some UAC and UI helper, Windows XP & 2003 users should run BarbaTunnel.exe manually.
I checked it with windows XP and it worked for me in my Windows XP virtual Machine. I didn't check it on Windows 2003.
Just go to bin folder and run BarbaTunnel.exe, let me know the result.
check: Problem with starting service on windows 2003 R2 32bit
Regards
May 25, 2013 at 1:58 PM
on previous version it was shown on which adapter barba client is working in barba monitor ,but in new version how can it be recognized?i changed adapterindex many times but to no avail.
Coordinator
May 25, 2013 at 2:30 PM
New version find adapter index automatically, just leave it blank,
adapterindex also just valid for WinpkFitler
Regards
May 25, 2013 at 7:59 PM
I did all the procedures .the barba server is running,and barba tunnel monitor on client side is ready too,when I run proxifier there is no reaction from barba monitor and it still remains on idle mode.
Barba Client Started...
Version: 7.0
FilterDriver: WinpkFilter
Adapter: Wireless Network Connection
Ready!
in previous version as soon as I ran proxifier ,barba tunnel started to interact with server
this is config file:
; for information see:
; http://barbatunnel.codeplex.com/wikipage?title=config.ini

[General]
ServerAddress=88.150.135.117
Enabled=1
Mode=HTTP-Tunnel
Key=1234567890ABCDEF
GrabProtocols=GRE:,TCP:1723,ESP:,UDP:1701,UDP:500,UDP:4500
TunnelPorts=80,8080
MaxUserConnections=
FakeFileTypes=jpg,zip

; None | Normal | Bombard
HttpRequestMode=

; In kilobyte
MaxTransferSize=

; In Bytes
MinPacketSize=
Coordinator
May 25, 2013 at 8:27 PM
I don't know about proxifier but is it use same port as PPTP & L2TP? I see you didn't change GrabProtocols=GRE:,TCP:1723,ESP:,UDP:1701,UDP:500,UDP:4500
Also why u don't use VPN?
Regards
May 26, 2013 at 4:46 AM
unfortunately this version dose not work with Iranian latest filtterings methods,neither with proxy nor with vpn
May 26, 2013 at 5:50 AM
there is a problem in capturing packets, there is no reaction when use version 7, but version 6.4 works very well.
May 26, 2013 at 9:33 AM
bemamian wrote:
there is a problem in capturing packets, there is no reaction when use version 7, but version 6.4 works very well.
are you behind Iran firewall?
with version 6.4 used to work flawless but these days it connects and disconnects repeatedly,maybe it differs from ISP to ISP
May 26, 2013 at 10:16 AM
Edited May 26, 2013 at 10:22 AM
please pay attention dear friend "alimomen"

I told that the client does not have any reaction about capturing the packets!!!
After client captures the packets, THEN trying to send them to server and in this part IRAN FILTERING is engaging ;-)

In version 6.4, If you turned off the server, you can see the client is capturing the packets, but there is no response from server, but in new version 7, you can see any capturing packet!?!
Coordinator
May 26, 2013 at 2:32 PM
bemamian wrote:
there is a problem in capturing packets, there is no reaction when use version 7, but version 6.4 works very well.
Hi
I think it may some problem in PacketFilter Driver. Please change it and make sure the server IP and GrabProtocols setup properly.
Please disable other HTTP config.
Maybe you don't install new BarbaMonitor and you don't see any log. Make sure you install 7.0 in both side.
Is there anyone have such issue?
May 26, 2013 at 7:07 PM
Hi

my server works very well with 6.4. I uninstalled 6.4 and close BarbaMonitor, then install version 7 in both sides, but client does not capture any packet, I testes both PacketFilter Drivers in client side, but there wasn't any reaction to grab packets.

I uninstalled version 7 and installed version 6.4 again and it works perfectly.
May 26, 2013 at 7:30 PM
bemamian wrote:
there is a problem in capturing packets, there is no reaction when use version 7, but version 6.4 works very well.
you mean this decrease speed tunnel will be fix with version 6.4 ?
May 26, 2013 at 7:31 PM
bemamian wrote:
Hi

my server works very well with 6.4. I uninstalled 6.4 and close BarbaMonitor, then install version 7 in both sides, but client does not capture any packet, I testes both PacketFilter Drivers in client side, but there wasn't any reaction to grab packets.

I uninstalled version 7 and installed version 6.4 again and it works perfectly.
Your speed Limit fixed with version 6.4 ?
May 26, 2013 at 7:43 PM
Edited May 26, 2013 at 7:45 PM
Mehranexpert wrote:
bemamian wrote:
there is a problem in capturing packets, there is no reaction when use version 7, but version 6.4 works very well.
you mean this decrease speed tunnel will be fix with version 6.4 ?
NO, there is no relation between capturing packets and speed, I said simple, version 7 does not work at all in my PC

مهران جان کار نمیکنه ورژن 7 برای من، چه ربطی به سرعت داره؟ اصلا کار نمیکنه
ورژن 6.4 قشنگ کار میکنه
Coordinator
May 26, 2013 at 7:56 PM
bemamian wrote:
Hi

my server works very well with 6.4. I uninstalled 6.4 and close BarbaMonitor, then install version 7 in both sides, but client does not capture any packet, I testes both PacketFilter Drivers in client side, but there wasn't any reaction to grab packets.

I uninstalled version 7 and installed version 6.4 again and it works perfectly.
Sorry, currently not have more idea.
Regards
May 26, 2013 at 8:01 PM
bemamian wrote:
Mehranexpert wrote:
bemamian wrote:
there is a problem in capturing packets, there is no reaction when use version 7, but version 6.4 works very well.
you mean this decrease speed tunnel will be fix with version 6.4 ?
NO, there is no relation between capturing packets and speed, I said simple, version 7 does not work at all in my PC

مهران جان کار نمیکنه ورژن 7 برای من، چه ربطی به سرعت داره؟ اصلا کار نمیکنه
ورژن 6.4 قشنگ کار میکنه
منظوزت از اینکه کارنمیکنه جیه ؟ برای من کارمیکنه
فقط افت سرعت دارم البنه الان خوبه
میخوام ببینم روی 6 سرعتت چطوریه ؟
Coordinator
May 26, 2013 at 8:15 PM
Edited May 26, 2013 at 8:15 PM
bemamian wrote:
Hi

my server works very well with 6.4. I uninstalled 6.4 and close BarbaMonitor, then install version 7 in both sides, but client does not capture any packet, I testes both PacketFilter Drivers in client side, but there wasn't any reaction to grab packets.

I uninstalled version 7 and installed version 6.4 again and it works perfectly.
What is your BarbaTunnel.exe timestamp and when you download it?
I remind that I upload version 7 with such bug and only 9 people download it. I replace it immediately. Maybe you are one of them. Would you download it again and let me know is it solve the issue or not?

Also I test it on Win32 again and it grab packets.
Regards
May 27, 2013 at 3:15 AM
I have the same problem,client shows no reaction in capturing packets,I think has some bugs
Coordinator
May 27, 2013 at 6:26 AM
alimomen wrote:
I have the same problem,client shows no reaction in capturing packets,I think has some bugs
Unfortunately "Not working" does not help me to solve the issue, i need to fill my checklist.
  1. Would you donwload BarbaTunnel again, I update it without notify it in initial release 7.0
  2. Would you set log level to 3 and Send me the barba client log.
Regards
May 27, 2013 at 1:31 PM
Edited May 27, 2013 at 1:32 PM
Hi

I've heard that "The early bird catches the worm" but this time I caught the bug :-P

I downloaded again version 7.0 and It works as perfect as version 6.4, but I think the bandwidth is not like version 6.4, I must test more
Coordinator
May 27, 2013 at 6:30 PM
Version 7.0 HTTP tunnel with Normal HttpRequestMode should be little better than older versions, but if you set HttpRequestMode to Bombard (this feature does not exists in older version) then it should be 20%~30% slower than normal mode depending you upload speed.
Cheers
May 28, 2013 at 6:59 PM
BarbaCoder wrote:
alimomen wrote:
I have the same problem,client shows no reaction in capturing packets,I think has some bugs
Unfortunately "Not working" does not help me to solve the issue, i need to fill my checklist.
  1. Would you donwload BarbaTunnel again, I update it without notify it in initial release 7.0
  2. Would you set log level to 3 and Send me the barba client log.
Regards
I reinstalled it the problem still exist.here is the log:
BarbaCourier: TID: 1578, SessionId: e2af75c9, Opening TCP Connection for HTTP POST connection. RemotePort: 80.
BarbaCourier: TID: 157c, SessionId: e2af75c9, Opening TCP Connection for HTTP POST connection. RemotePort: 8080.
BarbaCourier: TID: 1588, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: 1588, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: fc0, SessionId: e2af75c9, Error: No connection could be made because the target machine actively refused it.
BarbaCourier: TID: fc0, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 14e4, SessionId: e2af75c9, Opening TCP Connection for HTTP GET connection. RemotePort: 80.
BarbaCourier: TID: 1580, SessionId: e2af75c9, Opening TCP Connection for HTTP GET connection. RemotePort: 8080.
BarbaCourier: TID: b3c, SessionId: e2af75c9, Opening TCP Connection for HTTP POST connection. RemotePort: 8080.
BarbaCourier: TID: 1578, SessionId: e2af75c9, Error: No connection could be made because the target machine actively refused it.
BarbaCourier: TID: 1578, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 14e4, SessionId: e2af75c9, Error: No connection could be made because the target machine actively refused it.
BarbaCourier: TID: 14e4, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 158c, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: 158c, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 157c, SessionId: e2af75c9, Error: No connection could be made because the target machine actively refused it.
BarbaCourier: TID: 157c, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 55c, SessionId: e2af75c9, Opening TCP Connection for HTTP POST connection. RemotePort: 8080.
BarbaCourier: TID: 1588, SessionId: e2af75c9, Opening TCP Connection for HTTP POST connection. RemotePort: 80.
BarbaCourier: TID: 1580, SessionId: e2af75c9, Error: No connection could be made because the target machine actively refused it.
BarbaCourier: TID: 1580, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: fc0, SessionId: e2af75c9, Opening TCP Connection for HTTP GET connection. RemotePort: 8080.
BarbaCourier: TID: 1578, SessionId: e2af75c9, Opening TCP Connection for HTTP POST connection. RemotePort: 8080.
BarbaCourier: TID: 14e4, SessionId: e2af75c9, Opening TCP Connection for HTTP GET connection. RemotePort: 80.
BarbaCourier: TID: 158c, SessionId: e2af75c9, Opening TCP Connection for HTTP GET connection. RemotePort: 8080.
BarbaCourier: TID: 158c, SessionId: e2af75c9, Error: No connection could be made because the target machine actively refused it.
BarbaCourier: TID: 158c, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: b3c, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: b3c, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 14e4, SessionId: e2af75c9, Error: No connection could be made because the target machine actively refused it.
BarbaCourier: TID: 14e4, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 868, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: 868, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 157c, SessionId: e2af75c9, Opening TCP Connection for HTTP POST connection. RemotePort: 80.
BarbaCourier: TID: 55c, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: 55c, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 1580, SessionId: e2af75c9, Opening TCP Connection for HTTP GET connection. RemotePort: 8080.
BarbaCourier: TID: 1588, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: 1588, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: fc0, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: fc0, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 158c, SessionId: e2af75c9, Opening TCP Connection for HTTP GET connection. RemotePort: 8080.
BarbaCourier: TID: b3c, SessionId: e2af75c9, Opening TCP Connection for HTTP POST connection. RemotePort: 80.
BarbaCourier: TID: 14e4, SessionId: e2af75c9, Opening TCP Connection for HTTP GET connection. RemotePort: 8080.
BarbaCourier: TID: 868, SessionId: e2af75c9, Opening TCP Connection for HTTP GET connection. RemotePort: 8080.
BarbaCourier: TID: 14e4, SessionId: e2af75c9, Error: No connection could be made because the target machine actively refused it.
BarbaCourier: TID: 14e4, SessionId: e2af75c9, Retrying in 10 second...
BarbaTunnel Stopping.
BarbaTunnel Stopped.
BarbaCourier: TID: 1508, SessionId: e2af75c9, BarbaCourier disposing.
BarbaCourier: TID: 1578, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: 1578, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 158c, SessionId: e2af75c9, Error: No connection could be made because the target machine actively refused it.
BarbaCourier: TID: 158c, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 157c, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: 157c, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 1580, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: 1580, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: b3c, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: b3c, SessionId: e2af75c9, Retrying in 10 second...
BarbaCourier: TID: 868, SessionId: e2af75c9, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BarbaCourier: TID: 868, SessionId: e2af75c9, Retrying in 10 second...
Coordinator
May 28, 2013 at 7:50 PM
client shows no reaction in capturing packets
So, What you mean by that!!! It look it capture packet but couldn't connect to your server, it does not mean "no reaction in capturing packets". So
  1. Did you update your server to version 7.0?
  2. Are you sure you have same key in both side?
  3. Set TunnelPorts=80 and remove 8080
  4. Please send log of server too.
    Regards
May 29, 2013 at 4:25 AM
Edited May 29, 2013 at 4:27 AM
Hi dear Coder
I updated both client and server to version 7(the newest one which u advised)
both the keys are the same
I set the port to 80 only on server and client
As I use win 2003 server so I don't have barba monitor to send u the server logs(are the loges saved in a file in a specific path on the server side?)
the problem still available and no change in client log occured
cheers
Coordinator
May 29, 2013 at 6:12 AM
You can find it here:
C:\ProgramData\Barbatunnel\report.txt

I check your log again, such thing is impossible unless even if you key is invalid
  1. You set invalid server address from client.
  2. Your BarbaServer does not listen to port 80
  3. Your Local firewall (Windows Firewall) block BarbaTunnel 7.0 to access network in one or both site. I recommend you temporary turn-off windows firewall from both side.
As you see tcp connection is not established, no enterprise firewall in the world exists to block the connection in this step.
Regards
May 29, 2013 at 9:21 AM
this path doesnot exist ,maybe because I use server 2003 and I havnt installed barba and I just start it from bin folder
I am dead sure that address is correct and firewall is off and keys are the same
thx
Coordinator
May 29, 2013 at 9:29 AM
The file generated by BarbaTunnel.exe not monitor and it should be exists, i think differ in Windows 2003 server. try:
C:\Documents and Settings\All Users\Application Data\BarbaTunnel
Regards
May 29, 2013 at 11:25 AM
barba server didn't know what interface should be chosen,now it works like charm,thanks a lot for your great work and patience.just plz mention what configurations should be used for UDP tunnel
Coordinator
May 29, 2013 at 11:33 AM
barba server didn't know what interface should be chosen
I like to know error message of that and how you find it?
just plz mention what configurations should be used for UDP tunnel
Just enable all config (utp,tcp,http) on server side and now just enable the one you like in client side.
server can accept any type but client should be configured just for 1 for each server
set Enabled=1 or 0 in config.ini
cheers
May 29, 2013 at 11:47 AM
I think just the problem is slow connection,is there any way to boost it?
Coordinator
May 29, 2013 at 11:50 AM
if udp tunnel is so slow you can just use HTTP tunnel and increase MaxUserConnections.
Currently no other chance with barba tunnel.
cheers
May 29, 2013 at 12:10 PM
what should be the MaxUserConnection?i mean to what number should it be set
Coordinator
May 29, 2013 at 12:13 PM
for 4Mbit coonection set it to 20