Port is not listening

10.6.8 X-serve.  I have an app that requires ports 9100 and 9200 to be open.  I have added these ports to the server firewall to enable.  Started and stopped the sever firewall.  My app is unable to connect via these two ports.  Through terminal netstat -an | grep LISTEN does not show my server listening on ports 9100 or 9200.  How can I persuade these ports into listening?

Problem solved, Reinstalled app, now ports are listening

Similar Messages

  • Port 3389 not listening

    Windows Server 2003R2. Terminal Services is installed and started. Remote Desktop is Enabled. In the Terminal Services Manager session window, RDP-TCP is shown as being in a listening state. But when I run netstat -a, port 3389 does not show up. RD client
    cannot connect. Telnet or ssh to that port does not connect.
    TCP is working fine: I can use logmein to view the server; I can VPN to the server, I can look at SMB shares once the VPN is up. No TCP filtering is active. The Windows Firewall is not active.
    How can I get port 3389 going and be able to RDP in?
    The registry is still showing port 3389 as the listening port.
    I have removed and re-created the RDP-tcp port without any trouble and without success. The properties are set on defaults.
    Remote Desktop devices in the device manager show as operating fine.
    It used to work fine and just recently (sometime in January) it stopped working. As far as I know, no new software was installed at that time.
    I have reviewed a bunch of stuff found in Google but none of it seems to help, so far.

    We opened a case with Microsoft on this issue and we determined that it was related to the following driver being disabled:
    remote desktop services security filter driver
    To check whether this enabled or disabled, open device manager and show hidden devices. We were not able to enable it, so we uninstalled it and rebooted. After rebooting we were able to telnet to the server on port 3389, but we were still not able to connect
    with remote desktop.
    As a last step, we set remote desktop security layer to “negotiate”. To do this, open the "remote desktop session host configuration" application in administrative tools and edit the properties of “rdp-tcp”. The setting can be found on the general tab.
    Hope this helps someone!

  • LDAP Ports 389 and 636 not listening

    after the BM3.9 upgrade, i realized, that my LDAP server is not working.
    i can load the nladp without any message but when i look in the tcpcon, the
    ports are not listen.
    i tried recreate the LDAP Server and group in the E-dir, i tried recreate
    the CertificateSSL. on all other servers it is running without problems.
    Server is 6.5 SP6 with BM 3.9, Edir 8.7.3.9
    it has two NICS, one private and a public.
    NLDAP NLM version 10555.40
    any suggestions
    Thanks
    Sascha

    high anders
    thanks for the answer.
    it says three times:
    LDAP Server config version 8 does not match executable config version 8
    Starting dynamic upgrade
    Dynamically upgrading LDAP Server object...
    Failed to set value '8.7.3.9' in attribute 'Version' on LDAP Server object
    'CN=LDAP Server - JLE3\OU=Resourcen\O=JLE' in UpgradeLDAPServerObject, err =
    no access (-672)
    Could not complete dynamic upgrade, err = no access (-672)
    Could not validate Group in ReadConfigFromDS, err = no access (-672)
    Could not update server configuration, err = no access (-672)
    did i mentioned, that i already new created the e-dir objects with C1. with
    imananger, i cant see the snapins for LDAP, because there i have the RBS
    somehow configured and i actually even not know, how to disable this.
    Sascha

  • GWIA not listening on HTTP port

    I recently upgraded our GW8 to new hardware and eventually to 2012 sp1, now I'm seeing the following error in the GWIA log and the GWIA is not listening on its http port.
    There is nothing listening on 9850 (default http port for gwia).
    ****** 04-10-13 10:03:39 ******
    10:03:39 F476 ****************** Agent Restarted ******************
    10:03:39 F476 MTP: Message Transfer Protocol initialization...
    10:03:39 F476 MTP: Queue initialization...
    10:03:39 F476 MTP: Queue initialization...
    10:03:39 F476 Startup: No frgnames.cfg file found.
    10:03:39 F3C7 Starting GWHTTP-Listener
    10:03:39 F476 HTTP server running
    10:03:40 F476 Error Listen Port is already in use. [856A]
    10:03:41 F476 Shutdown of Threads
    10:03:42 F476 Shutdown of Threads
    After disabling GWIA POP / IMAP / LDAP (setting them to port 0) I'm getting the following(and still no http):
    10:08:12 F476 ****************** Agent Restarted ******************
    10:08:12 F476 MTP: Message Transfer Protocol initialization...
    10:08:12 F476 MTP: Queue initialization...
    10:08:12 F476 MTP: Queue initialization...
    10:08:12 F476 Startup: No frgnames.cfg file found.
    10:08:12 F3E7 Starting GWHTTP-Listener
    10:08:12 F476 HTTP server running
    10:08:13 F476 Error, Internal Udp Port is unusable. [8911]
    10:08:14 F476 Shutdown of Threads
    10:08:15 F476 Shutdown of Threads
    GWIA is listening on the following ports, 1.2.3.4 being the server ip and I removed the POA connections.
    # netstat -pan | grep -i gwia
    tcp 0 0 1.2.3.4:7060 0.0.0.0:* LISTEN 12253/gwia
    tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 12253/gwia
    udp 0 0 0.0.0.0:41547 0.0.0.0:* 12253/gwia
    Any ideas ?
    Besides this GW is running just fine.

    Originally Posted by laurabuckley
    Oh ok.
    Check to see if the firewall is disabled on the server.
    Also, set an HTTP username and password in ConsoleOne then do a full stop and start of GWIA.
    Please post back your results.
    Cheers,
    Hi Laura,
    The firewall is disabled (double checked), there is a http username and password (re-set it) set in C1, a full stop and start did not make a difference.
    Originally Posted by laurabuckley
    One more thing.... if your POA is running on the same box try disabling POP and IMAP on the POA - restart the POA and GWIA.
    Cheers,
    We're actively using the POA IMAP so that's not something I can disable.
    Thanks,
    Arjan

  • Child DC cannot Replicate to Parent DC, because of connection errors. MS PortQryUI shows that ports 3268 and 3269 are not listening,

    I started a support case with Microsoft to help me with raising the our domain Forest level because i received a message stating that there were Windows 2000 PDC still listed in the database. These PDCs were removed years ago. The tech saw all of the problems
    i was having with domain replication so that is where he started. running the MS PortQryUI shows that ports 3268 and 3269 are not listening, (TCP port 3268 (unknown service): NOT LISTENING) when run FROM a Child domain controller against the Parent
    Domain controller. Between the 2 Child domain controllers these ports are listening.
    The Windows firewall is not running on any of the controllers, i removed a virus protect client from all of the servers, although i didn't enable the firewall there either, but these ports are still not listening on the Parent DC.
    I need help debugging this. I am not very familiar with network sniffers so if i need to run one i'll need some guidance. This DC only has one NIC, all IP addresses are static, all servers are setup like this. All servers are in the same subnet, on the same
    lan, on the same cisco switch, there shouldn't be anything blocking this port from starting.
    I looked over other post that show this same problem, but they don't give a solution. If i am not using the Windows firewall why wouldn't these ports be open?
    Any ideas? web searches are all over the map on trying to find the reason for this.
    Bobby

    Try running the below command on the DCs that you think have the ports blocked or all the DCs.
    netdiag /test:ipsec /debug > c:\dcname-ipseclog.log
    Open that from the C drive and see if there is anything saying block or filters. 
    Also, just for kicks have you disabled the firewall service on the DCs? 
    And just for kicks have you tried enabling firewalls ports on all the DCs?  The KB is below
    http://support.microsoft.com/kb/555381/en-us
    Step 1 - netdiag results
    Step 2 - disable the firewall service on all DCs if step 1 was negative
    Step 3 - enable the firewalls on all DCs per KB 555381 if step 2 doesn't work
    Let us know how it goes!
    If it answered your question, remember to “Mark as Answer”.
    If you found this post helpful, please “Vote as Helpful”.
    Postings are provided “AS IS” with no warranties, and confers no rights.
    Active Directory: Ultimate Reading Collection

  • Port 88 is not listening

    I have seen in few servers and client machines , they are not listening on port 88.But I am able to login in that machine using my domain credential.
    If it is not listening then how authentication will work?
    Thanks 
    Ragavan

    I have seen in few servers and client machines , they are not listening on port 88.But I am able to login in that machine using my domain credential.
    If it is not listening then how authentication will work?
    Thanks 
    Ragavan
    I presume below two links will be helpful for you.
    http://technet.microsoft.com/en-us/video/kerberos-authentication-how-it-works.aspx
    http://technet.microsoft.com/en-us/library/cc772815%28v=ws.10%29.aspx
    Awinish Vishwakarma - MVP
    My Blog: awinish.wordpress.com
    Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.

  • Sles poa not listening on default ports

    we dbcopied the domain and post office from netware 6.5.8 to sles 10 spk2, gw7.0.3.
    installed mta, poa and gwia... the poa starts but is not listening on ports 1677, 7181 or 7101 all default ports.
    all 3 agents are running on the host... these ports are not being used by any other service....
    any ideas... or has any seen this....

    * waketech,
    firewall is down?
    Uwe
    Novell Knowledge Partner (NKP)
    Please don't send me support related e-mail unless I ask you to do so.

  • Sql 2008 express not listening on port 1433

    I installed sql 2008 express on 2008R2 but it is not listening on port 1433.
    I check configuration for tcp and enabled that already. also started sql browser service.
    any idea?

    I installed sql 2008 express on 2008R2 but it is not listening on port 1433.
    I check configuration for tcp and enabled that already. also started sql browser service.
    any idea?
    by default SQL Server Express does not enable Remote Connections.
    Could you check the following:
    1) check that the SQL Express is running (SQL Server Configuration Tool)
    2) log onto the box containing the SQL Server and try to connect with SSMS to the SQL Express instance. Try tcp/ip and/or shared memory to connect.
       if you can successfully login check that the SQL Server does allow Remote Connections
    3) Firewall does not block incoming connections
    4) does the DNS server name resolve to the correct ip address of the SQL Server ?

  • POA ist not listening on port 7191

    Hi,
    When installing the mobility service I noticed that POA is not listening on port 7191.
    How can I start this listening ?
    Bye
    Alfons

    Originally Posted by Alfons
    Hi,
    When installing the mobility service I noticed that POA is not listening on port 7191.
    How can I start this listening ?
    Bye
    Alfons
    Take a look here: https://www.novell.com/documentation...nfig_user_soap
    Thomas

  • RDP Port not Listen in Windows Server 2008 Std With Sp2

    Hi all
    I have Windows 2008 Server Std with SP2 Domain Member Server..  From Last week On-wards , am not able to take remote desktop control .. But i can able to Ping my Server from network .. I check remote settings on that server.. It
    is enabled.. and also remote desktop service(Terminal service) was started successfully..  I checked my network firewall for port(3389) blocking.. But there is no much block in my network firewall.. i also disabled windows firewall in my server.. But
    still i couldn't able to take RDP.. I also checked my Domain GPO and Local GPO settings for RDP Block.. But there is no such settings enabled.  I did following Troubleshooting Steps, but still the problem persist
    1. Telnet serverip 3389
     Result : Could not open connection to the host, on port 3389: 
    2. netstat -n -a -o | find "3389" (i run this command in my RDP Problem server)
    Result : nothing displayed (3389 port not listed )
    3. i again & again restarted Terminal service and the server, but still problem exists
    4.i changed the RDP port no and restarted the service as well as the server , but still problem exist
    5. I checked all RDP related Registry settings , everything is perfect
    Please help me to solve this issue
    I need your valuable reply urgently
    Thanks in advance

    Hi Mohamed,
    You mention, that you the server is not listening to port 3389 when you run netstat. This is the reason why telnet and RDP connectivity fails in a first place. You also said that you changed the RDP port number. What was is before the change, and to what
    did you change it to?
    Please verify if the Terminal Service is listening to 3389 (0xd3d) with following command:
    reg query "HKLM\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v PortNumber
    Output:
    PortNumber    REG_DWORD    0xd3d
    Try to enable the Operational log for TerminalServices-RemoteConnectionManager events in Event Viewer:
    Open Event Viewer
    Navigate to Applications and Service Logs\Microsoft\Windows\TerminalServices-RemoteConnectionManager
    Select the Operational log and chose Enable Log
    from the Action or context menu
    Restart Terminal Services service
    Then consult this event log and the System and Application logs for any related errors and warning. It might be helpful to post relevant event log entries here.
    Additional information and solutions about Terminal Server Listener events and errors can be found here:
    http://technet.microsoft.com/en-us/library/cc727385(v=ws.10).aspx
    Regards,
    Johann
    // Johann

  • Mail Not Listening On Port 25

    Oh joy, another problem with the Mail System. Now mail is not listening on port 25. A port scan on the box shows ftp on port 21, ssh on 22, then jumps to http on port 80. Port 25 is not listed, although the mail server is still sending out mail that's backed up in the queue. How do I get this thing to start listening on 25 again?
    Gary

    Never mind, I found the issue. Parallels. Go figure.

  • VPN ports not listening on WRVS4400N

    Hi, 
    I have a brand new WRVS4400N running Firmware Version: V1.1.03-ETSI and I cannot seem to get the client VPN workign at all. 
    Config :
    No Static IPSec tunnels
    DOS Protection : OFF
    FireWall : OFF
    Block WAN Request: DISABLE
    Remote Mgmt : ON
    HTTPS : ON
    I have used QuickVPN  1.2.11 on both Vista and XP and still no luck. QuickVPNPlus reports "a connection with the server cannot be established" when using ports 443 OR 60443. I have even  tried this from behing many routers in case I was running into a NAT-T issue.Then I went back to basics and tried to telnet which is showing me that neitherr port 443 or 60443 are listening.!!
    Does anyone have any pointers to resolving this issue. ?
    I have spend hours on hold for support and trying to debug what I thought was a client side issue and all the time it appears as if the device is not listening.
    Any help would be greatly appreciated.
    Regards
    Peggo 

    Hi,
    Thanks for the prompt reply.
    The router has been tested with the fireall both ON and OFF.
    There are two  VPN accounts and both are marked as active. 
    The router does have a public on the WAN interface in the 194.125 range. The router is connected to a DSL ISP over PPPoE and all connections over the link are working just not 443 OR 60443 to the router IP. 
    The VPN Log (below) shows nothing of use (to me anyway) I cannot see the connections come through in the log. But I am sure remote connections are working as I'm logged into the device remotely on port 8080.
    Many Thanks 
    Peggo
    VPN_LOG>>>>>>> 
    Dec 31 16:00:59 - [VPN Log]: Starting Pluto (Openswan Version cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID OE@ECqImzhFD)
    Dec 31 16:00:59 - [VPN Log]: @(#) built on Sep 3 2007:16:44:42:
    Dec 31 16:00:59 - [VPN Log]: Setting NAT-Traversal port-4500 floating to on
    Dec 31 16:00:59 - [VPN Log]: port floating activation criteria nat_t=1/port_fload=1
    Dec 31 16:00:59 - [VPN Log]: including NAT-Traversal patch (Version 0.6c)
    Dec 31 16:00:59 - [VPN Log]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
    Dec 31 16:00:59 - [VPN Log]: starting up 1 cryptographic helpers
    Dec 31 16:00:59 - [VPN Log]: started helper pid=731 (fd:5)
    Dec 31 16:00:59 - [VPN Log]: Using KLIPS IPsec interface code on 2.4.27-star
    Dec 31 16:00:59 - [VPN Log]: Changing to directory '/etc/ipsec.d/cacerts'
    Dec 31 16:01:00 - [VPN Log]: Changing to directory '/etc/ipsec.d/aacerts'
    Dec 31 16:01:00 - [VPN Log]: Changing to directory '/etc/ipsec.d/ocspcerts'
    Dec 31 16:01:00 - [VPN Log]: Changing to directory '/etc/ipsec.d/crls'
    Dec 31 16:01:00 - [VPN Log]: Warning: empty directory
    Oct 29 15:45:39 - [VPN Log]: shutting down
    Oct 29 15:45:42 - [VPN Log]: Starting Pluto (Openswan Version cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID OE@ECqImzhFD)
    Oct 29 15:45:42 - [VPN Log]: @(#) built on Sep 3 2007:16:44:42:
    Oct 29 15:45:42 - [VPN Log]: Setting NAT-Traversal port-4500 floating to on
    Oct 29 15:45:42 - [VPN Log]: port floating activation criteria nat_t=1/port_fload=1
    Oct 29 15:45:42 - [VPN Log]: including NAT-Traversal patch (Version 0.6c)
    Oct 29 15:45:42 - [VPN Log]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
    Oct 29 15:45:42 - [VPN Log]: starting up 1 cryptographic helpers
    Oct 29 15:45:42 - [VPN Log]: started helper pid=1204 (fd:5)
    Oct 29 15:45:42 - [VPN Log]: Using KLIPS IPsec interface code on 2.4.27-star
    Oct 29 15:45:42 - [VPN Log]: Changing to directory '/etc/ipsec.d/cacerts'
    Oct 29 15:45:42 - [VPN Log]: Changing to directory '/etc/ipsec.d/aacerts'
    Oct 29 15:45:42 - [VPN Log]: Changing to directory '/etc/ipsec.d/ocspcerts'
    Oct 29 15:45:42 - [VPN Log]: Changing to directory '/etc/ipsec.d/crls'
    Oct 29 15:45:42 - [VPN Log]: Warning: empty directory
    Oct 29 16:05:49 - [VPN Log]: shutting down
    Oct 29 16:05:51 - [VPN Log]: Starting Pluto (Openswan Version cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID OE@ECqImzhFD)
    Oct 29 16:05:51 - [VPN Log]: @(#) built on Sep 3 2007:16:44:42:
    Oct 29 16:05:51 - [VPN Log]: Setting NAT-Traversal port-4500 floating to on
    Oct 29 16:05:51 - [VPN Log]: port floating activation criteria nat_t=1/port_fload=1
    Oct 29 16:05:51 - [VPN Log]: including NAT-Traversal patch (Version 0.6c)
    Oct 29 16:05:51 - [VPN Log]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
    Oct 29 16:05:51 - [VPN Log]: starting up 1 cryptographic helpers
    Oct 29 16:05:51 - [VPN Log]: started helper pid=1785 (fd:5)
    Oct 29 16:05:51 - [VPN Log]: Using KLIPS IPsec interface code on 2.4.27-star
    Oct 29 16:05:51 - [VPN Log]: Changing to directory '/etc/ipsec.d/cacerts'
    Oct 29 16:05:51 - [VPN Log]: Changing to directory '/etc/ipsec.d/aacerts'
    Oct 29 16:05:52 - [VPN Log]: Changing to directory '/etc/ipsec.d/ocspcerts'
    Oct 29 16:05:52 - [VPN Log]: Changing to directory '/etc/ipsec.d/crls'
    Oct 29 16:05:52 - [VPN Log]: Warning: empty directory
    Oct 29 16:16:52 - [VPN Log]: shutting down
    Oct 29 16:16:54 - [VPN Log]: Starting Pluto (Openswan Version cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID OE@ECqImzhFD)
    Oct 29 16:16:54 - [VPN Log]: @(#) built on Sep 3 2007:16:44:42:
    Oct 29 16:16:54 - [VPN Log]: Setting NAT-Traversal port-4500 floating to on
    Oct 29 16:16:54 - [VPN Log]: port floating activation criteria nat_t=1/port_fload=1
    Oct 29 16:16:54 - [VPN Log]: including NAT-Traversal patch (Version 0.6c)
    Oct 29 16:16:54 - [VPN Log]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
    Oct 29 16:16:54 - [VPN Log]: starting up 1 cryptographic helpers
    Oct 29 16:16:54 - [VPN Log]: started helper pid=2293 (fd:5)
    Oct 29 16:16:54 - [VPN Log]: Using KLIPS IPsec interface code on 2.4.27-star
    Oct 29 16:16:54 - [VPN Log]: Changing to directory '/etc/ipsec.d/cacerts'
    Oct 29 16:16:54 - [VPN Log]: Changing to directory '/etc/ipsec.d/aacerts'
    Oct 29 16:16:54 - [VPN Log]: Changing to directory '/etc/ipsec.d/ocspcerts'
    Oct 29 16:16:54 - [VPN Log]: Changing to directory '/etc/ipsec.d/crls'
    Oct 29 16:16:54 - [VPN Log]: Warning: empty directory 

  • 10.1.2.0.2 OID not listening after database patch 10.0.5

    Hi
    I've installed database patch 10.0.5 to an Oracle Infrastructure 10.1.2.0.2. The software and scripts installed with no problems. I started the OID server using:
    opmnctl start process-type=OID
    Which always worked before and it returns with no errors. But OID is not listening on port 389. dcmctl start will throw an error trying to connect to OID.
    Any ideas?

    The readme for the patch has very detailed instructions !
    OID needs to be up as you say plus the other components. But there is a good prereq checker before you run it.
    If worried do a backup of $OH , the inventory and the IASDB then give it a try, if it fails just restore.

  • Listener not listening instance

    hi,
    I am strange why listener is not listening instance
    listener and instance are up
    anyone could help me??
    I can give you more details as you need
    [oracle@fsze88linux ~]$ lsnrctl status
    LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 19-DEC-2009 18:03:35
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
    STATUS of the LISTENER
    Alias                     LISTENER
    Version                   TNSLSNR for Linux: Version 11.1.0.6.0 - Production
    Start Date                19-DEC-2009 17:52:08
    Uptime                    0 days 0 hr. 11 min. 27 sec
    Trace Level               off
    Security                  ON: Local OS Authentication
    SNMP                      OFF
    Listener Parameter File   /u01/app/oracle/product/11.1.0/db_1/network/admin/listener.ora
    Listener Log File         /u01/app/oracle/diag/tnslsnr/fsze88linux/listener/alert/log.xml
    Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))
    Services Summary...
    Service "test123" has 1 instance(s).
      Instance "test123", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    [oracle@fsze88linux ~]$
    [oracle@fsze88linux ~]$ export ORACLE_SID=test123
    [oracle@fsze88linux ~]$ sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.6.0 - Production on Sat Dec 19 18:06:42 2009
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Connected to an idle instance.
    SQL> select instance_name, version, host_name, status
    , database_status, to_char(startup_time,'DD-MON-YYYY HH:MI:SS') strtd
    from v$instance;  2    3 
    INSTANCE VERSION    HOSTNAME         STATUS      DATABASE_STATUS   STARTED
    test123  11.1.0.6.0 fsze88linux.wor OPEN      ACTIVE         19-12?-2009 06:09:47
                  kgroup

    Paul M. ,
    I feel this question is still not solved.
    content of listener.ora
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = test123)
          (ORACLE_HOME = /u01/app/oracle/product/11.1.0/db_1)
          (SID_NAME = test123)
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS_LIST =
            (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
      )tnsnames.ora
    TEST123 =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = SHARED)
          (SERVICE_NAME = test123)
      )yes, I can login that database test123. But lsnrctl status is UNKOWN.
    [oracle@fsze88linux ~]$ lsnrctl status
    LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 19-DEC-2009 23:14:15
    Copyright (c) 1991, 2007, Oracle.  All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
    STATUS of the LISTENER
    Alias                     LISTENER
    Version                   TNSLSNR for Linux: Version 11.1.0.6.0 - Production
    Start Date                19-DEC-2009 23:11:54
    Uptime                    0 days 0 hr. 2 min. 21 sec
    Trace Level               off
    Security                  ON: Local OS Authentication
    SNMP                      OFF
    Listener Parameter File   /u01/app/oracle/product/11.1.0/db_1/network/admin/listener.ora
    Listener Log File         /u01/app/oracle/diag/tnslsnr/fsze88linux/listener/alert/log.xml
    Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))
    Services Summary...
    Service "test123" has 1 instance(s).
      Instance "test123", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfullyis that cause of static pointing to that instance test123?
    But why dynamic pointing is not work....
    I feel very confused....
    help help....

  • UDP PORT 445 Not listed in System Process

    Hi! Can you help me? I need the UDP PORT 445 listed on SYSTEM Process. 
    I open UDP PORT 445 on Firewall (WSBS 2011), but in Syshelp (symatech validation too) the result is:
    Title: One or more network services, ports, protocols or associated processes may need attention
    Product: Backup Exec Server
    Status: Warning
    Details:
    Warning SYSTEM's UDP port 445 is not open or listening.
    Warning Port is not open or listening.
    UDP Process: System
    Ok SYSTEM is the correct process for UDP port 137
    Ok Port 137 with protocol UDP is open on the following IP addresses: - 25.54.28.213
    - 169.254.41.25
    - 169.254.244.222
    - 192.168.0.6
    - 192.168.1.2
    Ok Process System has port 137 with protocol UDP open.
    Ok Process System has port 137 with protocol UDP open.
    Ok Process System has port 137 with protocol UDP open.
    Ok Process System has port 137 with protocol UDP open.
    Ok Process System has port 137 with protocol UDP open.
    Information Network service name not defined. Test skipped.
    Information Default settings - Network Service Name: netbios-ns Port: 137 Protocol: UDP Process: System
    Ok SYSTEM is the correct process for UDP port 138
    Ok Port 138 with protocol UDP is open on the following IP addresses: - 25.54.28.213
    - 169.254.41.25
    - 169.254.244.222
    - 192.168.0.6
    - 192.168.1.2
    Ok Process System has port 138 with protocol UDP open.
    Ok Process System has port 138 with protocol UDP open.
    Ok Process System has port 138 with protocol UDP open.
    Ok Process System has port 138 with protocol UDP open.
    Ok Process System has port 138 with protocol UDP open.
    Information Network service name not defined. Test skipped.
    Information Default settings - Network Service Name: netbios-dgm Port: 138 Protocol: UDP Process: System
    Ok SYSTEM is the correct process for TCP port 445
    Ok Port 445 with protocol TCP is open on the following IP addresses: - 0.0.0.0
    Ok Process System has port 445 with protocol TCP open.
    Information Network service name not defined. Test skipped.
    Information Default settings - Network Service Name: microsoft-ds Port: 445 Protocol: TCP Process: System

    Hi,
    à
    I need the UDP PORT 445 listed on SYSTEM Process.
    à
    Warning SYSTEM's UDP port 445 is not open or listening.
    Based on your description, I’m a little confused with this issue. Please run following commands with administrator
    permission and monitor the result. Would you please check and confirm whether any process listened the UDP port 445?
    netstat –ab
    netstat -a | find /i "445"
    In addition, I noticed that you use Syshelp (Symantec validation tool) to check. I suggest that you would post
    the warning message in Symantec Forum and confirm this issue. I believe we will get a better assistance there.
    If anything I misunderstand, please don’t hesitate to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

Maybe you are looking for