Oh yeah, all that was already in place -- I should have mentioned that I am maintaining/expanding someone else's code, and this is in a library function that was working in a lot of other applications.
I have fixed the problem, by the way, in no small part due to your help -- the recommendation of Wireshark alone saved me many hours of fruitless and frustrated staring at the screen. As it turned out, the culprit was the firewall. Turning it off entirely cleared up the problem, so I went in and deleted what turned out to be several contradictory rules concerning the program I am working on, reactivated it, and then let it set it self properly the first time I ran the app afterwards.
I am ze happy.
Thanks again for the advice -- rest assured I am printing it out and storing it in my collection of advice and references.
-- Bob
---------
Then the horns kicked in...
...and my shoes began to squeak.
I have fixed the problem, by the way, in no small part due to your help -- the recommendation of Wireshark alone saved me many hours of fruitless and frustrated staring at the screen. As it turned out, the culprit was the firewall. Turning it off entirely cleared up the problem, so I went in and deleted what turned out to be several contradictory rules concerning the program I am working on, reactivated it, and then let it set it self properly the first time I ran the app afterwards.
I am ze happy.
Thanks again for the advice -- rest assured I am printing it out and storing it in my collection of advice and references.
-- Bob
---------
Then the horns kicked in...
...and my shoes began to squeak.