Opening a TCP port on a WIN2K DC

[Stephen Hartman]

Hi all,

I have a program that requires a port to be open on the server. I run a
netstat -a command and find a port that is listening but is not established.
I then input this port number in the program. What seems to be happening is
that the program starts but then shuts down as if windows won't allow the
prgram to be active on that port. I have had success using port 80. Is
there a procedure I can use to open a port specifically for this program
that is not used for any other purpose? Or am I completely off base. Any
help is appreciated.

Thanks

 

[Andrei Ungureanu [MVP]]

The port shouldn't appear at all in NETSTAT output. Use TCPVIEW or
ACTIVEPORTS to see who is using that port.

--
Regards,
Andrei Ungureanu
www.eventid.net
Test our new EventReader!
http://www.altairtech.ca/eventreader/default2.asp?ref=au

 

[Phillip Windell]

I have a program that requires a port to be open on the server. I run a
netstat -a command and find a port that is listening but is not
established.

Listening is all it is supposed to do. There is nothing else it can do until
something actually connects to the application using that port #.

I then input this port number in the program. What seems to be happening
is
that the program starts but then shuts down as if windows won't allow the
prgram to be active on that port.

The port isn't going to be blocked,...there is nothing in Windows to block
it. But if another Application is already using the port, then this app
isn't going to be allowed to.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
-----------------------------------------------------

 

[Stephen Hartman]

Any advice on how can I manually open a port for this app? I have only
found MS technet advice for opening for RDP.

I have a program that requires a port to be open on the server. I run a
netstat -a command and find a port that is listening but is not
established.

Listening is all it is supposed to do. There is nothing else it can do until
something actually connects to the application using that port #.

I then input this port number in the program. What seems to be happening
is
that the program starts but then shuts down as if windows won't allow the
prgram to be active on that port.

The port isn't going to be blocked,...there is nothing in Windows to block
it. But if another Application is already using the port, then this app
isn't going to be allowed to.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.

 

[Richard G. Harper]

You can't manually open a port in Windows 2000 - there are no blocked ports
in Windows 2000. Only a firewall can block ports. If you can't access the
port there's nothing to change in Windows 2000 but you may need to configure
any hardware or software firewalls within your environment.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Phillip Windell]

You can not open something that is "imagninary" anyway.
Ports are just Layer4 Addresses in the same way that IP#s are Layer3
addresses.
When an Application starts up is notifies the OS's Networking subsystem that
any packet containing a particular Layer4 Address should be passed up the
"food chain" to that Application. That is all it is,...that is what
"Listening" means. The whole idea of some kind of entity called a "port" is
just imaginary.

Anyway, it takes a Firewall Application to restrict particular Layer4
Addresses (ports). if no such Firewall Application exists, then nothing is
restricted (closed, blocked, whatever).

The Windows OS,... by itself,...on its own,...by default,...allows all
Layer4 addresses.

So if it isn't working,...some other Application on the machine is already
using that port,...or the current Application you are fighting with is just
simply screwed up.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
-----------------------------------------------------

Any advice on how can I manually open a port for this app? I have only
found MS technet advice for opening for RDP.

I have a program that requires a port to be open on the server. I run
a
netstat -a command and find a port that is listening but is not
established.

Listening is all it is supposed to do. There is nothing else it can do until
something actually connects to the application using that port #.

I then input this port number in the program. What seems to be happening
is
that the program starts but then shuts down as if windows won't allow the
prgram to be active on that port.

The port isn't going to be blocked,...there is nothing in Windows to
block
it. But if another Application is already using the port, then this app
isn't going to be allowed to.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those
of
my employer or anyone else associated with me.