Folks - I'm a little stumped by this one. I'm using NetLib (on the Symbol SPT-1740). Things seem to operate fairly smoothly the first time I connect to a host, but for some reason when I call NetLibSocketBind, I get a client port of 1. In other words, when I make a client socket connected to a remote server, I'm connecting from port 1. In the first place, this shouldn't be happening; I shouldn't be getting a reserved port number. What's stranger, though, is that when I connect a second time, I'm *still* getting local port 1. The Palm immediately gives me a netErrTimeout error (even though it's not waiting for the timeout), and the NetLibSocketConnect fails. What's even stranger than this is that the remote server gets a connection from the Palm, but then the socket hangs. I'd appreciate any thoughts or advice. Could this be a result of my application stack getting too large? Thanks, Ben Flaumenhaft
