search for: portmapped

Displaying 20 results from an estimated 209 matches for "portmapped".

Did you mean: portmapper
2010 Feb 03
2
cannot mount NFS share, portmap problems, what todo?
Hi all, I want to map an NFS share from a remote server to a local CentOS 5.4 server, but have a problem with portmap: root at mercury:[~]$ service portmap restart pmap_getmaps rpc problem: RPC: Unable to receive; errno = Connection reset by peer Stopping portmap: [FAILED] Starting portmap: [ OK ] root at
1998 Dec 15
1
portmap & tcpwrappers
I don't know if this is RedHat 5.1 specific, but be aware that the version of portmap distributed is the enhanced (Wietse Venema) version. That's great, except for two things. The first is documented, but easy to overlook: "In order to avoid deadlocks, the portmap program does not attempt to look up the remote host name or user name...The upshot of all this is that only network
1998 Dec 05
8
portmap vulnerability?
Are there any known vulnerabilities in portmap (redhat''s portmap-4.0-7b)? I''ve been receiving a lot of attempts to access the portmap port on some linuxppc machines I administer by various machines which clearly have no business with mine, and I wonder if this is an attempt to break in to my machines. I''ve searched some archives, but I haven''t yet found any
2008 Mar 27
2
portmap not answering
CentOS 5 updated, Xen host. The portmap on this machine is somehow "stuck" and I can't figure out why. I enabled it to be able to mount a remote nfs share. The first hurdle was that "portmap" didn't appear in the chkconfig list, it was installed with the initial packages but not added to chkconfig. Took me a while to figure this out. Adding and starting it up is no
2007 Dec 04
1
odd behavior with provider yum...
Anybody else noticed this: debug: package provider yum: Executing ''/usr/bin/yum -d 0 -e 0 list available portmap'' err: //nfs_server/Package[portmap]: Failed to retrieve current state of resource: Could not get latest version: Execution of ''/usr/bin/ yum -d 0 -e 0 list availaSearching 100% | =========================| 16 kB 00:03 Error: No
2000 Jan 23
2
portmap messages under /var/log/messages
I am running Redhat 6.1 as a firewall between a cable modem and my home network. Occasionally, I see messages such as these under /var/log/messages: Jan 17 13:38:16 saturn5 portmap[3726]: connect from 24.28.77.200 to dump(): request from unauthorized host Jan 18 14:00:34 saturn5 portmap[1544]: connect from 204.151.148.146 to dump(): request from unauthorized host My assumption is that the
2008 Apr 29
2
Do I need portmap, haldeamon & xfs running on dom0?
Hi all I have a CentOS 5.1 server running Xen and recently installed ConfigServer Firewall (CSF) on the main node to give it some protection. On a daily basis I''m getting an email about portmap. haldeamon and xfs consumming too much resources. The main node, dom0 doesn''t even do anything, and everything is done on the domU''s Here''s a thread I''ve
2003 Jul 30
1
portmap, bind(), and NIS
Greetings I'm running an NIS server that I would very much *not* want to be accessible on some of its interfaces. portmap can be instructed to bind to specific addresses using the -h flag, but this seems to break ypbind. ypbind will attempt to find a server by issuing a broadcast rpc request to the local network. When portmap is not bound to INADDR_ANY, it will not reply to these requests.
2006 Aug 25
1
SELinux targeted - named, portmap and syslogd errors
Yesterday I activated SELinux in targeted mode, then I rebooted and started receiving some error messages in the system services initialization: ====================================================================== audit(1156518721.252:2): avc: denied { read } for pid=2223 comm="syslogd" name="libc-2.3.4.so" dev=dm-0 ino=50441 scontext=user_u:system_r:syslogd_t
2004 Jun 17
0
portmap spoofing in nfsmount
Hi all, I have implemented portmap spoofing in klibc nfsmount (released as klibc-0.144) This is basically a vestigial portmap daemon which gets launched before the mount() call and then just records any transactions it gets to a file and sends back an affirmative reply. There are two ways to use it (this belongs in a README file, but it's too late at night right now): a) Set a fixed
2008 Jul 24
1
selinux & httpd & portmap
Having problems starting httpd & portmapper #service httpd start /usr/sbin/httpd: error while loading shared libraries: libm.so.6: cannot open shared object file: No such file or directory and I traced it to selinux, which I had just turned on for the first time: # sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode:
2012 Mar 04
1
Unable to start nfs server
An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120304/04099724/attachment.html>
2008 Feb 13
1
Linux client cannot mount to NFS-Root: Portmap RPC call returned error 101
Hello all, I have seen various reports on this error posted in the past few years, but was unable to find a resolution to the various postings. I've googled the error messages too, and have hit on various sporadic similar problems encountered with no resolutions .. Apologize if this has been exhaustively queried upon in the past; however, I'd like to try asking again, nevertheless:
2012 Oct 24
2
Why portmap is needed for NFSv4 in CentOS6
Hi all, I have setup a CentOS6.3 x86_64 host to act as a nfs server. According to RHEL6 docs, portmap is not needed when you use NFSv4, but in my host I need to start rpcbind service to make NFSv4 works. My /etc/sysconfig/nfs # # Define which protocol versions mountd # will advertise. The values are "no" or "yes" # with yes being the default MOUNTD_NFS_V2="no"
2010 Feb 03
0
cannot mount NFS share, portmap problems, what todo? [SOLVED]
On Wed, Feb 3, 2010 at 2:40 PM, Geoff Galitz <geoff at galitz.org> wrote: > > > > Should it be running, or not? > > > > > > >root at mercury:[~]$ netstat -ap --inet | grep rpc > > >tcp 0 0 *:sunrpc *:* > LISTEN 6458/portsentry > > >udp 0 0 localhost:filenet-rpc localhost:filenet-rpc
2012 May 31
1
portmap/NIS mystery
Hello all, I have a server on my private network that is configured as an NIS server and mapped to a "public" IP address on a firewall. All other TCP ports (SSH, iperf, you name it) are visible from the outside - but the portmapper-managed ports (port 111 itself and the YPSERV/YPXFRD ports, etc.) are not visible from the outside - even though they are alive and well on the internal
2003 May 20
0
intermittent failure of ability to connect to samba share from win (NT/2k) client
First, my installation is samba 2.2.8 running as a daemon (not inetd) on Solaris 8 configured to use a WINS server and provide authentication via a PDC (same host as WINS server). I do have an lmhosts file in the samba /lib directory with the PDC/WINS server address in it. My globals section; [global] workgroup = WORKGROUP netbios name = SAMBASERVER security =
1998 Dec 03
2
interactions between OPIE-ftpd and RH5.2
Ran into a weird problem, and this seemed a good forum to toss it out into -- if I've gaffed, please let me know. Just upgraded my RH5.0 box to RH5.2. Went well, worked nearly seamlessly. When running 5.0, though, I'd installed the opie-fied ftpd that comes with the most recent opie package (ftp://ftp.inner.net/pub/opie/opie-2.32.tar.gz) and had it work without a hitch. I'd also
2015 Sep 24
0
FreeBSD 10 & default_vsz_limit causing reboots?
Update.? Only a single reboot has occurred since changing defalt_vsz_limit from 384M to 512M.? It would seem that something the users are doing is causing that virtual memory size to be exceeded (possibly a mailbox search?), and when that occurs Dovecot/FreeBSD is not handling the event as smoothly as expected. Here's my dmesg for more basic info. Sep 17 11:25:39 romulus syslogd: kernel boot
2006 Aug 03
2
Icecast behind firewall
Hey List! I am in the process of moving an icecast2 server from a serve in an R&D lab to a virtual machine in the main server area. The servers are both running Debian sarge and are configured identically for icecast minus the bind address and the hostnames. When I try and start the icecast server, using the same init script and running the same version of icecast (2.3.1), the process