VNC connection refused - Server OS 10.4.10

Before I upgraded my server to 10.4.10, I could connect from home with a VNC Viewer (UltraVNC) for windows. Since the upgrade, when I try to connect, the response is "...incompatible version...". I have double checked all of the settings on Xserve that allowed me to connect before, they are the same. I even tried to upgrade my vnc viewer for windows, but I got the same response.
I keep the MAC OS firewall turned off since we use a hardware firewall between the internet and my system. Is there a security setting with OS 10.4.10 that I don't know about that may be blocking my connection?

Does the VPN service in 10.4.10 work differently than 10.3.9? I have always kept the VPN service turned off since this is handled by the firewall. All of my other systems are still available to me from home, except this server. Just for good measure, I took my laptop to work and tried to access the server from inside the firewall, using UltraVNC as I would from home, but I get the same results, so I wouldn't think the VPN connection, or port settings, etc... would be at issue.
Mike

Similar Messages

  • Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

    All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
    Anyway, here is my problem..
    I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
    So the story is this.. I can send mail from my domains, without issue.  imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
    Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
    Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
    Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
    Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
    Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
    Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
    Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
    Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
    Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
    Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
    Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
    Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
    So in summary
    I can send mail out
    IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
    mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
    mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
    Could anyone shed light on this...
    my main.cf file:
    # Global Postfix configuration file. This file lists only a subset
    # of all 300+ parameters. See the postconf(5) manual page for a
    # complete list.
    # The general format of each line is: parameter = value. Lines
    # that begin with whitespace continue the previous line. A value can
    # contain references to other $names or ${name}s.
    # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
    # POSTFIX STILL WORKS AFTER EVERY CHANGE.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing.  When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    # soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /private/var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/sbin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/libexec/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes.  Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = _postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites.  If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on.  By default,
    azathoth:postfix root#
    azathoth:postfix root# less main.cf
    azathoth:postfix root# more main.cf
    # Global Postfix configuration file. This file lists only a subset
    # of all 300+ parameters. See the postconf(5) manual page for a
    # complete list.
    # The general format of each line is: parameter = value. Lines
    # that begin with whitespace continue the previous line. A value can
    # contain references to other $names or ${name}s.
    # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
    # POSTFIX STILL WORKS AFTER EVERY CHANGE.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing.  When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    # soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /private/var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/sbin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/libexec/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes.  Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = _postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    #myhostname = virtual.domain.tld
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    #mydomain = domain.tld
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites.  If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    #myorigin = $mydomain
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on.  By default,
    # the software claims all active interfaces on the machine. The
    # parameter also controls delivery of mail to user@[ip.address].
    # See also the proxy_interfaces parameter, for network addresses that
    # are forwarded to us via a proxy or network address translator.
    # Note: you need to stop/start Postfix when this parameter changes.
    #inet_interfaces = all
    #inet_interfaces = $myhostname
    #inet_interfaces = $myhostname, localhost
    # The proxy_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on by way of a
    # proxy or network address translation unit. This setting extends
    # the address list specified with the inet_interfaces parameter.
    # You must specify your proxy/NAT addresses when your system is a
    # backup MX host for other domains, otherwise mail delivery loops
    # will happen when the primary MX host is down.
    #proxy_interfaces =
    #proxy_interfaces = 1.2.3.4
    # The mydestination parameter specifies the list of domains that this
    # machine considers itself the final destination for.
    # These domains are routed to the delivery agent specified with the
    # local_transport parameter setting. By default, that is the UNIX
    # compatible delivery agent that lookups all recipients in /etc/passwd
    # and /etc/aliases or their equivalent.
    # The default is $myhostname + localhost.$mydomain.  On a mail domain
    # gateway, you should also include $mydomain.
    # Do not specify the names of virtual domains - those domains are
    # specified elsewhere (see VIRTUAL_README).
    # Do not specify the names of domains that this machine is backup MX
    # host for. Specify those names via the relay_domains settings for
    # the SMTP server, or use permit_mx_backup if you are lazy (see
    # STANDARD_CONFIGURATION_README).
    # The local machine is always the final destination for mail addressed
    # to user@[the.net.work.address] of an interface that the mail system
    # receives mail on (see the inet_interfaces parameter).
    # Specify a list of host or domain names, /file/name or type:table
    # patterns, separated by commas and/or whitespace. A /file/name
    # pattern is replaced by its contents; a type:table is matched when
    # a name matches a lookup key (the right-hand side is ignored).
    # Continue long lines by starting the next line with whitespace.
    # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
    #mydestination = $myhostname, localhost.$mydomain, localhost
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
    #       mail.$mydomain, www.$mydomain, ftp.$mydomain
    # REJECTING MAIL FOR UNKNOWN LOCAL USERS
    # The local_recipient_maps parameter specifies optional lookup tables
    # with all names or addresses of users that are local with respect
    # to $mydestination, $inet_interfaces or $proxy_interfaces.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown local users. This parameter is defined by default.
    # To turn off local recipient checking in the SMTP server, specify
    # local_recipient_maps = (i.e. empty).
    # The default setting assumes that you use the default Postfix local
    # delivery agent for local delivery. You need to update the
    # local_recipient_maps setting if:
    # - You define $mydestination domain recipients in files other than
    #   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
    #   For example, you define $mydestination domain recipients in   
    #   the $virtual_mailbox_maps files.
    # - You redefine the local delivery agent in master.cf.
    # - You redefine the "local_transport" setting in main.cf.
    # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
    #   feature of the Postfix local delivery agent (see local(8)).
    # Details are described in the LOCAL_RECIPIENT_README file.
    # Beware: if the Postfix SMTP server runs chrooted, you probably have
    # to access the passwd file via the proxymap service, in order to
    # overcome chroot restrictions. The alternative, having a copy of
    # the system passwd file in the chroot jail is just not practical.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify a bare username, an @domain.tld
    # wild-card, or specify a [email protected] address.
    #local_recipient_maps = unix:passwd.byname $alias_maps
    #local_recipient_maps = proxy:unix:passwd.byname $alias_maps
    #local_recipient_maps =
    # The unknown_local_recipient_reject_code specifies the SMTP server
    # response code when a recipient domain matches $mydestination or
    # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
    # and the recipient address or address local-part is not found.
    # The default setting is 550 (reject mail) but it is safer to start
    # with 450 (try again later) until you are certain that your
    # local_recipient_maps settings are OK.
    unknown_local_recipient_reject_code = 550
    # TRUST AND RELAY CONTROL
    # The mynetworks parameter specifies the list of "trusted" SMTP
    # clients that have more privileges than "strangers".
    # In particular, "trusted" SMTP clients are allowed to relay mail
    # through Postfix.  See the smtpd_recipient_restrictions parameter
    # in postconf(5).
    # You can specify the list of "trusted" network addresses by hand
    # or you can let Postfix do it for you (which is the default).
    # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
    # clients in the same IP subnetworks as the local machine.
    # On Linux, this does works correctly only with interfaces specified
    # with the "ifconfig" command.
    # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
    # clients in the same IP class A/B/C networks as the local machine.
    # Don't do this with a dialup site - it would cause Postfix to "trust"
    # your entire provider's network.  Instead, specify an explicit
    # mynetworks list by hand, as described below.
    # Specify "mynetworks_style = host" when Postfix should "trust"
    # only the local machine.
    #mynetworks_style = class
    #mynetworks_style = subnet
    #mynetworks_style = host
    # Alternatively, you can specify the mynetworks list by hand, in
    # which case Postfix ignores the mynetworks_style setting.
    # Specify an explicit list of network/netmask patterns, where the
    # mask specifies the number of bits in the network part of a host
    # address.
    # You can also specify the absolute pathname of a pattern file instead
    # of listing the patterns here. Specify type:table for table-based lookups
    # (the value on the table right-hand side is not used).
    #mynetworks = 168.100.189.0/28, 127.0.0.0/8
    #mynetworks = $config_directory/mynetworks
    #mynetworks = hash:/etc/postfix/network_table
    # The relay_domains parameter restricts what destinations this system will
    # relay mail to.  See the smtpd_recipient_restrictions description in
    # postconf(5) for detailed information.
    # By default, Postfix relays mail
    # - from "trusted" clients (IP address matches $mynetworks) to any destination,
    # - from "untrusted" clients to destinations that match $relay_domains or
    #   subdomains thereof, except addresses with sender-specified routing.
    # The default relay_domains value is $mydestination.
    # In addition to the above, the Postfix SMTP server by default accepts mail
    # that Postfix is final destination for:
    # - destinations that match $inet_interfaces or $proxy_interfaces,
    # - destinations that match $mydestination
    # - destinations that match $virtual_alias_domains,
    # - destinations that match $virtual_mailbox_domains.
    # These destinations do not need to be listed in $relay_domains.
    # Specify a list of hosts or domains, /file/name patterns or type:name
    # lookup tables, separated by commas and/or whitespace.  Continue
    # long lines by starting the next line with whitespace. A file name
    # is replaced by its contents; a type:name table is matched when a
    # (parent) domain appears as lookup key.
    # NOTE: Postfix will not automatically forward mail for domains that
    # list this system as their primary or backup MX host. See the
    # permit_mx_backup restriction description in postconf(5).
    #relay_domains = $mydestination
    # INTERNET OR INTRANET
    # The relayhost parameter specifies the default host to send mail to
    # when no entry is matched in the optional transport(5) table. When
    # no relayhost is given, mail is routed directly to the destination.
    # On an intranet, specify the organizational domain name. If your
    # internal DNS uses no MX records, specify the name of the intranet
    # gateway host instead.
    # In the case of SMTP, specify a domain, host, host:port, [host]:port,
    # [address] or [address]:port; the form [host] turns off MX lookups.
    # If you're connected via UUCP, see also the default_transport parameter.
    #relayhost = $mydomain
    #relayhost = [gateway.my.domain]
    #relayhost = [mailserver.isp.tld]
    #relayhost = uucphost
    #relayhost = [an.ip.add.ress]
    # REJECTING UNKNOWN RELAY USERS
    # The relay_recipient_maps parameter specifies optional lookup tables
    # with all addresses in the domains that match $relay_domains.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown relay users. This feature is off by default.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify an @domain.tld wild-card, or specify
    # a [email protected] address.
    #relay_recipient_maps = hash:/etc/postfix/relay_recipients
    # INPUT RATE CONTROL
    # The in_flow_delay configuration parameter implements mail input
    # flow control. This feature is turned on by default, although it
    # still needs further development (it's disabled on SCO UNIX due
    # to an SCO bug).
    # A Postfix process will pause for $in_flow_delay seconds before
    # accepting a new message, when the message arrival rate exceeds the
    # message delivery rate. With the default 100 SMTP server process
    # limit, this limits the mail inflow to 100 messages a second more
    # than the number of messages delivered per second.
    # Specify 0 to disable the feature. Valid delays are 0..10.
    #in_flow_delay = 1s
    # ADDRESS REWRITING
    # The ADDRESS_REWRITING_README document gives information about
    # address masquerading or other forms of address rewriting including
    # username->Firstname.Lastname mapping.
    # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
    # The VIRTUAL_README document gives information about the many forms
    # of domain hosting that Postfix supports.
    # "USER HAS MOVED" BOUNCE MESSAGES
    # See the discussion in the ADDRESS_REWRITING_README document.
    # TRANSPORT MAP
    # See the discussion in the ADDRESS_REWRITING_README document.
    # ALIAS DATABASE
    # The alias_maps parameter specifies the list of alias databases used
    # by the local delivery agent. The default list is system dependent.
    # On systems with NIS, the default is to search the local alias
    # database, then the NIS alias database. See aliases(5) for syntax
    # details.
    # If you change the alias database, run "postalias /etc/aliases" (or
    # wherever your system stores the mail alias file), or simply run
    # "newaliases" to build the necessary DBM or DB file.
    # It will take a minute or so before changes become visible.  Use
    # "postfix reload" to eliminate the delay.
    #alias_maps = dbm:/etc/aliases
    #alias_maps = hash:/etc/aliases
    #alias_maps = hash:/etc/aliases, nis:mail.aliases
    #alias_maps = netinfo:/aliases
    # The alias_database parameter specifies the alias database(s) that
    # are built with "newaliases" or "sendmail -bi".  This is a separate
    # configuration parameter, because alias_maps (see above) may specify
    # tables that are not necessarily all under control by Postfix.
    #alias_database = dbm:/etc/aliases
    #alias_database = dbm:/etc/mail/aliases
    #alias_database = hash:/etc/aliases
    #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
    # ADDRESS EXTENSIONS (e.g., user+foo)
    # The recipient_delimiter parameter specifies the separator between
    # user names and address extensions (user+foo). See canonical(5),
    # local(8), relocated(5) and virtual(5

    Ok 1st one. The warning restriction message relates to this line in main.cf:
    smtpd_helo_restrictions = permit_sasl_authenticated  permit_mynetworks  check_helo_access hash:/etc/postfix/helo_access  reject_non_fqdn_hostname  reject_invalid_hostname  permit reject_invalid_helo_hostname
    The last reject occurs after the single word "permit" and is ignored.
    However, that's not the problem.
    I'm not exactly sure what's happening, but this might be a clue.
    It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions.  You might need to ramp up the debug level to get a better idea.
    You could check if it's being created by "netstat -a | grep private/policy" in terminal.
    My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up.  Private/policy I think relates to grey listing.  Maybe gives you a hint.

  • "Connect to server" inserts "afp://" in front of "vnc://"? 10.4.11

    Hi All: I have a macbook running 10.4.11 connecting to the internet through a wireless router. I'm trying to connect to a vnc server in a remote location. When I go to "connect to server" and enter:
    vnc://[ip address]
    the "connecting to server" window pops up, but I see in there "connecting to afp://vnc//[ip address]"
    where it seems to be inserting "afp://" in front of what I entered, and stripping out the colon after "vnc"
    What am I doing wrong?

    Hi BD: I'm not sure I understand all your questions...let me clarify the topology.
    The system I'm trying to connect to has a VNC server running on it and is accessible through a public IP. I'm trying to connect to that system across the 'net from my laptop. I don't have access to that system, but their IT guy assures me people are able to connect to it remotely and screen share.
    Also, I'm able to connect to the remote computer using AFP...it's just VNC that's not connecting.
    My laptop is on a local subnet connecting through a WAP that connects to a DSL router. I have not configured any special PAT or forwarding on my end that would be messing with an outgoing VNC connection. Again, I'm trying to connect as a client to a remote VNC server so I can share the screen of the server (I'm pretty sure the "server" is just a Mac with sharing enabled).

  • Connection refused Error while writing file to FTP server.

    Hi All,
    We got below error while writing file to FTP server. Any one have any idea on this?
    sABCS_1.0_8e88588d4fb54ebd2ac7ef66c8421d52.tmp/writeEncryptedFile.wsdl [ Put_ptt::Put(opaque) ] - Could not invoke operation 'Put' against the 'FTP Adapter' due to:
    ORABPEL-11429
    Error sending file to FTP Server.
    Unable to send file to server. [Caused by: Connection refused]
    Please ensure 1. Specified remote output Dir has write permission 2. Output filename has not exceeded the max chararters allowed by the OS and 3. Remote File System has enough space.

    Hmmm ...
    Same issue as your post from three months' earlier?
    Re: Error while putting file in sftp location.

  • Connection refused in SQL Server 2005

    I have just installed SQL Server 2005 Developer Edition, and
    I still have SQL Server 7 running on port 1433.
    I have many SQL7 databases connected to CF7.0.2
    When I try to connect to a new database that I can read and
    write to in SQL2005, I get a connection refused error.
    I'm not sure what port to connect to as SQL2005 port shows 0
    which apparently means dynamic port allocation.
    When I try port 1434 I get connection refused.
    I have user name set to sa (and this is enabled in SQL2005)
    and no password (windows authentication). Same result if user name
    is blank.
    Anyone got any idea what these settings should be?
    Doug

    I have now switched off dynamic port allocation and changed
    the port to 1435 and I think I now connect to SQL Server 2005, but
    I now get the error:
    The user is not associated with a trusted SQL Server
    connection.
    I have tried using sa and tried setting up another user name,
    but cannot get past this error.
    Any help would be appreciated.
    Doug

  • SQL Server 2000/CFMX 7 - connection refused: connect

    Hi all,
    I have been trying to troubleshoot this for a few weeks now,
    I have looked high and low and tried multiple solutions that worked
    for other people, none have worked for me.
    I have SQL Server 2000 Version 8 and Coldfusion 7.0.2.
    I can't seem to make a database connect in Administrator. I
    have tried changing the port that SQL Server listens on, I made a
    new security role in SQL Server specifically for the database I'm
    creating, I tried making an ODBC connection (which can see the SQL
    Server) in windows then connecting to that, nothing is working.
    I thought it might be the windows firewall, it isn't since it
    is off, my TCP/IP protocol is enabled, I am running out of ideas.
    If anyone can suggest anything, please do this is what I see
    everytime.
    Connection verification failed for data source: IFDA
    java.sql.SQLException: [Macromedia][SQLServer JDBC
    Driver]Error establishing socket. Connection refused: connect
    The root cause was that: java.sql.SQLException:
    [Macromedia][SQLServer JDBC Driver]Error establishing socket.
    Connection refused: connect
    I'm dying over here.
    Thanks.

    This might be a dumb question, but have you searched Google
    groups? Its one of the first places I go when I get error messages
    I don't understand.
    Googling this:
    "java.sql.SQLException: [Macromedia][SQLServer JDBC
    Driver]Error establishing socket. Connection refused: connect"
    ..gave me 84 results (ok, a lot of them point back to these
    forums but I still find searching thru Google easier than using the
    built in search) - here's a
    Link
    hth - cheers.

  • ReportViewer control not connecting to the report server - Connection refused

    I'm having an issue with connecting to SQL report server using the ReportViewer control.  Thing is when I connect to the reporting services web service (http://10.3.27.80/ReportServer/ReportService2010.asmx)
    it works fine and I can successfully pull the data I need.  But when I use the web control, its then that I cannot connect.  Here's my code:
    ASP.net code:
    <%@ Page Title="Reports" Language="C#" MasterPageFile="~/Site.Master" AutoEventWireup="true" CodeBehind="Results.aspx.cs" Inherits="RSReportViewer.Results" %>
    <%@ Register Assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" Namespace="Microsoft.Reporting.WebForms" TagPrefix="rsweb" %>
    <asp:Content ID="BodyContent" ContentPlaceHolderID="MainContent" runat="server">
    <rsweb:ReportViewer ID="ReportViewer2" runat="server" Width="90%" ProcessingMode="Remote">
    <ServerReport ReportServerUrl="http://10.3.27.80:80/" />
    </rsweb:ReportViewer>
    Error message:
    ConnectionRefused
    Inner Exception: No connection could be made because the target machine actively refused it 176.74.176.178:8080
    I have not got the IP signified above configured anywhere throughout my solution!  So not sure where its getting that in the message.
    Stack trace:
       at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods()
       at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname)
       at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.SetConnectionSSLForMethod(String methodname)
       at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
       at Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
       at Microsoft.Reporting.WebForms.SoapReportExecutionService.LoadReport(String report, String historyId)
       at Microsoft.Reporting.WebForms.ServerReport.EnsureExecutionSession()
       at Microsoft.Reporting.WebForms.ServerReport.SetParameters(IEnumerable`1 parameters)
       at RSReportViewer.Results.Page_Load(Object sender, EventArgs e) in c:\Users\admin\Desktop\RSViewer\RSViewer\RSReportViewer\Results.aspx.cs:line 71
       at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
       at System.Web.UI.Control.OnLoad(EventArgs e)
       at System.Web.UI.Control.LoadRecursive()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    Firewalls are disabled between the two boxes. 
    Thanks in advance for any pointers!

    Hi rmccabe82,
    Generally, “actively refused it" means that the host sent a reset instead of an acknowledge when you tried to connect. As per my understanding, the issue can be caused by the process that is hosting the service is not listening on that port, this may be
    because it is not running at all or because it is listening on a different port. Please try to ping ‘netstat –anb’ (requires admin privileges) to verify that it is running and listening on the expected port.
    Furthermore, please make sure the user has permissions to access the report server.
    References:
    http://www.smartftp.com/support/kb/connection-refused-f58.html
    http://stackoverflow.com/questions/9695224/no-connection-could-be-made-because-the-target-machine-actively-refused-it-127-0
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Bi Server Connection Refused

    Hi, i've installed BI Server EE on a virtual machine.
    I press "Start OC4J" and the batch file starts as i think. When i try to start "BI publisher" i see a Java Exception "Connection Refused" Some idea?

    Hi MIcheal, i'm working on the same VM, i've got as the db as publisher on this VM, and i try connect to localhost.
    The error log is :
    <TIMESTAMP> NOTIFICATION connect to NQSSECONDARYCCS=;PORT=;SSLKEYSTOREPASSWORD=***;PRIMARYCCS=;TRUSTANYSERVER=;LOGFILEPATH=<PATH>;SECONDARYCCSPORT=;TRUSTSTOREPASSWORD=***;LOGLEVEL=;SSL=;HOST=VM_ODI;CATALOG=;PASSWORD=***;
    <timestamp> WARNING java.net.ConnectException: Connect Refused: connect
    java.sql.SQLException: java.net.ConnectException:Connection Refused: connect
    at oracle.bi.jdbc.AnaJdbcDriver.conncetToNQSNode<AnaJdbcDriver.java:413>

  • Client-Proxy-Server:  Connection refused

    I was meddling with a client-proxy-server toy program.
    Pardon my poor code construction. I have never had any previous knowledge in this field.
    I have created  a client side program with my main that handles IO serially.
    ProxY consists of 2 unscynchronized threads each interacts with client and server respectively.
    Packet exchange within ProxY is relayed using a PacketBuffer object.
    Server consist of a single threaded service. Below is the code for my main.
    import java.io.IOException;
    import java.net.ServerSocket;
    import java.net.Socket;
    import java.io.InputStream;
    import java.io.OutputStream;
    import java.util.Scanner;
    public class TestProxy
         public static void main(String[] args) throws IOException
              final int SERVER_PORT = 19989;
              final int PROXY_PORT = 19988;
              ServerSocket proxyServerSoc = new ServerSocket(PROXY_PORT);
              Socket proxyClientSoc = new Socket("127.0.0.9",SERVER_PORT); //127.0.0.9 is server IP
              Server serv = new Server(SERVER_PORT);                             //Server started
              ProxY prox = new ProxY(proxyClientSoc, proxyServerSoc);            //proxy started
              //Start Client side;
              Socket toProxy = new Socket("127.0.0.1", PROXY_PORT);
              InputStream in = toProxy.getInputStream();
              OutputStream out = toProxy.getOutputStream();
              Scanner keyboard = new Scanner(System.in);
              String input;
              while(true)
                   System.out.println("Enter data  : ");
                   input = keyboard.nextLine();
                   if(input.equals("exit")) break;
                   System.out.println("data in BYTE: "+input.getBytes());
                   System.out.println("Sending data to server ...");
                   out.write(input.getBytes());
                   try{
                        Thread.sleep(100);
                   catch(InterruptedException e)
                        e.printStackTrace();
                   System.out.println("Received from server :" + in.toString());
    }Compilation is a success, but there is a runtime error...
    When i attempt to run the program for the first time(tried on XP, Vista, 7, jdk1.6), windows prompts for network permission.
    Before i can [edit]unblock[edit] it, my console window shows following error
    C:\java\proxy>javac *.java
    C:\java\proxy>java TestProxy
    Exception in thread "main" java.net.ConnectException: Connection refused: connec
    t
            at java.net.PlainSocketImpl.socketConnect(Native Method)
            at java.net.PlainSocketImpl.doConnect(Unknown Source)
            at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
            at java.net.PlainSocketImpl.connect(Unknown Source)
            at java.net.SocksSocketImpl.connect(Unknown Source)
            at java.net.Socket.connect(Unknown Source)
            at java.net.Socket.connect(Unknown Source)
            at java.net.Socket.<init>(Unknown Source)
            at java.net.Socket.<init>(Unknown Source)
            at TestProxy.main(TestProxy.java:15)
    C:\java\proxy>Can someone advise me where might i be possibly wrong?
    Edited by: J-Ideas on Mar 10, 2010 10:50 PM

                   out.write(input.getBytes());
                   try{
                        Thread.sleep(100);
                   catch(InterruptedException e)
                        e.printStackTrace();
                   }What's that for?
                   System.out.println("Received from server :" + in.toString());No no no. 'in' is an input stream. in.toString() is just a string representation of that object. It certainly isn't anything received from the server. If you want to receive data from the server you must call one of the in.read() methods.
    When i attempt to run the program for the first time(tried on XP, Vista, 7, jdk1.6), windows prompts for network permission.
    Before i can [edit]unblock[edit] it, my console window shows following errorYou should separate your program into three: server, proxy, and client, each with their own main() methods, so you can deal with these problems one at a time.

  • Connection refused from Java in Windows to remote postgresql Linux server

    I fail to connect from windows to a remote postgresql linux server. The SQLEexception received is same as the SQLException that happen to the localhost connection to postgresql where the condition of postgresql not started or not start with -i option to allow tcp/ip connection. The SQLException is SQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
    Please help..
    Java class file with the following codes:
    String url = "jdbc:postgresql://servername:5432/databasename";
    Connection con = DriverManager.getConnection(url,"username","password");
    The /var/lib/pgsql/data/pg_hba.conf have the following configuration:
    # TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
    local all all trust
    host all all 127.0.0.1 255.255.255.255 trust
    hostssl all all 219.94.117.8 255.255.255.255 trust
    hostssl all all 0.0.0.0. 0.0.0.0 trust
    host all all 219.94.117.8 255.255.255.255 trust
    host all all 0.0.0.0 0.0.0.0 trust
    The /var/lib/pgsql/data/postgresql.conf have the following configuration:
    # Connection Parameters
    tcpip_socket = true
    #ssl = false
    #max_connections = 32
    #superuser_reserved_connections = 2
    #port = 5432
    #hostname_lookup = false
    #show_source_port = false
    The postgresql start in the /etc/init.d directory with the command ./postgresql start
    postgres 16923 0.1 0.3 9556 1956 pts/0 S 01:58 0:00 /usr/bin/postmaster -p 5432 -i
    postgres 16925 0.0 0.3 10548 1948 pts/0 S 01:58 0:00 postgres: stats buffer process
    postgres 16926 0.0 0.3 9580 1968 pts/0 S 01:58 0:00 postgres: stats collector process
    root 16931 0.0 0.1 2664 716 pts/0 R 01:58 0:00 ps aux

    On my machine (OS X ) I had trouble with postgresql refusing to notice the -i option in the configuration file. Instead I manually had to specifiy postmaster -i ...
    Also check your firewall settings. I also could not get localhost to work, I had to use the actual IP address of the machine, ie not 127.0.0.1. Use telnet hostip 5432 to check if you can get a connection. For my situation once telnet would connect, then JDBC started working too. Then localhost started working too.

  • Connect to message server host failed;WSAECONNREFUSED: Connection refused

    Hi All,
    I am getting the following error when I tried to test the system connectivity from the portal to NSP instance.
    Connection failed. Make sure that Single Sign-On is configured correctly
    I found the following entry in the logs
    Error> occured  >Wed Feb 03 22:43:49,875<   
    RfcException:
        message: Connect to message server host failed
    Connect_PM  TYPE=B MSHOST=abchome.abcsap.local GROUP=SPACE R3NAME=NSP MSSERV=sapmsNSP PCS=1
    ERROR       partner '192.xxx.xxx.123:sapmsNSP' not reached
    TIME        Wed Feb 03 22:43:49 2010
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     1
        Return code: RFC_FAILURE(1)
        error group: 102
        key: RFC_ERROR_COMMUNICATION
    Both NSP and J2E instances are on the same server. OS - win2k3.
    I checked the services file and have the sapmsNSP entry.
    I am able to launch an SAP transaction from System Administration -> Support
    RZ70 from NSP also fails JCo error. SLD_UC RFC itself works fine and the JCo RFC provider SLD_UC program is running
    WEB AS & ITS connections work fine.
    User authentication is from backend, NSP.
    I think I have gone thru all the logs but could not resolve the issue.
    I appreciate any help on this,
    Victor

    I tried to go thru the thread. I did not find any clue as why only server connectivity is failing. ABAP trial version is running fine and the NW trial version is working fine too. These run without crashing. I did a lot of customizing on the portal but dont see any issues except the System Connectivity. Like I mentioned I did UME configuration to point to NSP ABAP instance and I can log into the portal with user credentials that I use to login to ABAP.  I can launch webgui etc without any issues.

  • Error in installing ECC 6... msg server connected nie_conn connection refus

    when i am trying to install ECC 6 i had receive the
    error msg as
    <u><b>msg server connected nie_conn connection refused</b></u>

    Please provide more information:
    - operating system
    - the last lines of sapinst_dev.log with the error in it
    - the workprocess trace dev_w0
    Markus

  • I am set up mac mini and when I test the mail server by sending a mail from administrator to administrator I get the error message 'Diagnostic-Code: X-Postfix; connect to 127.0.0.1[127.0.0.1]:10024: Connection    refused'. Can any one suggest a solution

    I set up mac mini and when I test the mail server by sending a mail from administrator to administrator I get the error message 'Diagnostic-Code: X-Postfix; connect to 127.0.0.1[127.0.0.1]:10024: Connection    refused'. Can any one suggest a solution

    Thanks. Where could I possibly look for a firewall rule. I knowingly did not creat any. My system has internet coming to a Modem which then is connected to a wireless router. I have computers connecting to the router through cable as well as wireless. One of these computers has been our  mailserver using Mercury and Pegasus and that computer has a static IP address. The Mac Mini also has been assigned a different srtatic IP address. I have only set up user account, none of them an email account as I initially expect them to receive only internal mails. Is it necessary that I must set up an email id for each user while setting up the user account. My server id is server.local. So would the email id for local users be [email protected]?

  • "connection refused" when accessing gmail pop server

    I am having a problem connecting to gmail. I get a "connection refused" error when I try to download or upload mail. This problem started last Saturday Aug, 22nd, give or take a day. As for trouble shooting, here's what info I can share. I am connected to the internet because I can browse websites. I was able to access my mail on the gmail website, using the browser interface. On the website, I was able to read new mail that had been sent to me since the problem started, so there's no problem with the account itself. I have made no recent changes to my e-mail client settings and I tried another email client and had the same type of error message come up. POP is enabled in Gmail. I can not run the telnet test provided on gmail because it appears to be only available to PC users. However, I took my iBook down to the local pub, connected to the internet on wifi, and had no problem. My email client performed its normal functions as usual. At this point I gather the problem has something to do with my ISP specifically not being able to see gmail's server, or vice versa. Should I contact gmail to ask them if there is something they can check? If I have to resolve this through my ISP, what should I tell them to look for? Are there any setting in the System Preference Networking Control Panel I should be checking, such as proxies, ethernet, TCP/IP, etc? Thanks

    I have found that I can use "terminal" on my Mac to run a telnet command on gmail's server addresses. It says "connection refused". Pretty much the same thing my e-mail client said. So I am still working under the assumption that the problem has something to do with my ISP specifically not being able to see gmail's servers, or vice versa. But which is more likely? If the problem is with my ISP, should I simply ask them to change my IP address (or their IP address)? This is an area that I am not very familiar with. And there is an added complication that I may not be able to contact the ISP directly. I will have to speak to the landlord, and it will probably be a situation where I will have to tell the landlord what to say to the ISP. So I'm looking for the layman's nutshell way to convey the info to the landlord so that it does not get lost in the translation to the ISP.
    And another point. I am being told that other users on my landlord's network are not having problems with gmail. Is there a way for ME to force the IP address on MY computer to change? Or is that not really the issue? Thanks

  • Getting kicked off of VNC connection when logging into server

    We have noticed that when we log into the VNC server, and sign into the console of the server, that we get kicked off of the VNC connection. If we wait a few seconds then connect again we get the desktop of the server.
    What is causing this? I use JollysFastVNC 0.98.50 (928701) and a coworker of mine uses ChickenoftheVNC, both are on Macs. It is very annoying. I do like that when I'm done and I log off of the console that it also logs me out of the VNC connection. But kicking me out for logging in is absurd.
    Thanks,
    Ben
    PS. The server is Mac OS X 10.6.1 on a Mac Mini last generation, since they just came out with a new one.

    I linked to the free client. That is what runs on the computer that you you turn on in System Preferences --> Sharing, so you are going to want to install that on the server, not the machine you are connecting from. If you installed it on both it doesn't matter—it was there anyway as part of the OS. It is built into the OS, but a reinstall can fix problems and makes sure you have the latest version. The ARD application is what you would use to connect with from the machine you are sitting in front of. That is what costs money. Apple calling the software "client" can be confusing.
    Have you turned on the VNC option under either Screen Sharing or Remote Management. You will need that to connect with a third party VNC app like JollysFastVNC or Tight. If you don't turn that on then the built in Screen Sharing app should just work (accessible from Safari or the Connect to Server dialog in finder by typing vnc://ipofserver)
    It is hard to say if this is a SL bug, or a problem on your network since you only have one machine to test. You could try running Vine Server on your server. You will want to change it's port to something else like 5901, or at least turn off Screen Sharing so it doesn't conflict ports. If you change the port you would connect by typing vnc://ipofserver:5901
    In Vine be sure to use System Server (under Server menu) to keep vine running all the time, even after a reboot.
    Vine:
    http://www.macupdate.com/info.php/id/11283/vine-server-%26-viewer

Maybe you are looking for