Windows Server with 2 NIC's (two subnets) only one subnet controlled by Windows Server - windows-server-2012

I have to build up a second network with Windows Server 2012 as DHCP and AD.
The PC for the Windows Server 2012 has two NIC's:
The first one 192.168.10.* (NIC1) should get the IP-Addresses from our Windows-Server and lives in it's own subnet. Except for the Internet-com, that should be handled over the NIC2.
The second one 192.168.20.* (NIC2) gets its IP-addresses from a Linux DHCP but has the connection to the internet.
Is that possible and would there be an easy solution?

You just have to make sure that NIC1 doesn't get a default gateway by DHCP.
On the DHCP server, use a reservation and in its options set option 003 Router to nothing. The PC will then use only the default gateway from NIC2.

Related

linking virtual machine as server and client

I have multiple virtual machine(vmware)(linux) but would like to make one as the server, meaning all the client who wants to access the internet, uses the server internet so, the server is able to view all the incoming and outgoing data packets.
Also, I would like to install another virtual machine to act as an IDS to track the server packet, if anything is wrong it is able to flag out.
Thanks for your help in advance
You can setup one Linux server as the gateway for the others. All you need is to create two virtual ethernet interfaces for it, one in bridged mode and other in virtual network mode.
One will be bridged with your actual network and act as the WAN, and the other will be act as a LAN gateway for others VM's.
So other VM's should use your server virtual network IP address as main gateway, and you can use tcpdump or wireshard or everything you like to sniff traffic forwarded.
One thing you need to configure on the server is IP forwarding option in sysctl, which is disabled by default:
net.ipv4.ip_forward = 1
You may find more relevant information here too.
Hope it will help you.

Bridge Wifi to Raspberry Pi using Ethernet Cable

I am not finding this question in SF history, which was a surprise, so I'll go ahead and ask it.
I am working on an IoT Raspberry Pi project with Windows 10 and need to connect it to the internet via an Ethernet/USB adapter. The adapter itself is made by Belkin. Using this, I can see an ip of 169.stuff get generated for my Pi, which is a private ip. I can deploy code to that from my connected box, however other devices are not able to reach it, and it is not able to make connections out to any servers.
I'm wondering if anybody knows how to bridge the connection.
I am attempting to use the new Azure IoT Hub and the SDK with this in case that makes any differences as that is not a simple rest interface and I believe is some form of socket connection.
Additional Notes:
I have installed a DCHP Server and the Pi gets the ip address: 192.168.0.3 assigned to it. Unfortunately the Pi still can not ping external sites, such as google.com
Latest Discoveries:
I am on a corporate box, which has internet sharing disabled by the system admin. Following these instructions: http://zizhujy.com/blog/post/2013/07/07/Solved-Internet-Connection-Sharing-has-been-disabled-by-the-Network-Administrator.aspx Fails. It shuts down all connectivity to my box and I cannot ping anything or reach the internet or anything.
Thanks,
~David
The 169 address means it isn’t getting a DHCP address assigned.
Since you don't have a router for the Ethernet, you can use Internet Connection Sharing, however we will need to run the following commands against the Pi to set a static IP, gateway, and dns server, since internet connection sharing botches this up a bit at times:
Set-Item WSMan:\localhost\Client\TrustedHosts -Value 192.168.137.2
Enter-PSSession -ComputerName 192.168.137.2 -Credential 192.168.137.2\Administrator
set-executionpolicy unrestricted
netsh int ip set address "Ethernet" static 192.168.137.2 255.255.255.0 192.168.137.1
netsh int ip set dns "Ethernet" static 8.8.8.8
netsh interface ipv4 show config
set-executionpolicy remotesigned
You may need to reboot the Pi at this point then test pinging 8.8.8.8 and google.com to make sure resolution is working. You should be all set!
One other thing, if you have a group policy on the machine that is restricting Internet Connection Sharing then take a look at this article to fix the issue. Note if your organization is constantly sending down the policy then you may have to re-enable Internet Connection Sharing often which is aggravating but at least it will work.
http://zizhujy.com/blog/post/2013/07/07/Solved-Internet-Connection-Sharing-has-been-disabled-by-the-Network-Administrator.aspx
I do this by creating a DHCP server on my laptop and connecting the Pi directly to it. I followed these instructions to get it working:
Download DHCP Server for Windows. It is a 100kB download.
Go to the IPv4 properties page of the Ethernet adapter and set a fixed IP address, say 192.168.2.1
Run the DHCP Server Wizard (downloaded above)
Select the Ethernet adapter from the list shown
Save the configuration file and start up the DHCP Server
Click the 'Continue as tray app' button in the server control panel.
Boot up the Raspberry Pi
A popup notification shows the IP address assigned by the DHCP server to the Raspberry Pi.
Use a SSH client, like PuTTy, to connect to the IP address shown
Hope this works!

IIS server unavailable on a local wifi

I want to create an IIS server on my PC. I've created a wifi hotspot through netsh wlan set hostednetwork ... , and a new wifi hotspot appeared (wifi2, in which my pc was 192.168.137.1).
So I shared the connection of wifi1 (the real NIC, with ip 192.168.0.104) and I enabled sharing of HTTP service (because of the IIS server). Obviously IIS is running. wifi2 is set as a domestic net.
So, I've connected my smartphone to wifi2, and typed 192.168.137.1, the IP of my pc in wifi2, in wich it should be running the IIS server. But it respond with a timeout error. So I've typed 192.168.0.104 , the IP of wifi1, and I though my smartphone cannot reach it, because my phone is connected to wifi2, but it show the IIS home page. This is strange, but the problem is here: if I disconnect my PC from wifi1 (so there isn't an internet connection, but only a local wifi lan), from my smartphone I can't visualize anything, both 192.168.137.1 and 192.168.0.104 !
why I need an internet connection to show the IIS page?
How can I fix this problem?

I can't access my Hyper-V Linux Web Server over the Internet

I'm trying to access a VM Linux Web Server from Internet but as response I get the server's internal IP.
Infra:
Physical PC: Windows 8 running on IP x.x.x.10 (internal) and y.y.y.y (external/internet)
Virtual Server: Debian 7.3 + Apache2, running on a Hyper-V machine, IP x.x.x.11
Router: D-Link DMG-6661 with 'Applications' and 'Virtual Server' set on both :80 and :7080, pointing to x.x.x.11
Inside my network everything works fine, I'm able to access my web page using both x.x.x.11:80 and x.x.x.11:7080.
Outside my network, lets say at work, if I try to access y.y.y.y:80 or :7080 I get ERR_NETWORK_ACCESS_DENIED and the address on my browser changes to x.x.x.11!
What am I missing here?
Thanks.
So difficult to answer you without precisions... Please check all network segments and software/hardware components ( linking your web browser at work to your Apache server). Lot's of thing may drop your connection. Think about these questions:
Does your router allow incoming connections from the Internet ? Is it configured to NAT/PAT incoming traffic to your Web server at x.x.x.11:80 ?
Does your Linux VM allow connections from other network than your LAN (netfilter/iptables configuration ?).
Does your Apache is configured to accept incoming traffic from any IP addresses ?
Regards

Multiple VPN connections behind NAT

I have the following problem:
I have Windows 2003 RAS VPN server configured with a single Nic (let's call it LAN1) behind a firewall (lets call it's public address WAN1). PPTP & L2TP ports are forwarded to the Server.
When a client (Windows or LINUX) in a remote network behind a firewall (LAN2) tries to connect to a PPTP VPN on the WAN1 everything goes fine.
When a second client in the same LAN2 tries to connect to the same VPN on the same WAN1 I get an error 629.
It's independant of which machine gets the first connection.
Apparently the problem is also independant of the router/firewall hardware of LAN2 (We have tested it from at least five different types of remote small router/firewalls - linksys, huawey, d-link, etc.)
The firewall WAN1 listens to two internet connections. The problem is independant of which external address the clients are pointing to (even if two different workstations point to different IP addresses to attempt to stablish a vpn).
Inside LAN1, there is no such limitation and multiple workstations connect just fine.
Theres also no limitation from different remote LANs.
Is this a limitation of PPTP protocol?
Thanx in advance.
From your description it sounds like the issue is at the remote end. You mention that when a second user from LAN2 attempts to reach the same VPN server at WAN1 you receive an error.
Depending on the firewall mechanism in use there can be a "limitation" that exists with regard to PPTP connection tracking and multiple VPN connections to the same server address.
Google: pptp multiple connections to same ip
Due to the way in which NAT tracks PPTP connections, specific modules need to be loaded in order to handle multiple connections to a single server.
If it's netfilter based, make sure 'nf_conntrack_pptp' and 'nf_nat_pptp' are loaded.

Resources