How can I access a site configured in IIS 7 on the host machine from a guest OS in VMWare (Fedora 10). I have configured the VM to use "NAT"
Depends on your network configuration of vmware product you are using (player, server, workstation). If it is set for a bridged mode, then you can do it as any other machine - by host machine's IP. If it is a "host only" or NAT mode - check what is the gateway IP for the guest (/sbin/route), and try using it:
# /sbin/route
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.x.y.z 0.0.0.0 UG 0 0 0 eth0
In this case, 10.x.y.z is the ip of the host machine.
Pretty easy...
Step 1 Configure IIS on the host OS to include a binding, if you would like to use a "url". for example mySite.com
Step 2. In the Guest open up the hosts file c:\windows\system32\drivers\etc\hosts.
Add the entry
[hostip address] [host iis bining url]
Example
192.168.0.1 mySite.com
restart your browser in the guest, and you should be good to go.
Related
I am trying to deploy a hub & spoke topology on Azure. I have VNet: hub, spoke1 & spoke2, respectively with the 3 following address spaces: 10.0.0.0/16, 10.1.0.0/16 & 10.2.0.0/16. And each have only one subnet on the /24 address space.
I have peered each spoke to the hub and deployed a Linux machine in my hub subnet. Now, I want to use that Linux machine as a router to forward traffic coming from 10.1.0.0/16 and targetting 10.2.0.0/16 to the spoke2 VNet and vice-versa.
I have added a User Defined Route on each spoke to use the Linux router IP address (10.0.0.5) as the Next hop when targetting the other spoke.
I have enable ip_forwarding on my Linux machine: echo 1 > /proc/sys/net/ipv4/ip_forward and added 2 routes ip route add 10.1.0.0/24 via 10.0.0.1 dev eth0 and ip route add 10.2.0.0/24 via 10.0.0.1 dev eth0 since 10.0.0.1 is my gateway on my router and eth0 my NIC.
I have also enabled IP Forwarding on the NIC of my router in Azure.
But... this does not work. Packets are not forwarded to appropriate network and I don't understand why.
If any of you has a hint or even the solution to implement this I would appreciate.
Thanks.
Don't forget about the setup for NIC for specific machine:
BTW: Microsoft has an easy tutorial on this.
You shoud configure the linux machine as a router.
create a linux bridge, and attach the eth0.
set the bridge ip as 10.0.0.1/24, and setup a dhcp server on it.
on each spokes, set 10.0.0.1 as next hop for target network.
On the linux machine, add router entry to 10.1.0.0/24 and 10.2.0.0/24 through 10.0.0.1.
Okay.
I don't know exactly what went wrong during my first tries.
I simply dropped the Resource Group and restarted from scratch with Windows VM, following Microsoft tutorial.
Then, I replaced step by step the Windows VM by Linux VM... and everything is working.
On the NVA, you simply have to:
enable the IP Forwarding on the Network Interface of the VM in Azure,
enable the IP Forwarding in the VM:
sudo sed -i 's/#net.ipv4.ip_forward=/net.ipv4.ip_forward=/' /etc/sysctl.conf
sudo sed -i 's/net.ipv4.ip_forward=0/net.ipv4.ip_forward=1/' /etc/sysctl.conf
sudo sed -i 's/#net.ipv6.conf.all.forwarding=/net.ipv6.conf.all.forwarding=/' /etc/sysctl.conf
sudo sed -i 's/net.ipv6.conf.all.forwarding=0/net.ipv6.conf.all.forwarding=1/' /etc/sysctl.conf
sudo sysctl -p
Then define routes in Azure (Route table + Routes) in each spoke to forward traffic to the NVA IP.
Nothing more. Works out of the box.
I even created my NVA in a Virtual Machine Scale Set behind an Internal Load Balancer with HA-Ports, so my NVA is highly available.
i'm having some issue with m VirtualBox installation, 6.1.22.
I have a VM with SUSE (SL12P1) for 64bit as a guest operative system, I have already installed the extension package and I'm trying to reach the guest from the host-system (Windows10) using ssh.
I have set the network adapter as "Bridge", in this way the guest has a 192.168.120.x IP, which i verified with ifconfig while the host has an IP of 192.168.120.y.
I can ping the guest from the host, but I cannot ssh the guest from the host system.
Notice that:
The firewall has been disabled
I have enabled Hyper-V virtualization.
I have tried setting the network adapter as NAT, and use port forwarding, but the ssh does not work either
The firewall for SuSE was active by default, after disabling it everything worked.
Hi StackOverflow members,
I have an issue with ssh connection on my Debian 7 system to a remote OpenSSH server located on the same network. It looks like there is some network configuration problem but I cann't find where it lays. This two debian machines are connect with a switch that is NOT connected to a router. So the two machines have no internet connection.
A-Debian 7
IP: 192.168.1.2
MASK: 255.255.255.0
GW: 192.168.1.1
B-Debian 7
IP: 192.168.1.3
MASK: 255.255.255.0
GW: 192.168.1.1
With that configuration the ssh command prompts my for a password in less then a second. But the with the following network configuration I get the password prompt after a 10+ second delay:
A-Debian 7
IP: 10.10.1.83
MASK: 255.255.255.128
GW: 10.10.1.1
B-Debian 7
IP: 10.10.1.82
MASK: 255.255.255.128
GW: 10.10.1.1
The ssh connection from the server A -> B runs with both configs on custom 1111 port.
The B machine has also a Web server running on port 8080 that has no delays with both net configurations.
Thank you in advance for any clues or tips how to solve that problem.
SOLVED: Removing of the gateway parameter "GW: 10.10.1.1" in the network settings has solved the problem.
The usual culprits here are IPv6 and DNS lookups.
SSH might try to connect via IPv6, first, but the timeout is too low for that. You can see whether IPv6 is enabled with
cat /proc/sys/net/ipv6/conf/eth0/disable_ipv6
To disable:
echo 1 > /proc/sys/net/ipv6/conf/eth0/disable_ipv6
The second culprit is DNS; my guess is that DNS lookups don't work correctly with the second configuration. Try host www.google.com to test this theory.
If that also has a delay, you need to fix your DNS setup.
If that's not it, check the rest of your networking parameters: Gateway, cables, etc.
Start to ping the other host. Is that fast & reliable?
Next, try remote login (ssh, telnet). Note that you can give telnet a port to connect to, so if you have DB server running, you can still use telnet to connect to the server. It will print an error but it allows you to test the TCP/IP connection without any extra error sources.
I have a virtual network which is vmnet2 using the 10.0.2.0/24 network, I want my Linux server to be able to ping the default gateway.
I have set the Linux eth1 values to be
IPADDR="10.0.2.50"
NETMASK="255.255.255.0"
BOOTPROTO="none"
ONBOOT="yes"
In the etc/sysconfig/network
GATEWAY="10.0.2.1"
However, when I attempt to ping 10.0.2.1 the destination host is unreachable. I've restarted the network with service network restart but to no avail.
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.2.0 255.255.255.0 U 1 0 0 eth1
default 10.0.2.1 0.0.0.0 UG 0 0 eth1
The first row is the ipaddress and the second is the default gateway
Please make sure below,
Bridge the connection from your desktop .
You should be able to ping your Virtual machine IP from the parent machine where you have hosted the same.
Make sure you should not have any iptables rules configured that are constraing your connectivity.
This seems to enough , i have made similar setup recently.
Thanks,
Jain
You should add DEFROUTE=no in your eth1 configuration.
I Have Window 7 as Host Machine and I have installed Redhat 5.3 and Centos 5.4 as Vmware Machines under Window 7 through Vmware Workestation.I configure DNS & DHCP in Redhat 5.3(10.0.0.1) and able to do nslookup & DIG in this.I am able to ping window 7,redhat,centos with each other.
I have made one entry client30.example.com for ip 10.0.0.30 in forword and backword lookup file in DNS server(10.0.0.1).
Problem :-
Centos whom i have made dhcp client of Redhat(10.0.0.1) is able to get ip from dhcp server and it gets ip 10.0.0.30 (as i wanted no problem till now)
But Centos is not picking up hostanme client30.example.com as i have bind entry of ip 10.0.0.30 with client30.example.com.
Still it is picking up hostname localhost.localdomain. I check /etc/resolve.conf file of centos and i found that by default it picks nameserver 192.168.1.1(even i have not provided this ip anywhere).Everytime i made manual change in this ip again it pics same ip on reboot.
Kindly help how i can resolve this problem.
Because VMware Workstation is itself DHCP. Please disable DHCP in VMware Workstation, You can't run two DHCP in single network subnet.
Also check /etc/sysconfig/network file, Hostname coming from there.