Hot answers tagged networking
tcp/53 DNS tcp/88 Kerberos tcp/135 RPC tcp/445 sysvol share tcp/389 LDAP tcp/464 Kerberos password (Max/Unix clients) tcp/636 LDAP SSL (if the domain controllers have/need/use certificates) tcp/1688 KMS (if KMS is used. Not necessarily AD, but the SRV record is in AD and clients need to communicate with the KMS). tcp/3268 LDAP GC tcp/3269 ...
I've done L4 loadbalancing for clustered RabbitMQ with Stingray load balancers - it works well, and we have done RR without any particular issue. In the event that one Rabbit node goes down, TCP connections fail and the load balancer sends traffic to the other node. Now this is technically inefficient, as any record send to node A will be sent to node B ...
So after waiting two weeks for an answer and researching another few hours after opening up a bounty i found the solution. Set up a new IPv6 enabled network and assign a subnet available to me (a /80 of my /64) docker network create --ipv6 --subnet=w:x:y:z:aaaa::/80 myfancynetwork Now start a container and connect it to the new network. Find out it's IP ...
I am not sure why you have not tried using PowerCLI, that would be the easiest and fastest way to do that. You can change the network adapter from connected to disconnected, change the network label (vLAN), or remove it all together. From all the times I have used this I have not come across any adverse effects on the VM's.
The only way I see this being possible is to have multiple virtual firewalls i.e. Pfsense running in the middle. Each of the four Pfsense firewalls would have one ip from your router on what would normally be the WAN side, and can give off any number of "internal" its on its LAN side. This will allow your network to be something like follows: Router using ...
Both of your virtual hosts assign themselves an IP address automatically from the 169.254 address space, when they cannot connect to a DHCP server. Try to configure an address manually to both these VMs, for example in the 192.168.100.0/24 subnet.
The client will need to access Kerberos so that's TCP 88 Then there is the Global Catalogue service so that's TCP 3268 There is the KPassword service TCP 464 (this allows password changes) Then there is LDAP port TCP 389, clients still need to access this to help locate domain controllers. There are also UDP ports for Kerberos (88) and KPassword (464) I am ...
There's many... you didn't specify much so i'll give my recommendation. I love GNS3: https://www.gns3.com/ Works best in linux. Then you can see: http://www.unetlab.com/ http://virl.cisco.com/ I have not tested the ones below.
After getting an overwhelming number of responses on SF... not!?!, I did my own research the figured it out. This is how I did it. Configuration -SSH to Host A and update /etc/network/interfaces as below: auto lo iface lo inet loopback iface eth1 inet manual auto vmbr1 iface vmbr1 inet static address 10.0.2.99 netmask 255.255.255.0 ...
Only top voted, non community-wiki answers of a minimum length are eligible