Closed Port at Firewll

Hi,
I have started configuring my EPORTAL system and in the process of connection Testing to my ECC Development server I get the below error in the ITS Connection Test Details.
An HTTP/S connection to http://sapeccdev.zentagroup.com:8000/sap/bc/gui/sap/its/webgui?sap-client=100 was not obtained successfully; this might be due to a closed port on the Firewall.
When I login at OS level in the EPORTAL SYSTEM and directly put the URL of ECC Development system it works fine in the WEB GUI. Also the web GUI works from any other PC in our organization by direct use of URL.
I would like to know when I test this from EPORTAL is this due to some closed port as this working by direct use of URL and what might be the possible cause of error.

Hi,
are you using a URL iview on your portal to connect to your system?
You said that you can connect to the destination application without problems when you are on the machine where your portal is installed.
This means that your portal should be able to connect as well (It cannot be any Firewall issue unless you have more than one network interface and the connection (TCP) maybe is using different interface and thus different Source IP or you normally use a Proxy to connect to your destination application and the portal is currently not)
You say you connect through Web GUI. Is there a proxy involved??
Try the following:
Login to your machine where the portal resised and on OS level issue the following command:
telnet sapeccdev.zentagroup.com 8000
Do you get a connection here?
Do you have more then one network interface on your machine??
Cheers

Similar Messages

Closed port for torrent with no iptables.rules

I have a home system with internet connection over a router. Firewall in the router seems to be disabled. I had installed guarddog and selected all the protocols that I need. There is no iptables in deamons line of rc.conf nor there is any iptables.rules files. There are 2 files in /etc/iptables, empty.rules and simple_firewall.rules. So, I wonder if any firewall is working at all in my system since guarddog is a frontend to iptables (i guess) and also is there any need for firewall since almost all the ports are closed.
Secondly, the main issue. I was using ktorrent and it was working fine until a few days ago. Now, bittorrent is not working. its not connecting at all. I tried deluge from community repo and tested the ports with http://www.deluge-torrent.org/test-port.php?port=6881 and it gave me this result:
TCP port 6881 closed on 121.247.200.189
UDP port 6881 open on 121.247.200.189
121.247.200.189 seems to be the ip of my isp as I got a dynamic one.
I am able to reach surf net but not able to download using bitorrent, however, both is possible in windows.
Taking clue from forum, i did nmap.
nmap on my router
[shantanu@bluehead ~]$ nmap 192.168.1.1
Starting Nmap 4.20 ( http://insecure.org ) at 2007-06-25 20:49 IST
Interesting ports on 192.168.1.1:
Not shown: 1679 filtered ports
PORT STATE SERVICE
21/tcp open ftp
23/tcp open telnet
53/tcp closed domain
80/tcp open http
443/tcp closed https
554/tcp closed rtsp
1755/tcp closed wms
2401/tcp closed cvspserver
5000/tcp closed UPnP
5001/tcp closed commplex-link
5050/tcp closed mmcc
6881/tcp closed bittorent-tracker
6969/tcp closed acmsoda
7070/tcp closed realserver
8000/tcp closed http-alt
8080/tcp closed http-proxy
8888/tcp closed sun-answerbook
11371/tcp closed pksd
Nmap finished: 1 IP address (1 host up) scanned in 27.653 seconds
nmap on my ip
[shantanu@bluehead ~]$ nmap 192.168.1.5
Starting Nmap 4.20 ( http://insecure.org ) at 2007-06-25 20:48 IST
Interesting ports on 192.168.1.5:
Not shown: 1696 closed ports
PORT STATE SERVICE
6000/tcp open X11
Nmap finished: 1 IP address (1 host up) scanned in 0.519 seconds
nmap on isp's ip displayed above.
[shantanu@bluehead ~]$ nmap 121.247.200.189
Starting Nmap 4.20 ( http://insecure.org ) at 2007-06-25 20:50 IST
Interesting ports on 121.247.200.189.bang-dynamic-bb.vsnl.net.in (121.247.200.189):
Not shown: 1679 filtered ports
PORT STATE SERVICE
21/tcp open ftp
23/tcp open telnet
53/tcp closed domain
80/tcp open http
443/tcp closed https
554/tcp closed rtsp
1755/tcp closed wms
2401/tcp closed cvspserver
5000/tcp closed UPnP
5001/tcp closed commplex-link
5050/tcp closed mmcc
6881/tcp closed bittorent-tracker
6969/tcp closed acmsoda
7070/tcp closed realserver
8000/tcp closed http-alt
8080/tcp closed http-proxy
8888/tcp closed sun-answerbook
11371/tcp closed pksd
Nmap finished: 1 IP address (1 host up) scanned in 30.573 seconds
Everywhere the bittorrent port seems to be closed. [b]How do I open this port?.[b/]
Last edited by ravisghosh (2007-06-25 21:09:55)

@madeye, first of all I used utorrent in Then I tried as you [shantanu@bluehead Chain INPUT (policy DROP)
target prot opt source ACCEPT 0 -- anywhere ACCEPT udp -- anywhere ACCEPT 0 -- 192.168.1.5 logaborted tcp -- anywhere ACCEPT 0 -- anywhere ACCEPT icmp -- anywhere ACCEPT icmp -- anywhere ACCEPT icmp -- anywhere nicfilt 0 -- anywhere srcfilt 0 -- anywhere Chain FORWARD (policy DROP)
target prot opt source ACCEPT 0 -- anywhere ACCEPT icmp -- anywhere ACCEPT icmp -- anywhere ACCEPT icmp -- anywhere srcfilt 0 -- anywhere Chain OUTPUT (policy DROP)
target prot opt source ACCEPT 0 -- anywhere ACCEPT udp -- anywhere ACCEPT 0 -- anywhere ACCEPT icmp -- anywhere ACCEPT icmp -- anywhere ACCEPT icmp -- anywhere s1 0 -- anywhere Chain f0to1 (3 references)
target prot opt source ACCEPT udp -- anywhere ACCEPT icmp -- anywhere ACCEPT tcp -- anywhere logdrop 0 -- anywhere Chain f1to0 (1 references)
target prot opt source ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT udp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT udp -- anywhere ACCEPT tcp -- anywhere ACCEPT udp -- anywhere ACCEPT icmp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere ACCEPT tcp -- anywhere logdrop 0 -- anywhere Chain logaborted (1 references)
target prot opt source logaborted2 0 -- anywhere LOG 0 -- anywhere Chain logaborted2 (1 references)
target prot opt source LOG 0 -- anywhere ACCEPT 0 -- anywhere Chain logdrop (4 references)
target prot opt source logdrop2 0 -- anywhere LOG 0 -- anywhere DROP 0 -- anywhere Chain logdrop2 (1 references)
target prot opt source LOG 0 -- anywhere DROP 0 -- anywhere Chain logreject (0 references)
target prot opt source logreject2 0 -- anywhere LOG 0 -- anywhere REJECT tcp -- anywhere REJECT udp -- anywhere DROP 0 -- anywhere Chain logreject2 (1 references)
target prot opt source LOG 0 -- anywhere REJECT tcp -- anywhere REJECT udp -- anywhere DROP 0 -- anywhere Chain nicfilt (1 references)
target prot opt source RETURN 0 -- anywhere RETURN 0 -- anywhere RETURN 0 -- anywhere logdrop 0 -- anywhere Chain s0 (1 references)
target prot opt source f0to1 0 -- anywhere f0to1 0 -- anywhere f0to1 0 -- anywhere logdrop 0 -- anywhere Chain s1 (1 references)
target prot opt source f1to0 0 -- anywhere Chain srcfilt (2 references)
target prot opt source s0 0 -- anywhere That means iptables I removed guarding Removed iptables and Last edited by thanks a lot for such elaborate help.
windows and u r very much right that it uses UPnP. In deluge (bt client on arch), UPnP was there but disabled (shaded). Hence, I tried running utorrent using wine and it gave a error message "Unable to map UPnP port' and is not able to connect. So, UPnP is not working in my box.
suggested "iptables -L" and it gave me the following results.
~]$ sudo iptables -L
destination
anywhere
anywhere udp spt:bootps dpt:bootpc
192.168.1.255
anywhere state RELATED,ESTABLISHED tcp flags:RST/RST
anywhere state RELATED,ESTABLISHED
anywhere icmp destination-unreachable
anywhere icmp time-exceeded
anywhere icmp parameter-problem
anywhere
anywhere
destination
anywhere state RELATED,ESTABLISHED
anywhere icmp destination-unreachable
anywhere icmp time-exceeded
anywhere icmp parameter-problem
anywhere
destination
anywhere
anywhere udp spt:bootpc dpt:bootps
anywhere state RELATED,ESTABLISHED
anywhere icmp destination-unreachable
anywhere icmp time-exceeded
anywhere icmp parameter-problem
anywhere
destination
anywhere udp dpts:6970:7170
anywhere icmp echo-reply
anywhere tcp spts:1024:65535 dpts:6881:6889 state NEW
anywhere
destination
anywhere tcp spts:1024:5999 dpt:6969 state NEW
anywhere tcp spts:1024:5999 dpt:http state NEW
anywhere tcp spts:1024:5999 dpt:http-alt state NEW
anywhere tcp spts:1024:5999 dpt:8008 state NEW
anywhere tcp spts:1024:5999 dpt:8000 state NEW
anywhere tcp spts:1024:5999 dpt:8888 state NEW
anywhere tcp spts:1024:5999 dpt:ftp state NEW
anywhere tcp spts:1024:5999 dpt:https state NEW
anywhere tcp dpt:rtsp state NEW
anywhere tcp dpt:7070 state NEW
anywhere tcp spts:1024:5999 dpt:cvspserver state NEW
anywhere tcp dpt:1755 state NEW
anywhere udp dpt:1755
anywhere tcp spts:1024:5999 dpt:11371 state NEW
anywhere tcp spts:1024:5999 dpt:5050 state NEW
anywhere tcp spts:1024:5999 dpt:telnet state NEW
anywhere tcp spts:1024:5999 dpts:5000:5001 state NEW
anywhere udp spts:1024:5999 dpt:5000
anywhere tcp dpt:domain state NEW
anywhere udp dpt:domain
anywhere icmp echo-request
anywhere tcp spts:1024:5999 dpt:5222 state NEW
anywhere tcp spts:1024:5999 dpt:5223 state NEW
anywhere tcp spts:1024:5999 dpts:6881:6889 state NEW
anywhere
destination
anywhere limit: avg 1/sec burst 10
anywhere limit: avg 2/min burst 1 LOG level warning prefix `LIMITED '
destination
anywhere LOG level warning tcp-sequence tcp-options ip-options prefix `ABORTED '
anywhere state RELATED,ESTABLISHED
destination
anywhere limit: avg 1/sec burst 10
anywhere limit: avg 2/min burst 1 LOG level warning prefix `LIMITED '
anywhere
destination
anywhere LOG level warning tcp-sequence tcp-options ip-options prefix `DROPPED '
anywhere
destination
anywhere limit: avg 1/sec burst 10
anywhere limit: avg 2/min burst 1 LOG level warning prefix `LIMITED '
anywhere reject-with tcp-reset
anywhere reject-with icmp-port-unreachable
anywhere
destination
anywhere LOG level warning tcp-sequence tcp-options ip-options prefix `REJECTED '
anywhere reject-with tcp-reset
anywhere reject-with icmp-port-unreachable
anywhere
destination
anywhere
anywhere
anywhere
anywhere
destination
192.168.1.5
192.168.1.255
bluehead.localdomain
anywhere
destination
anywhere
destination
anywhere
is not disabled and that firewall rules are setup by guarddog.
using "pacman -Rns guarddog" and rebooted. Still get the same results with utorrent and "iptables -L" and also the port test shows tcp 6881 is still closed.
now bt clients seems to be able to connect and it works; however, port test still shows tcp 6881 closed.
ravisghosh (2007-06-27 16:51:12)

"Limiting closed port RST response" what is this?

I'm getting this message continuously in the system log:
Limiting closed port RST response from 251 to 250
I'm running server 10.4.8 on an xserve G5, 2 GB RAM. I don't have firewall enabled. My firewall is a Sonicwall 2040 pro and I know there are no port scans being let through. Any one have any idea what's causing this?

Here is a sample from the system.log, it just goes on and on like this:
Feb 8 05:32:17 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:20 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:23 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:26 humanla kernel[0]: Limiting closed port RST response from 253 to 250 packets per second
Feb 8 05:32:27 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:32 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:35 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:38 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:41 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:44 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:47 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:50 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:53 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:56 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:32:59 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:02 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:05 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:08 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:11 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:14 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:17 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:20 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:23 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:26 humanla kernel[0]: Limiting closed port RST response from 252 to 250 packets per second
Feb 8 05:33:29 humanla kernel[0]: Limiting closed port RST response from 252 to 250 packets per second
Feb 8 05:33:32 humanla kernel[0]: Limiting closed port RST response from 252 to 250 packets per second
Feb 8 05:33:35 humanla kernel[0]: Limiting closed port RST response from 253 to 250 packets per second
Feb 8 05:33:38 humanla kernel[0]: Limiting closed port RST response from 252 to 250 packets per second
Feb 8 05:33:41 humanla kernel[0]: Limiting closed port RST response from 252 to 250 packets per second
Feb 8 05:33:44 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second
Feb 8 05:33:47 humanla kernel[0]: Limiting closed port RST response from 252 to 250 packets per second
Feb 8 05:33:50 humanla kernel[0]: Limiting closed port RST response from 251 to 250 packets per second

Closed ports on an open firewall w/ port forwarding enabled.

I'm running a closed network for my game development club and I need to be able to have each computer be able to communicate with each other for when the group tests out their new multiplayer games.
I decided to set up Arch as the operating system since they use Lenovo Thinkcentre M92p's right now. I also set up a seperate network server with Arch to take care of networking issues between the computers and because we aren't allowed to use the campus bandwidth.
The server has its own dhcp server running (dhcpd) and iptables set up to allow any and all connections. The computers have exactly the same iptables setup as well.
I've done basic scans of the computers using nmap and it always comes back with
Nmap scan report for localhost.localdomain (127.0.0.1)
Host is up (0.00033s latency).
All 1000 scanned ports on localhost.localdomain (127.0.0.1) are closed
If I try to scan the other computers, the report is no different. I've set iptables to accept incoming connections, wouldn't nmap say all ports are open?
Last edited by Jakkin (2014-11-04 03:09:56)

I know dhcp servers don't open ports, mainly they just provide IP addresses to computers on the network.
I have ssh installed on all the computers (including the server), but the only computer that shows up on nmap is the server itself.
Its kinda embarrassing, but how I found out about the port problem was from testing the network using TF2. When I used my Netgear router as the dhcp server, TF2 worked perfectly. Since I've migrated to the new server and disabled dhcp on my router, TF2 hasn't worked. The computers can see each other, but, other then sshing into the server, they can't seem to connect to each other.
Last edited by Jakkin (2014-11-04 05:15:00)

Need quick help closing port

I have created a server.java and client.java
The programs are not that good.
However I have a problem
I have ran my server a few times and each time need to use a diff port as the previous ones are being listnened to. Obviously from the last servers I ran.
I have switched my comp off and on many times and these ports are still in use.
Please help as I have no idea what is wrong.

I don't have a copy of XP at hand, so I can only give you some generalities.
Somewhere in the Control Panel, I think in the Administrative Tools folder, there should be a "Services" program that displays to some extent what programs you have running. Every program that's listening on a port should be listed in there.
It sounds like XP thinks you've only temporarily suspended your server program. I won't guarantee that's the case, but that's what sounds reasonable, and as a result, it is saving those "open" port numbers just in case you decide to resume the program.
If you have copies of server.java on that list (or rather, copies of the JVM), I would suggest closing all of your Java programs first, your web browsers to be on the safe side, and then "stop" and "remove" any remaining JVMs especially those that are tied to the ports you want to close.
(And yes, you are discovering the hard way why it's crucial that you remember to close your ports. The simplest way to do so is to write a method that closes all ports, and include it inside each and every try...catch block, as well as your exit routine.)

Wap2000 closing ports after 10 mins of uptime

We have two WAP2000's in our offices which we roam between depending on which office we are in. Lets call them Access point A and Access point B.
Both are firmware 2.0.4.0 and have seperate IP addresses. Both are set up with two SSID's and VLAN tagging. Both handle connections just fine and can route traffic. Both are PoE and the catalyst switch reports PoE util at 25% over all of its ports.
After 10 minutes of uptime, Access point B will close all of its TCP ports - SNMP, Web admin etc but does still handle wireless connections and traffic correctly. Access point A does not close any ports.
I have confirmed that when the problem happens, Access point B still handles traffic just fine by checking the MAC address the clients is associated with, as well as powering down Access point A and confirming traffic is flowing. Access point B will also respond to ICMP ping after it has closed all of its management ports. I have confirmed there is no other device on the network attempting to use the same IP address as Access point B.
I have also confirmed that I am attempting to access the management ports from the management Vlan (1) - else I would not be able to reach Access Point A's management ports either. I have turned wireless management access on for Access point B and the ports close after 10 minutes of uptime from the wireless side too, so highly unlikely this is a vlan issue.
I have confirmed all of the settings (bar the IP address config) exactly match on both Access point A and Access point B. The firmware revisions are the same.
Not sure what would cause this behavior to happen? Any ideas? Its rather frustrating.

Mr. Newton, Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center. Thank you so much for participating in the Community Forums. I found your issue rather strange having never seen that behaviour out of any of our Access Points before. But more importantly Thank You for posting the way that your issue was resolved. That small piece is so often left out when the customer finds a resolution with out one of the Cisco Techs getting involved.
That example, shows how the forums are supposed to work for you the customer. Now if someone has a similar issue and searches the forum they will be presented with a possible solution to try.
Thanks again
Eric Moyers
Cisco Network Support Engineer
1-866-606-1866

Opening and closing ports?

I used to be able to specify certain TCP ports to be open or closed, but I can't find how to do this in Snow Leopard. Can anyone point me in the right direction, please? Thanks!

Hi Sandra,
The Firewall in Leopard and Snow Leopard works differently to the Tiger and Earlier versions.
It has also moved from System Preferences > Sharing to System Preferences > Security.
Apps are now "Certificated" to be allowed in Leopard and Snow Leopard.
The layout between the two also has some changes.
Snow Leopard needs the Firewall On and then the Advanced Button to accessed "Allowed Signed Apps" and the App needs adding to the list.
Leopard has a Allow All (Off setting, Allow Specific Apps requiring apps to be added to the list and a middle Allow Essentials (iChat is not an Essential) option.
Airport Utility > Modify Button > Internet Pane > NAT tab Port Mapping Protocol is the setting that work like UPnP in other routers. (Which I think you have discovered.)
9:49 PM Monday; March 22, 2010

"Closed" port allowing connections

I installed Transmission to get distro .iso's even though I'm typically wary of P2P programs. One reason is the interesting behavior that I'm seeing when Transmission is open. I'm using the iptables.basic rules that come with the package. An nmap scan from another computer in my wireless network shows that the connection port is closed but when I scan my IP address (not localhost) from my computer, it says that the torrent client port is the only one that is open which is consistent with the fact that it is also accepting connections (even without any port forwarding enabled on the router or my machine). I would like to at least have a choice whether or not I allow connections to my machine but the only option seems to be not using Transmission at all. Is this the case? If not, why is the port closed according to external tests yet it is accepting connections?

upnp is the only thing I can come up with.

Closed ports

I am trying to use ARD with an Airport Extreme and I've set up the base station to open the ports for ARD, but I still cannot make a remote connection with another computer over the Internet. I've also done some port scans which say the ports are closed. I don't know what else to do to get the ports open. Is there something I should do besides port mapping?
Thanks for your help.

Note that you need to be opening and forwarding the ports in the router on the client's end of the Internet connection as well as on your end (on your end, the ports would be open and forwarded to your administration system's IP address). It's not clear when you refer to the Airport Extreme whether that's on your end or the client system's end.

Closed ports with WRT160NL

Hello,
Im trying to open some ports in WRT160NL router (firmware: 1.0.02 ), i set them i save the configuration but when i check it from outside http://www.yougetsignal.com/tools/open-ports/ it said the ports are closed. This is my configuration
out port= 22000
in port= 21000
protocol= udp/tcp (both)
ip addres= 192.168.1.135
active= true
thanks in advance for your help.

Thanks, i found out my mistake...
step 2:Verify the server uses those ports..
best regards!

Help! 5 closed ports while the rest are stealthed.

My ISP recently blocked access to specific torrent sites on foot of a court ruling that it must do so.
Up until they did this, ALL of my ports were "stealthed" by my NAT (hardware) firewall (in my ISP's router).
Now, 5 of my ports report as "closed" instead of "stealthed". I would like to have them report as "stealthed" again.
I have no idea how to do this, so would appreciate advice on the issue.
My router/firewall are made by Netgear for my ISP.
Additionally, when I regularly check the security status of my network on the excellent "Shields Up!", I sometimes find that port 443 (HTTPS) is showing as "open" when I check it. This can be resolved by resetting my Windows Firewall
to its default settings, which returns it to stealth mode.
I have no idea why port 443 is opening or which program may be opening it. Obviously, I am concerned about this.
I hope someone can help!

You would create several pseudo classes on your footer links. First, make sure your footer has an id (or is the actual footer html5 element)...
<div id="footer">your links</div>
or
<footer>your links</footer>
Then in your css, specify that element's link pseudo classes in this order...
#footer a:link {color:white;}
#footer a:visited {color:white;} /*this needs to be set to avoid the default purple on visited links*/
#footer a:hover {color:orange;}
#footer a:active {color:green;} /*this is the color it changes to while clicking*/
or
footer a:link {color:white;}
footer a:visited {color:white;}
footer a:hover {color:orange;}
footer a:active {color:green;}

Plex Media Server Access Via Closed Port

Hey All,
I'm running Plex Media Server on my home server (running Arch of course) and am curious how it is able to run and be accessed on port 25244 when both my router and iptables config do not have this port opened? I can access the server via port 32400, but if I go into the app settings and connect it to a myPlex account, it allows the server to be mapped to 25244.
Thanks in advance!
- James

Hi dlw,
Thanks for the reply. I have installed plex server on my home PC (which I was going to use as the server pc - a windowns 7 - 64bit) and then install plex on my ipad so that I can watch films and listen to music held on my PC.
I've installed the lastest versions of silverlight and flash and also installed the plex server software. However, when I right click on the tray icom and select media manager it tries to open http://www.localhost.com:32400/manage/ in firefox but keeps getting timed out.
Haven't got a clue why or how to resolve it, but slowly trying me insane.

Kernel:limiting closed ports rst response

this report began to occur in log. How do I find what is it?

These commands:
sudo sysctl -w net.inet.udp.log_in_vain=1
sudo sysctl -w net.inet.tcp.log_in_vain=1
will give you output like the following in the console log:
01-10-12 20:20:45,000 kernel: Connection attempt to TCP 192.168.1.17:554 from 192.168.1.15:37481
In my case it was Synology Surveillance station trying to connect to port 554 on my laptop...
Don't forget to set the variable back to 0 after you found the problem!
Patrick

In CVI !!!! How to dynamic change BaudRate of RS232 Serial COM Without closing the Port !!!

Dear all:
I want to change the buadrate of serial com without closing the serial com, but it failed when I use the function "SetCommConfig(m_hCom, &Com_cfg, Com_cfg_S) " to reset the buadrate ,baudrate is no change when use GetCommConfig to read back the value.
Appreciated all of your advice . TKS!
Code with WINAPI as beloow:
CreateFile(..) ;
GetCommState(..);
dcb.BaudRate= 1000000 ;
SetCommState(..);
//......do other things
//change baudrate to normal without closing port .
GetCommConfig(m_hCom, &Com_cfg, &Com_cfg_S);
Com_cfg.wVersion = 0X100;
Com_cfg.dwProviderSubType = 1;
Com_cfg.dcb.BaudRate =9600 ;
Com_cfg.dcb.StopBits =1 ;
SetCommConfig(m_hCom, &Com_cfg, Com_cfg_S);
GetCommConfig(m_hCom, &Com_cfg, &Com_cfg_S);
Solved!
Go to Solution.

This topic has been discussed some years ago: see here. Please note that even if I made that sample program which changes the baud rate without closing the port, I never used it in a real situation: you'll need to made your tests and check if this solution can satisfy your needs in the short and long term.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Closing open ports

Hi,
$ uname -a
SunOS kite 5.10 s10_72 i86pc i386 i86pc
I installed Solaris 10 on an spare Dell box recently. I'm not well versed in Solaris and I wanted a little more exposure to it. Over the past couple of days I've managed to shut down just about every service I don't use/need, but I'm left with a few nagging open ports that I can't seem to close. The only port I want to have open is 22 for ssh.
Here's a list of currently open ports (as reported by nmap):
PORT STATE SERVICE VERSION
22/tcp open ssh SunSSH 1.1 (protocol 2.0)
111/tcp open rpcbind 2-4 (rpc #100000)
898/tcp open http Solaris management console server (SunOS 5.10 x86; Java 1.4.2_06; Tomcat 2.1)
6000/tcp open X11 (access denied)
Port 111: Stopping bind (hence closing port 111) prevents X from starting upon reboot. The boot process won't start the dtlogin screen, and I end up having to use console mode. Is there a way around this?
Port 898: This port is opened by the wbem service. If I disable wbem, the Solaris Managment Console won't work anymore. Is there a configuration option for the SMC that allows me to shutdown the listening port but still allows me to use the SMC from the localhost?
Port 6000: I have no idea how to close this port. I did manage to close port 177 (XDMCP) from the Xconfig file, but I don't know how to close 6000. I don't need any remote X connectivity at all. Any ideas?
Thanks.

Thanks for the reply, Bob.
But you can control wbem (port 898) by changing the
file /etc/rc2.d/S90wbem to /etc/rc2.d/s90wbem. So on
reboot it won't start. To turn it off now just enter
from the root prompt "/etc/rc2.d/S90wbem stop" (w/o
o the quotes). I'm not sure about rpcbind.Yeah, I was able to stop the wbem service permanently by toying inside rc2.d, but without wbem, the Solaris Mgt Console doesn't work anymore. I kinda like the Console, but in my opinion it shouldn't be listening for remote connections; there should be an option to allow its use only on the localhost.
>
I am looking around at how Solaris 10 handles these
services. If you enter the command "svccfg" you'll
be dropped a "svc:>" prompt. From here you can enter
"list" to get a listing of the servcies you can
manage through this tool. Of course you will want to
look at the man pages, svccfg(1M). Two other tools
to look at are svcadm(1M) and smf(5).Let me know if you figure out how to use the svc tools to point to a new daemon. For example, I installed OpenSSH 3.9.p1 at /usr/local/sbin/sshd but couldn't find a way to coax svcadm into starting the new daemon instead of the Sun SSH daemon. I ended up adding an rc2.d script to start OpenSSH, and executing svcadm disable ssh to permanently stop the Sun version. There's gotta be another way...

Closed Port at Firewll

Similar Messages

Maybe you are looking for