Re: TCP Server/Client Q

Giganews Newsgroups
Subject: Re: TCP Server/Client Q
Posted by:  LClark (LCla…@Bytewiser.com)
Date: Fri, 4 Jul 2003

Make sure you assign fixed IP addresses and subnet masks on both machines or
your host address in your client application will be wrong when you change
networks. All I can think of.
If you can PING obviously the network is not down.

L Clark

"J. Clarke" <jclar…@docstorsys.NOSPAMcom> wrote in message
news:5CCA6F35B975E240jclar…@docstorsys.NOSPAMcom...
> (W2K,D7)
>
> Ok, I have an Indy TCP Server & Client application that works great when
I'm
> on my regular network.  But I need to go demo the app someplace, so I got
a
> little 4 port hub.  I connected up both my PCs, signed in on both, changed
> the network properties so both machines were in the same workgroup.  Both
> machines can ping each other just fine.  I run my app & the client can't
see
> the server.  I get a "socket error 10050 network is down" error message
and
> they don't connect.
>
> I figure I'm missing something in my network settings but I'm not sure
what.
> Any suggestions?
>
> Jeff

Replies

In response to

TCP Server/Client Q posted by J. Clarke on Thu, 3 Jul 2003