Now.WAP Proxy v2009 (setup)

Now.WAP Proxy v2009 (setup) SearchSearch

SMS & MMS Technical Forum » Now.WAP Proxy (Product Support Only) » Now.WAP Proxy v2009 (setup) « Previous || Next »
Author Message
PHILIP TEO
New member
Username: Philip_teoph

Post Number: 6
Registered: 02-2009
Posted on Monday, January 25, 2010 - 08:20 am:   

Hi,

I setup a Tomcat Server and NowWAP Proxy (v2009.7.21) on my notebook (Windows XP Pro SP2) and use WinWAP for Windows 4.2 browser, it works perfectly.

But, when I setup on abovementioned software in Windows 2003 Server R2 Standard Edition SP2, it didn't work (with same setting).

Can you help me?

Thanks.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1711
Registered: 08-2008
Posted on Monday, January 25, 2010 - 01:16 pm:   

Hi Philip,

My first suspicion would be the Windows Firewall.

Add an exception for WAP3GXS.EXE and WAP3GXS64.EXE, or add an exception for the ports (UDP ports 9200 and 9201, plus whatever port is configured as the HTTP proxy).

--
Des
NowSMS Support
PHILIP TEO
New member
Username: Philip_teoph

Post Number: 7
Registered: 02-2009
Posted on Thursday, January 28, 2010 - 03:23 am:   

Hi Des,

I have check the window firewall and realise that the Server is configure as VPN Server (RRAS take over window firewall).

In order not to mess up the VPN setting, I have created a clean virtual Machine (VM) using VM Player for Windows 2003 Standard Edition R2 with all latest patches.

[Software Installation]

The software installed in clean VM are as follows:

1. Apache Tomcat 6.0.20 Server
* using default port 8080
* modify web.xml for wap

2. Now.WAP Proxy v2009.07.21
* Service TAB
Ticked - Run as a Service
* Options TAB
Un-ticked - Route connections via external HTTP Proxy Server
Un-ticked - IP Address Restrictions
* HTTP TAB
Ticked - Enable HTTP (WAP2) Proxy
HTTP Proxy Port : 8080
Ticked - Enable Compression
Ticked - Enable WML/WMLScript Complier
Ticked - Enable WTCP Extensions
Ticked - Allow SSL/TLS Tunnel to non-standard ports
Max Keep-Alive for Client Connections : 300 sec
Max Keep-Alive for Server Connections : 90 sec
Un-ticked - Throttle MM1 (MMS) Send Transactions
* MSISDN TAB
Un-ticked - Activate Radius Accounting for MSISDN Collection
* Users TAB
Un-ticked - Access to HTTP Proxy
Un-ticked - Access to WAP/WSP Proxy
Un-ticked - Authentication via built-in RADIUS Server
* Reports
Un-ticked - Generate Usage Reports
* Serial #
<no changed>

3. WinWAP for Windows 4.2
Select Edit -> Options
* General TAB
Connection mode : Gateway mode
* HTTP TAB
Un-ticked all
* Gateway TAB
Gateway IP/Host name : localhost
Connection Port / Mode : 2 Connection oriented port 9201

[Test Cases]

P1. "My first suspicion would be the Windows Firewall."

T1. I have disabled Windows Firewall / ICS service but not successful.

T2. I try to enable Windows Firewall / ICS service.
a) Add program exception for all executabless in NowWAP directory (including WAP3GXS.EXE and WAP3GXS64.EXE)
b) Add ports exception for UDP ports 9200, 9201, 9202 and 9203 plus udp port 8080 configured as the HTTP proxy.

Result : The Now.WAP Proxy on the Windows 2003 Standards R2 VM did not show in Service Information non-editable text box in Service TAB that it registered Users and detect Requests as in Windows XP Pro SP2 on my notebook when I use WinWAP browser to access the web pages.

Any suggestion or any steps that I have miss out?

Thank you in advance.

Regards,
Philip
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1731
Registered: 08-2008
Posted on Thursday, January 28, 2010 - 03:07 pm:   

Hi Philip,

I did some testing, and it appears that the 64-bit version is having problems in some VM environments.

While we investigate this, there is a simple work-around.

Stop the NowWAP service.

Delete WAP3GXS64.EXE from the Program Files (x86)\NowWAP directory.

Start the NowWAP service.

I'll post some follow-up when we have further identified the problem, but this should be a sufficient work-around.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1735
Registered: 08-2008
Posted on Friday, January 29, 2010 - 01:53 pm:   

Follow-up. A fix for this problem with the 64-bit version is available at http://www.nowwap.com/download/wapgw201001.zip.


--
Des
NowSMS Support
PHILIP TEO
New member
Username: Philip_teoph

Post Number: 8
Registered: 02-2009
Posted on Monday, February 01, 2010 - 08:14 am:   

Hi Des,

Thanks for your file.

I downloaded and try it on my Windows 2003 R2 VM with NowWAP, but the result is the same (not successful). Please also note that I am using 32-bit instead of 64-bit version of NowWAP.

Attached please find the exported services of the VM and hope it will help in the troubleshooting. Do I need disable more services?

Thanks.

Regards
Philip Teo
text/plainWindows Server 2003 Standard R2 Services
services.txt (26.7 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1737
Registered: 08-2008
Posted on Monday, February 01, 2010 - 08:42 pm:   

Hi Philip,

I don't know what the problem could be then.

There was clearly a problem with the 64-bit version in most VM environments. However, I am not seeing any problems with the 32-bit versions.

Deleting the WAP3GXS64.EXE file above will ensure that the 64-bit is not running.

I'm not sure what else to try or suggest.

That said ... in all of my tests, I was trying WinWap running on a separate machine.

I wouldn't rule out a problem with WinWap.

I can't get WinWap to connect to any WAP gateway in "gateway" mode when I run it on a Windows 7 PC.

My original tests had NowWAP running on a Windows 7 PC.

I was using WinWap on a separate Windows XP PC.

Now I've done more tests. I installed NowWAP on the XP PC. WinWap on the XP PC can use localhost NowWAP or external NowWAP in gateway mode with no problem.

WinWAP on W7 PC CANNOT use localhost NowWAP or external NowWAP in gateway mode. (HTTP mode is no problem.)

I've now also installed WinWap on a Windows 2003 Server PC, and I can't get it to work there either.

That said, in my attempts, I do see activity on the NowWAP screen when WinWap on W2003 tries to connect. And if I do a WireShark trace, I see that WinWap keeps trying to connect, and NowWAP keeps trying to send connect replies. It appears that WinWap is not seeing the reply. I tried disabling the W2003 firewall, and it still did not work.

When I try with a gateway and WinWap on the same PC with either W2003 or W7, I see no activity on the NowWAP console, and unfortunately, WireShark cannot intercept localhost data.

It doesn't look like a NowWAP problem. It looks like WinWap has some sort of problem with "gateway modem" when WinWap is running on Windows 7 or Windows 2003 Server. WinWap running on Windows XP works great.

Unfortunately, I don't think there's much more that I can suggest. I'm not seeing anything that looks like a NowWAP problem here (apart from the original 64-bit version problem that I observed).

--
Des
NowSMS Support
PHILIP TEO
New member
Username: Philip_teoph

Post Number: 9
Registered: 02-2009
Posted on Friday, February 19, 2010 - 05:02 am:   

I have use OpenWave V7 Simulator instead of WinWAP for my testing.

It works!

Thank you for your support.

===

Now I want to use Nokia E72 handphone to access the WAP page.

Do you have an idea how to configure the handphone to force it to access WAP page via NowWAP gateway?

(Note: access direct WAP page via Tomcat Server has no problem, but we need WAP gateway for performance purpose).

Thank you.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1822
Registered: 08-2008
Posted on Friday, February 19, 2010 - 08:08 pm:   

Hi Philip,

In Nokia S60 phones, they generally refer to this as configuring the access point for MMS messaging. At least that's how I'd say it in Nokia-speak.

From the menu you go into Messaging, select Options, Settings, Multimedia Message, Access Point ... and then you need to create or edit an access point.

Your access point is going to include information such as the GPRS APN, WAP Gateway IP address, and for MMSC settings, the "Homepage" setting has the URL for the MMSC.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1823
Registered: 08-2008
Posted on Friday, February 19, 2010 - 08:12 pm:   

Oops ... Philip ... I'm sorry, I've got MMSCs on the brain today.

I see your question has nothing to do with MMS, you're just talking about the browser.

To configure this, you want to go into Internet, Web, Options, Settings. This is where you can configure the Access Point that is used by the browser. The access point settings include a GPRS APN, WAP Gateway IP address and port. The Nokia E72 does NOT support WAP1/WSP, so you must specify the WAP2/WHTTP port number that has been configured for NowWAP.

--
Des
NowSMS Support

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics