| Port 8080 works, but ports 9201 and 9203 are unresponsive |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through October 01, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Jack Krupansky New member Username: Jackk Post Number: 1 Registered: 06-2006 |
The Now.WAP WAP gateway server software doesn't seem to be responding to attempts to connect on ports 9201 and 9203 for WAP 1.2. Port 8080 (for WAP 2.0) seems to work fine. There are no messages in WAPDEBUG.LOG that indicate a failed connection even though I see messages for the 8080 connection. I verified with a network monitor that TCP acknowledges receipt of attempted connections on ports 9201 and 9203. In fact, if I temporarily change the HTTP/WAP2 port to 9201, it works fine (for WAP 2.0). So I'm confident that frames are being sent to ports 9201 and 9203. I use telnet to verify whether a port can be connected to. It times out after about half a second and says that the connection failed. I've tried it over the LAN and from the gateway server machine locally ("telnet 127.0.0.1 9201"). Version: 2.58 and 2.57 Windows XP -- Jack Krupansky | |||
| Jack Krupansky New member Username: Jackk Post Number: 2 Registered: 06-2006 |
Can you offer an alternative way to quickly and easily verify from another host computer on the LAN (as well as on the local host computer) that Now.WAP is listening to ports 9201 and 9203? Also, could you verify whether there is any possible way that support for WAP 1.2 could be disabled? We don't need to disable it (at this time), but we do need to be able to verify that support for WAP 1.2 has not been disabled somehow. Thanks. -- Jack Krupansky, Customer | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6141 Registered: 10-2002 |
Jack, The WAP/WSP protocol uses UDP, not TCP. So you can't connect to it over Telnet. It also makes it very difficult to determine if there is a problem. When there is a problem like this, it is usually one of two things: 1.) Another application has already grabbed these UDP ports. This is very rare, but the Nokia SDK includes a WAP gateway simulator that only accepts requests from the local emulator. That WAP gateway simulator can get in the way, but the simulator is usually only loaded while the SDK is running. 2.) Firewall issues. Opening up a firewall for UDP is different than opening it for TCP. If #1 is a problem, then you'd usually see an error in WAPDEBUG.LOG during startup. There would be an error about binding to a socket. 3.) As I think about it, there is one other potential issue, so let's add a #3 ... but it is usually only a problem when you have a dynamic network connection. It's worth a try though ... edit WAPGW.INI, and under the [WAPGW] header, add BindWildcardIP=Yes ... I wouldn't expect this setting to make a difference, but in some specialised network environments it can. As for verifying from another host computer whether or not the port is actually available and listening ... I don't have any suggestions. If there is no error in the log, then it is listening (there is no way to disable it). However, from the computer itself, you can use the NETSTAT command line utility. Issue the command NETSTAT -a , and you should see the proxy listening for UDP on the relevant ports. If you stop the service, those listening ports should go away ... restart the service, they should come back. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6142 Registered: 10-2002 |
P.S. - I did just think of a way to test it from another computer. You could use NowSMS ... Go to the "MMSC Routing" tab in NowSMS, and press "Add". Specify "Account Name" = "test" "Route messages to VASP via" = "MM1" Check "Use Specific network connection (GPRS modem)" "Network Connection" = "Network: Local Area Connection" "WAP Gateway IP Address" = ip you want to test Press "Test Connection" ... If all is well, NowSMS should report that the connection test is ok, and you should see activity in WAPDEBUG.LOG. -bn | |||
| Jack Krupansky New member Username: Jackk Post Number: 3 Registered: 06-2006 |
Thanks for the NETSTAT tip. That does the test that I wanted, albeit locally. But... It shows THREE copies of each of 9200 and 9201, all for the same process. If I add the BindWildcardIP=Yes to WAPGW.INI and restart the gateway I see only one pair of 9200/9201 UDP listeners. But, the gateway is still unresponsive to incoming requests for port 9201 (our WSP client retries 8 times, every 5 seconds). I have a NETMON capture that shows the incoming UDP frames that have 9201 as their destination port. Two questions... 1) Is there any .INI setting to get the gateway to log that a UDP message had been received from port 9201 evenif it cannot be processed for some reason, and what that reason is? 2) NETSTAT does not show a Now.WAP listener for port 9203 (WTLS). Does that mean that our server doesn't have WTLS support? How can I get/enable WTLS support? Thanks. -- Jack Krupansky, Customer | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6168 Registered: 10-2002 |
Yes, that is what I would expect. The default setting includes some unusual behaviour to deal with some quirks of old phones. It is normal.
If any data is received on that UDP port (valid or invalid), it will be logged to WAPDEBUG.LOG ... showing the source IP and a hex dump of the data. If it is invalid, there might also be some explanation of what is wrong. However, if any data is received, it will be logged.
WTLS support is licensed separately. What you might want to do is get a copy of Ethereal ... with the WinPCap driver ... load that, and it should also show you that no data is being received. It might help you do some troubleshooting, but my suspicion is that the network connection between the device and the PC is not routing UDP, or there is a firewall issue. | |||
