[LIL L]

this is kinda confusing so i'll try to explain it as much as possible.

i have a 8MB connection down 512KB up (bytes not bits) broadband and a netgear router. i have like 6 people in my house connected to my router and everythings all good nothing wrong there. i'm running windows 7 rtm build 7264. i got two nics and i was wondering if i can plug them both in and use some programs on one nic and other programs for the other? it didn't work when i had xp or when i had vista and i couldn't find information on exactly why it won't work (yes i searched all over the internet) but win 7 seems to have some new features i'm still discovering. would that be possible? it says its going through a switch but its not? (my connection is Mad-Labs)




if i go to my router configuration page and port forward my programs to one or the other nic, would windows 7 try to connect on my lan 1 and then switch automatically to my lan 2? would i be able to use both connections at the same time. maybe ftp on one and browsing on the other?

oh yeah, just in case you ask John Will lol:

Microsoft Windows [Version 6.1.7264]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\The Mas Scientist>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Mad-Labs
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : ADMtek AN983 based ethernet adapter
   Physical Address. . . . . . . . . : 00-1A-70-10-85-68
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::ecb1:b9bb:211f:feb5%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, August 23, 2009 5:47:42 PM
   Lease Expires . . . . . . . . . . : Monday, August 24, 2009 5:47:42 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 318773872
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-12-9B-C4-00-40-2B-4F-62-59

   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet
 NIC
   Physical Address. . . . . . . . . : 00-40-2B-4F-62-59
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a4b5:fed0:38bc:e3d9%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.15(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 234897451
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-12-9B-C4-00-40-2B-4F-62-59

   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{8D084CFB-13B9-4830-8DF8-EBA902534566}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{C2ECF646-6D07-412F-8877-B5683762D67A}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

 

[McNinja]

The reason to have two ethernet connections so you can have have ICS (internet connection sharing) or teamed ethernet with one port for download and one for uploading. This is meant for servers mostly

 

[LIL L]

thanks for the reply. so whats with the switch? i don't have one. i have eset smart security 4 and when i look at my network connections it says that some of my programs are using one and some are using the other. i guess its no harm right?

 

[McNinja]

I've got the same switch on my network map and its probably just the router.

 

[LIL L]

i've been working with this for some time now and i managed to find an article that has helped me greatly.

Windows Firewall was introduced with XP, but only the version for Windows Vista was powerful enough to replace third party desktop firewalls. Actually, Vista’s firewall is better than many of the personal firewalls I have ever seen. Compared to these enhancements, Windows 7 only has a tiny improvement to offer. However, in some environments, it might turn out to be very useful.

You probably know that Windows distinguishes between Public, Home, and Work networks. Whenever you connect to a new network, Windows will ask what type of network it is. Each network has its own firewall profile, which allows you to configure different firewall rules depending on the security requirements of the user’s locations. You can use the Windows Firewall with Advanced Security’s snap-in filter to display only rules for specific locations. The corresponding firewall rule sets are Public (Public), Private (Home / Work), and Domain (when a domain-joined workstation detects a domain controller) (see comment below).

This works fine as long as you are only connected to one network at a time. As a matter of fact, more and more users now have their own networks at home. The problem is that once they connect to the corpnet, the Domain firewall rule set becomes active, which will break homegroup connections. The solution to this problem seems to be to work with multiple NICs. However, in Windows Vista, only one profile can be active on the computer at a time. Windows Sever 2008 machines that are connected to multiple networks suffer the same problem. In this case, the profile with the most restrictive settings is applied to all adapters on the computer.

Windows-7-Firewall-Protected-Connections Windows 7’s multiple active firewall profiles are the solution to this problem. It is now possible to assign each firewall profile to specific NICs. You can configure this feature in the Windows Firewall properties (right click on the root folder Windows Firewall with Advanced Security snap-in). This allows you to work with a different firewall profile for each network interface. If the computer is connected to multiple networks at a time, Windows Firewall will use the different rule sets for each NIC.

Note that this feature can’t be configured via Group Policy. At least the Group Policy settings of Windows Server 2008 R2 Beta don’t offer a corresponding option. The problem is that you can’t know in advance, for all external computers, which NIC is connected to the home network and which to the domain network. I guess that’s why you will have to configure this manually for each computer.

i'm still trying to configure my windows and my eset firewall to work at same time. thanks for all of the help and i hope this help many other people with this problem.

 

[DT Roberts]

Thanks for posting back. I've never heard of this before. I'll have to take a look myself.