Have you taken into account the fact that the Winsock control operates
asynchronously and thus releases the execution point back to your code
instantly after sending something?

If you send something, and then before the thing gets finished sending (and
a SendComplete event occurs), you send something else, it will cancel the
original transmission.  Thus, the reason it may work at home is because your
home network is faster and less saturated (and/or perhaps your computer is
slower).  The messages are getting sent before another Send method is
executed.

Anyway, if this is the case, you will have to build a Send State Machine
that sort of acts as a stopper and doesn't let new data get sent until the
SendComplete event gets fired.  Either that, you might investigate 3rd party
Winsock controls.  As I understand it, the free Socketwrench from Catalyst
Development Corporation supports a Send Que of sorts, but I've never tried
it.

I'm not sure about the other question.

--
Howard Henry 'Gawyn Ballpeen' Schlunder
Gawyn Developments; Core developer
http://www.*-*-*.com/ ~hschlund/

Hi,

Sorry for posting twice - I really need a solution to this problem, and I've
had no luck finding one myself so far...  Any comments or suggestions are
appreciated - heck, I'd even be happy if someone just acknowledged that
they'd read the post!

I've written a client/server application for use by an internet cafe style
business.  The clients and server communicate with one another via UDP
across a TCP/IP network.  I have a problem...  On my network at home, where
I developed the app, I have no problems getting the client and server to
talk.  At the site where the app will be implemented, it's a different
story.  Very occasionally, a message from the client will get through...
sometimes, the messages will get through after quite a substantial delay,
appearing in bursts.  The main difference (and it seems to be the key
difference) between my development network and the implementation site's
network is that the computers in the cafe have the network neighbourhood
hidden (using system policies).  If the network neighbourhood is enabled,
the app works fine.  This seems unusual to me, since I'm talking to a
specific IP address - it shouldn't matter whether I can browse for it or
not, surely?  Or does disabling the network neighbourhood icon do more than
simply stop the icon from appearing?  (silly question really!)

Is there a way around this problem?  Do you need more info?

Thanks for any help,

Dion Campbell.

P.S. I also need to count the number of pages a client has sent to the
(single) network printer - any ideas?