Urgent! Winsock Problem
-
Hi all, I am doing my final year project on Pocket PC. I want to set up a Client-Server communication between Pocket PC iPAQ h5400 series (Pocket PC 2002) (server) and a desktop computer (Windows 2000) (client). I use Embedded Visual C++ 3.0 and MFC dialog to implement. I firstly implement it using TCP protocol but I got a winsock error 10061 (Pocket PC 2002 Emulator) and even get 10060 when directly connected to the iPAQ h5400 series using USB) sckConnectionRefused 10061 Connection is forcefully rejected. sckTimedout 10060 Socket has been shut down. The server and client codes are referenced from MSDN at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm/htm/\_wcesdk\_TCP\_Stream\_Socket\_Server.asp . The main problem is that the server cannot get any message from the client and wait at the Accept call and halt the program. (When using emulator)à I find that the specific port 5000 is not listening by using netstat on Windows 2000 after the program has reached the Accept call. So can anyone kindly help to solve the problem? On the other hand, I implement it using UDP protocol but the server still can’t receive any message from the client. The codes are referenced from MSDN at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm/htm/\_wcesdk\_TCP\_Stream\_Socket\_Server.asp also. Furthermore, is there any method in Pocket PC that can check connection like “netstat” in Windows OS for ports?? It’s really urgent as I have to hand it before 26/3/2003 so please kindly help me. Many thanks!!! Wil
-
Hi all, I am doing my final year project on Pocket PC. I want to set up a Client-Server communication between Pocket PC iPAQ h5400 series (Pocket PC 2002) (server) and a desktop computer (Windows 2000) (client). I use Embedded Visual C++ 3.0 and MFC dialog to implement. I firstly implement it using TCP protocol but I got a winsock error 10061 (Pocket PC 2002 Emulator) and even get 10060 when directly connected to the iPAQ h5400 series using USB) sckConnectionRefused 10061 Connection is forcefully rejected. sckTimedout 10060 Socket has been shut down. The server and client codes are referenced from MSDN at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm/htm/\_wcesdk\_TCP\_Stream\_Socket\_Server.asp . The main problem is that the server cannot get any message from the client and wait at the Accept call and halt the program. (When using emulator)à I find that the specific port 5000 is not listening by using netstat on Windows 2000 after the program has reached the Accept call. So can anyone kindly help to solve the problem? On the other hand, I implement it using UDP protocol but the server still can’t receive any message from the client. The codes are referenced from MSDN at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm/htm/\_wcesdk\_TCP\_Stream\_Socket\_Server.asp also. Furthermore, is there any method in Pocket PC that can check connection like “netstat” in Windows OS for ports?? It’s really urgent as I have to hand it before 26/3/2003 so please kindly help me. Many thanks!!! Wil
Hi Wil The problem is that there are no routing tables set up to route IP connections from the PC to the PocketPC through ActiveSync. In other words, IP cannot find a way through to the PocketPC. The IP connectivity over ActiveSync has been set up to allow routing from the device to the PC. So if you set up a listening socket on the PC instead of the device, you should find that the device can connect to that. If you definitely need the listening socket on the device, then you'll either have to set up the routing tables on the PC or test over a proper network connection, not the cradle. Hope that helps, MikeS.
-
Hi Wil The problem is that there are no routing tables set up to route IP connections from the PC to the PocketPC through ActiveSync. In other words, IP cannot find a way through to the PocketPC. The IP connectivity over ActiveSync has been set up to allow routing from the device to the PC. So if you set up a listening socket on the PC instead of the device, you should find that the device can connect to that. If you definitely need the listening socket on the device, then you'll either have to set up the routing tables on the PC or test over a proper network connection, not the cradle. Hope that helps, MikeS.