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.

Similar Messages

Filr 1.1 not listening on default port 8443

Hi all,
may be someone else experienced this:
For testing purposes i installed Filr Release 1.1.0.407 in a Fusion 7.1 VM without any error messages. The only difference compared to the default VM settings is, that i limited the RAM size to 2,5 GB (default 8 GB).
After finishing the initial conficuration in the management portal i tried to configure the site, user source and so on but found ,that the applience isn't listening on port 8443...
Currently i'm unable to find any log entry where i can find the reason that port 8443 isn't bound. Can somebody help?
Regards, David

DThielheim wrote:
> For testing purposes i installed Filr Release 1.1.0.407 in a Fusion
> 7.1 VM without any error messages. The only difference compared to the
> default VM settings is, that i limited the RAM size to 2,5 GB
> (default 8 GB).
>
> After finishing the initial conficuration in the management portal i
> tried to configure the site, user source and so on but found ,that the
> applience isn't listening on port 8443...
>
> Currently i'm unable to find any log entry where i can find the reason
> that port 8443 isn't bound. Can somebody help?
Once you've gone through the initial config, the Tomcat stuff on port
8443 should come up automatically. I wonder if the lowered RAM setting
is causing a problem. Try increasing to 4GB and see if that makes a
difference.
Your world is on the move. http://www.novell.com/mobility/
Supercharge your IT knowledge. http://www.novell.com/techtalks/

Mac mail service isnt listening on default ports at all other than SMTP

Mac mail service isnt listening on default ports at all other than SMTP.
I can port scan locally and here is what's listening
Port Scan has started…
Port Scanning host: <IPADDRESS>
     Open TCP Port:     25             smtp
     Open TCP Port:     53             domain
     Open TCP Port:     80             http
     Open TCP Port:     88             kerberos
     Open TCP Port:     106            3com-tsmux
     Open TCP Port:     311            asip-webadmin
     Open TCP Port:     389            ldap
     Open TCP Port:     443            https
     Open TCP Port:     464            kpasswd
     Open TCP Port:     587            submission
     Open TCP Port:     625            dec_dlm
     Open TCP Port:     749            kerberos-adm
Port Scan has completed…
Mail service is on.

first place to start is always /var/log/system.log
stop/start mail service while watching that log.
You will probably catch some dovecot/imap lines that will yield clues.
Post results.

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

Mac not listening to SSH port

When I try to access the server remotely, it's giving me with an error:
ssh_exchange_identification: Connection closed by remote host
The firewall on Mac is disabled and all the traffic are allowed on my router to access the Mac from public IP. I'm using a custom port 52458 to connect to SSH on Mac and I can telnet to it locally and remotely. When I run telnet localhost 52458, it works but when I run netstat -an | grep ssh or netstat -an | grep 52458 it's not returning any values. I tried running netstat -l to view all listeners but SSH is not listed. The way I edited SSH port is by editing /etc/services and replacing ssh port 22 to 52458. Here is the report of ssh -vv -p52458 admin@localhost
ssh -vv -p52458 admin@localhost
OpenSSH_5.1p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to localhost [::1] port 52458.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /var/root/.ssh/identity type -1
debug1: identity file /var/root/.ssh/id_rsa type -1
debug1: identity file /var/root/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_5.1
debug1: match: OpenSSH_5.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1
debug2: fd 4 setting O_NONBLOCK
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-h ellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes19 2-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes19 2-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,[email protected],hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,[email protected],hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,[email protected],zlib
debug2: kex_parse_kexinit: none,[email protected],zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-h ellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes19 2-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes19 2-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,[email protected],hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,[email protected],hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,[email protected]
debug2: kex_parse_kexinit: none,[email protected]
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 130/256
debug2: bits set: 530/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '[localhost]:52458' is known and matches the RSA host key.
debug1: Found key in /var/root/.ssh/known_hosts:7
debug2: bits set: 532/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /var/root/.ssh/identity (0x0)
debug2: key: /var/root/.ssh/id_rsa (0x0)
debug2: key: /var/root/.ssh/id_dsa (0x0)
debug1: Authentications that can continue:
publickey,gssapi-keyex,gssapi-with-mic,password,keyboard-interactive
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug2: we did not send a packet, disable method
debug1: Next authentication method: gssapi-with-mic
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug2: we did not send a packet, disable method
debug1: Next authentication method: publickey
debug1: Trying private key: /var/root/.ssh/identity
debug1: Trying private key: /var/root/.ssh/id_rsa
debug1: Trying private key: /var/root/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug2: input_userauth_info_req
debug2: input_userauth_info_req: num_prompts 1
Password:
debug2: input_userauth_info_req
debug2: input_userauth_info_req: num_prompts 0
debug1: Authentication succeeded (keyboard-interactive).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Requesting [email protected]
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug2: channel 0: request shell confirm 1
debug2: fd 4 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Last login: Thu Jan 3 15:29:33 2013
Welcome to Darwin!
admins-mac-mini:~ admin$ exit
logout
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype [email protected] reply 0
debug2: channel 0: rcvd eow
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug2: channel 0: rcvd close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
Connection to localhost closed.
Transferred: sent 1888, received 2168 bytes, in 562.1 seconds
Bytes per second: sent 3.4, received 3.9
debug1: Exit status 0
Any help is greatly appreciated.

admins-mac-mini:/Users/admin root# lsof -i:ssh -sTCP:LISTEN
lsof: unsupported TCP/TPI info selection: C
lsof: unsupported TCP/TPI info selection: P
lsof: unsupported TCP/TPI info selection: :
lsof: unsupported TCP/TPI info selection: L
lsof: unsupported TCP/TPI info selection: I
lsof: unsupported TCP/TPI info selection: S
lsof: unsupported TCP/TPI info selection: T
lsof: unsupported TCP/TPI info selection: E
lsof: unsupported TCP/TPI info selection: N
lsof 4.77
latest revision: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/
latest FAQ: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/FAQ
latest man page: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_man
usage: [-?abhlnNoOPRstUvV] [+|-c c] [+|-d s] [+D D] [+|-f[cfgGn]]
[-F [f]] [-g [s]] [-i [i]] [-k k] [+|-L [l]] [-m m] [+|-M] [-o [o]]
[-p s] [+|-r [t]] [-S [t]] [-T [t]] [-u s] [+|-w] [-x [fl]] [--] [names]
Use the ``-h'' option to get more help information.

Looking at protocols on non default ports in Microsoft Message Analyzer

I have previously been using Microsoft Network Monitor. I'd like to migrate to Microsoft Message Analyzer but I cannot find out how to view network traffic as a certain protocol (in my case TDS, the protocol SQL Server uses) unless it has the default port.
For TDS the default TCP port is 1433 however I need to be able to look at TDS traffic coming on different TCP ports.
It was possible to do this in Network Monitor by editing the switch statement in the TCP parser to add the ports I required along with 1433 and then rebuilding the parsers. In wireshark it's even simpler as you just select the traffic you want and say "View
as TDS" however wireshark's TDS parsing is not as good as Microsoft's and we need the parsing to be as accurate as possible.
Does anyone know how to parse traffic as particular protocols if they are not on the default port in Message Analyzer?
Many thanks
Rob

With Message Analyzer and alternate Ports, you have to do much the same workaround we did with Network Monitor. We do plan to make it easier in the future, especially given the increased use of alternate ports, but for now changing the OPN (which is NPL
for Message Analyzer), you can make it parse.
You can make the change to TDS.OPN in C:\Users\YOURLOGINNAME\AppData\Local\Microsoft\MessageAnalyzer\OPNAndConfiguration\OPNs\Microsoft\MicrosoftCommon\TDS.OPN. You can find the actor that is defined like this:
autostart actor TDSOverTCP(ReassembledTCP.Server server)
These "act" as a the endpoint looking to match messages from TCP. You'll need to find each location where TDS.Port is defined and add your port. So for instance in the first process rule, you'd changed:
    process server accepts s:ReassembledTCP.VirtualDataSegment
        where s.DestinationPort == Port.TDS && ((inboundCache != null && inboundCache.Buffer != null && inboundCache.Buffer.Count > 0) || IsTDSHeader(s.Payload))
to
    process server accepts s:ReassembledTCP.VirtualDataSegment
        where (s.DestinationPort == Port.TDS || s.DestinationPort == 5555) && ((inboundCache != null && inboundCache.Buffer != null && inboundCache.Buffer.Count > 0) || IsTDSHeader(s.Payload))
If you need more help, please let me know. Keep in mind when you make an OPN change, we have to rebuild and cache things. This might slow down the UI at first, but after everything you normally touch as been re-cached, it will be fast again.
Paul

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

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 ?

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.

SSRS 2012 MP (Native) - Bug with non-default port on SSRS DB, Does not discover

We have test changing SSRS DB instance to default port 1433 and discovery is immediate in SSRS MP. When using non-default port, discovery fails, SSRS instance role is never identified.
Our SSRS is separated into app and db tires across two servers. Have tried creating sql network aliases, but this does not work either.
In our environment, we use non-default port for our SQL DB instances. how do we get SSRS to discover.
Thanks in advance,
Rois Cordova

The Monitoring Pack for Microsoft SQL Server 2012 Reporting Services automatically discovers instances of SSRS 2012 by reading registry.
When the Monitoring Pack for Microsoft SQL Server 2012 Reporting Services is imported for the first time, it creates three new Run As profiles:
• Microsoft SQL Server 2012 Reporting Services Discovery Run As Profile
• Microsoft SQL Server 2012 Reporting Services Monitoring Run As Profile
• Microsoft SQL Server 2012 Reporting Services SCOM SDK Discovery Run As Profile
By default, all discoveries, monitors and rules defined in the SQL Server 2012 Reporting Services management pack use accounts defined in the “Default Action Account”
Run As profile. If the default action account for a given system does not have the necessary permissions to discover or monitor the instance of SQL Server 2012 Reporting Services, then those systems can be bound to more specific credentials in the
“Microsoft SQL Server 2012 Reporting Services …” Run As profiles, which do have access.
It s recommend that you should check the default action account permission.
Roger

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.

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

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

Sles poa not listening on default ports

Similar Messages

Maybe you are looking for