similar to: Samba and NT (yes really) server

I''m running Xen 4.1.4 on Fedora 17. I have some CentOS 6 DomUs - an haproxy machine and some tomcat VMs. When clients send requests with: POST /ProposalInterface HTTP/1.1 Content-Type: text/xml Host: www.myhost.co.uk Content-Length: 2099 Expect: 100-continue Connection: Keep-Alive The "continuation" doesn''t happen. The POST is truncated at 1449 bytes, and the

On 4/28/2020 3:17 PM, Chris Adams wrote: > - gateway sends a router solicitation and gets a router advertisement > with "stateful config" set, which tells gateway to do DHCPv6 (but > default route comes from RA) I'm not seeing any outbound IPv6 traffic from my CentOS 7 box on the WAN interface. I do see RA's emitting from the LAN interface, from radvd. Is there

I am having problems implementing Samba using security=domain against a Windows 2008R2 server. I have been able to successfully join the domain via a net rpc join. Anytime I try to access a share through smbclient I get a NT_STATUS_TRUSTED_RELATIONSHIP_FAILURE but nothing in the logs (on either side) seems to be giving me any leads on where to look. The system is locked down to allow NTLv2

Hi. I run SuSE 8.1 and samba here. On the linux machine I have a HP1100A on the parallel port, and a HP-DJ895Cxi on a USB port. I can print ok from this linux machine to both printers. From my laptop, that runs WIN98, I can print to the HP1100A printer. I cannot print to the DJ895Cxi, even if its set up as a network printer. I could do this with SuSE dists up to 8.0. From 8.1 printers are

Once upon a time, Lists <lists at benjamindsmith.com> said: > I understand that it's possible to allow the 4 VM guest systems to each have a > "direct" fixed IP address and access the addresses \via the host network > adapter, while the host retains its fixed IP. If you are running NetworkManager (the default), it's not too hard. Here's an example

Shorewall 4.5.15 3 Interface setup em1 p3p1 p4p4 ppp0 Hi, Since changing to NetworkManger on Fedora 18 I can no longer connect to the DSL Modem, which is connected to Interface em1. When the NetworkManger brings up the interfaces and ppp0, it no longer assigns an IP to em1. If I have ppp0 disabled and NetworkManger brings up the interfaces, em1 gets an IP of 192.168.1.2. Then when I get

Hi, I would like to know if somebody can point me out how to configure several DomUs in a private LAN (for example 192.168.100.0/24) and one DomU with two interfaces (one - 192.168.100.0/24 and two - internet). So far I have enabled in xend-config.sxp: (network-script network-route) (vif-script vif-route) My config files have: /mnt/VM/1.cfg:vif = [''ip=192.168.1.3'']

Hey, I have KVM installed on my Fedora 17 box. I added the network interfaces of the virtual machines to the openvswitch bridge as follows: ____ ____ / VM1\______br0_______/ em1\ \____/ | \____/ | _|_ /VM2\ \____/ virbr0 is the virtual network switch VM1 and VM2 are on the same subnet having tap interfaces vnet0 and vnet1 respectively. em1 is the default

We just got DELL R920 and installed Centos 6.5 on it.? After installation, network not function.? We manually enter IP address, gateway and netmark on "em1".? we also do following: 1. startup NetworkManager 2. /etc/sysconfig/network-scripts/ifcfg-em1? ==> NM_CONTROOLED=yes I tried to startup network and get error message: Bring up interface em1: connection activation failed

My manager tells me a system in the datacenter is down. I go down there, and plug in a monitor-on-a-stick and keyboard. It's up, but no network. I try systemctl restart NetworkManager several times, and ip a shows *no* change. Finally, I do an ifdown, followed by an ifup, and everything's wonderful. My manager thinks that the NM daemon thinks everything's fine, and there've been

I have a physical host with a single physical network adapter. I want to host several VMs on host. (guest1 - guest4) The guest systems are accessible via 192.168.122.* as is the default with qemu/virsh. There are 4 IP addresses being routed to the primary interface on host. I can set up an alias for the NIC and "see" these ip addresses. I understand that it's possible to allow

dear All, I'm facing this routing problem, the setup is actualy part of ltsp, but I think this problem is Centos-specific. The server is a Dell Poweredge R210. The install is standard 6.4, updated. I have one nic facing the public internet: vi /etc/sysconfig/network-scripts/ifcfg-em1 DEVICE=em1 BOOTPROTO=none HWADDR=d4:ae:52:c1:28:2b NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet

Red Hat Enterprise Linux Server release 6.5 (Santiago) selinux is disabled. The following commands were all run on the RedHat Server on which I am running samba. *The following ports are open* 5 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:137 6 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:138 7 ACCEPT tcp --

Hi all, I moved from 8.0-RELEASE to last week's -STABLE: $ uname -v FreeBSD 8.1-STABLE #0: Thu Sep 2 16:38:02 SAST 2010 root@XXXXX:/usr/obj/usr/src/sys/GENERIC and all seems well except my network card is unusable. On boot up: em0: <Intel(R) PRO/1000 Network Connection 7.0.5> port 0x3040-0x305f mem 0xe3200000-0xe321ffff,0xe3220000-0xe3220fff irq 10 at device 25.0 on pci0 em0: Setup

Hello, Anybody else run into problems with biosdevname .0.5..0-2 changing names from p2p1 to em1 when upgrading from biosdevname 0.4.1-3? Darn! I thought biosdevname was to keep the names the same!! -- Stephen Clark *NetWolves Managed Services, LLC.* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark at netwolves.com http://www.netwolves.com

Hi, When I initially boot my system, it fails to bring up the network. Once booted, if I run "systemctl restart network.service", or even stop, wait a while, then start, it starts up fine and all is well. I'm running Fedora 19 (updated). I followed the instructions on this page to set up a bridged network: http://wiki.libvirt.org/page/Networking I note however that I did *not*

hi everyone I'm having a bit of a puzzle on one centos system, I have four interfaces: nm-team1 10.5.6.100 em1 192.168.2.17 em2 192.168.2.18 p3p3 172.25.12.222 I do: ping 10.5.6.17 -I em1 PING 10.5.6.17 (10.5.6.17) from 192.168.2.17 em1: 56(84) bytes of data. 64 bytes from 10.5.6.17: icmp_seq=1 ttl=64 time=0.367 ms the same for -I em2, for -I em1 and naturally for -I nm-team1 - all good.

I'm trying to autoinstall a DELL 9030 desktop with CentOS7 using PXE and Kikstart. I fall in a strange problem (I have several other laptop or desktop using this install process without any problem, kernel and initrd are from a Centos 7.4 iso) - PXE boot start and the desktop load the kernel and the inirtd file - the kernel is booted and at this time the led of the network switch goes down

Hello everyone I am running into some strange issues when configuring networking interfaces on my physical server running Centos 7.5. Let me give you an overview of what's going on: We have a physical server, running CentOS 7.5. This server has one 4 port NIC and one 2 port NIC and a Dell IDRAC port. The first port of the 4 port NIC, em1, is used for Management traffic. The first port of

current setup SIP phone 192.168.1.30 --> linksys wrt54g sveasoft -- INTERNET -- (xl0) Firewall (xl2:172.16.0.50)--> (em1:172.16.0.101) Asterisk problem is RTP stream not oging trouhg from * to sip and vice versa. #1 and asterusk is pushing 192.168.1.30 back to linksys with 172 as return address.... or #2 asterisk trying to get back to me as 192.168 on public internet.. got