FabulaTech Forum
        (http://www.usb-over-network.com/forum)
      

        Serial Port Solution >> Network Serial Port Kit >> Problem connection (not active)
        
(Message started by: aliceam on Jun 30th, 2005, 10:58pm)
Title: Problem connection (not active)
Post by aliceam on Jun 30th, 2005, 10:58pm
I am uisng the trial version.  My remote computer sees the network port and allows connecting.  The problem is that the host (XP pro) says "waiting for incoming connection" and the remote (2000 server) says (not active).  When I try to use the served port on the remote computer (with any application) It does not open the port. I get a message "the port is not currently available".  I have tried it on different computers.

I have turned off all Firewalls.  The computers are connected via a VPN.

Any ideas?  Thanks.  Miky
Title: Re: Problem connection (not active)
Post by Andrew on Jul 1st, 2005, 5:01am
It seems your shared COM port on the server side is occupied already. To verify that you can try to connect to the server shared COM port via HyperTerminal for example. If you will get the same error, that is problem exactly. Please try to verify then maybe some background application of your server is using this COM port already.
Title: Re: Problem connection (not active)
Post by aliceam on Jul 1st, 2005, 5:34am
It happens on the other machine I am trying it on also.  I verified that the port does not exist on the pc before I map it.  I even used a high number like Com 27 which I know is available and I have the same problem.

Hyperterminal tells me it cannot connect to the network port either.  Says not available. But this is the Network port I created with the software not a physical port.

For example, I will try to use hyperterminal on host machine on com1 and it allows me.  Then I share com1 and when the other machine tries to use it on hyperterminal is says not available to whatever virtual com port I map the host's com1 port.

Thanks for the help. Miky
Title: Re: Problem connection (not active)
Post by Andrew on Jul 1st, 2005, 6:15am
What exact error message do you get while trying to connect to shared COM port?
Title: Re: Problem connection (not active)
Post by aliceam on Jul 1st, 2005, 6:18am
Unable to open COM{whatever port}. Please check your port settings.

I get this no matter what port I select on the remote or whatever computer I try the software on.

I even tried using a different host and a different remote computer and I get the same problem.

Miky
Title: Re: Problem connection (not active)
Post by Andrew on Jul 1st, 2005, 7:06am
Using Hyperterminal can you try to open shared COM port of your server locally (not from remote computer over network)? We need to understand either this error related with server COM port itself or because of some network problems.
Title: Re: Problem connection (not active)
Post by aliceam on Jul 1st, 2005, 7:12am
Yes.  I can open port locally with hyperterminal.

I also tried two computers on the same network segment (no vpn) and also does not work.

I have to be doing something wrong but I don't know what.

Thanks for all your help.

Miky
Title: Re: Problem connection (not active)
Post by Andrew on Jul 1st, 2005, 7:31am
OK, that is network problem. What about MS Windows build-in Firewall (Control Panel -> Security Center -> Firewall) Did you try to disable this firewall as well?
Title: Re: Problem connection (not active)
Post by aliceam on Jul 1st, 2005, 8:53am
Thanks for all your help.

The problem was I was connecting to the remote computer using Terminal Services and working from there.

I connected to the server via VNC and it works fine.

Thanks again, Miky :)
Title: Re: Problem connection (not active)
Post by Greg on Dec 16th, 2005, 6:48am
I have this exact same problem on WinXP SP2. I have tried to use the software both over the network and connecting to a local serial port. The software knows there is a port shared but the status is always "Wait for incoming connection" and "Not Active".

Any ideas?

Greg
Title: Re: Problem connection (not active)
Post by Andrew on Dec 16th, 2005, 7:46am
Maybe shared COM port on the server side is occupied already. To verify that you can try to connect to the server shared COM port directly via HyperTerminal for example. Did you try this?