PDA

View Full Version : Help opening TCP port in basic program- used to, now it won't


MJF
April 21st 03, 11:32 PM
Hi,

We write custom programs in multiuser basic. We have a problem that has
developed on one XP PC that was working fince for months and now has stopped
working. I hope someone can help us on this XP PC (home version).

The exact basic language we use doesn't matter because the task of opening a
TCP port between two PC's (LAN or WAN) is the same in all basic programming
langauges. What happens is this:

1. the server, in our case a W2K Pro, runs a basic program that continuously
'listens' to port 10000 for a request from another basic program on another
PC.

2. If a valid request is received, the server program assigns a TCP port #
(in our case 11000) and sends that port number to the remote PC in a string
varible. The host program opens that same port x and waits for a
connection.

3. The remote PC attempts to open that port in basic code that looks like
this:

100 OPEN (CH)"[tcp]67.167.xxx.xxx;11000"

Remember the server is waiting on port 11000 and when the remote executes
line 100 above, a connection is made. At this point our basic code should
continue and it then runs on the remote side a 'thin-client' app to access
the basic programs and data files.

Here's the problem. Everything has worked fine untill recently on the XP
remote PC. It now hangs on line 100 and is stuck. No error in basic is
generated. It's stuck. Almost as if it did open and then got stuck. But
if it did open, it stopped executing
our basic code right at line 100.

The remote user on the XP PC has no other probems using internet (IE
browser,etc). They use Roadrunner ISP and Roadrunner has confirmed that
they do not block any TCP ports. So what could have created this problem
out of nowhere?

Things we've tried on the remote xp:

-uncheck firewall setting in network properties
-uninstall firewall software (there was none)
-uninstalled NoAds (a pop-up stopper)
-reboot

What might be stopping access to using TCP ports? It worked for months, now
it doesn't (except once for no known reason).

Thanks,
Mike

MJF
April 21st 03, 11:35 PM
I forget to mention that two other remote PC's (that use w98) work ok in our
basic code. They don't get stuck on line 100. That's why we are certain
somethings gone wrong on just this one XP home PC. Mike

MJF > wrote in message
news:4k_oa.560245$L1.162728@sccrnsc02...
> Hi,
>
> We write custom programs in multiuser basic. We have a problem that has
> developed on one XP PC that was working fince for months and now has
stopped
> working. I hope someone can help us on this XP PC (home version).
>
> The exact basic language we use doesn't matter because the task of opening
a
> TCP port between two PC's (LAN or WAN) is the same in all basic
programming
> langauges. What happens is this:
>
> 1. the server, in our case a W2K Pro, runs a basic program that
continuously
> 'listens' to port 10000 for a request from another basic program on
another
> PC.
>
> 2. If a valid request is received, the server program assigns a TCP port #
> (in our case 11000) and sends that port number to the remote PC in a
string
> varible. The host program opens that same port x and waits for a
> connection.
>
> 3. The remote PC attempts to open that port in basic code that looks like
> this:
>
> 100 OPEN (CH)"[tcp]67.167.xxx.xxx;11000"
>
> Remember the server is waiting on port 11000 and when the remote executes
> line 100 above, a connection is made. At this point our basic code should
> continue and it then runs on the remote side a 'thin-client' app to access
> the basic programs and data files.
>
> Here's the problem. Everything has worked fine untill recently on the XP
> remote PC. It now hangs on line 100 and is stuck. No error in basic is
> generated. It's stuck. Almost as if it did open and then got stuck. But
> if it did open, it stopped executing
> our basic code right at line 100.
>
> The remote user on the XP PC has no other probems using internet (IE
> browser,etc). They use Roadrunner ISP and Roadrunner has confirmed that
> they do not block any TCP ports. So what could have created this problem
> out of nowhere?
>
> Things we've tried on the remote xp:
>
> -uncheck firewall setting in network properties
> -uninstall firewall software (there was none)
> -uninstalled NoAds (a pop-up stopper)
> -reboot
>
> What might be stopping access to using TCP ports? It worked for months,
now
> it doesn't (except once for no known reason).
>
> Thanks,
> Mike
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Google