Connecting two networks.

I am trying to connect two similar networks. I am not sure if this is possible or not.
My network has cable internet access through a Airport Extreme wireless router to a hub that connects to all of my devices (iMac, Xbox 360, TiVo, Win XP computer). The other network also connects to the internet through a cable modem and has a linksys wireless router. My iMac connects to my network through ethernet and the second network wirelessly.
I can connect to either network separately. I would like to be able to transfer files and print to the other network while simultaneously logged on my network and accessing the internet through my modem.
Is this possible? If so what do I need to do?
Thanks,
Scott
iMac 24" 2.16 GHz Intel Core 2 Duo, 2 GB DDR2 SDRAM and 17" G4 Powerbook   Mac OS X (10.4.7)  

It is possible, but what would really be the point? For the possibility, you could simply have one network connected via ethernet cord, and the other network be strictly wireless. The only reason to even have two networks would be bandwidth issues, which you would want to have your non-computer (but internet reliant) on one network, and then have your computers connect through the other network. Transferring files between two networks at the same time wouldn't be the most efficiant method, simply having both computers connected via ethernet would be by far more effeciant.
Airport Extreme/Express is limited to 54 MBps realitivly. You would get much better speeds via ethernet. If your trying to get more data faster by transferring via ehternet and airport, then you may want to keep in mind that speeds are also limited to hard drive speeds.
In short, its pretty over-kill.

Similar Messages

  • Connecting two networks with wireless bridges

    Hello all,
    We are trying to create a true CAN. We have 2 sets of 2 buildings each. One set is on the 172.23.x.x network and the other set is on the 172.25.x.x network. Each set has routing in place to go out over their respective MPLS circuits (which will be removed once this project is done). Each set also has their own vtp domain each containing ~30 vlans.
    Right now, there is a wireless bridge at each set of buildings and they can reach each other fine according to the vendor. I am trying to figure out an efficient way to tie these two networks together keeping their current vlan and local topology in place.
    Site 1:
    Vlan 1: 172.23.1.x
    Wireless bridge: 172.25.1.x
    Site 2:
    Vlan 1: 172.25.1.x
    Wireless bridge: 172.25.1.x
    Any help is appreciated. The idea is that all traffic from site two will now traverse the wireless bridge and use all resources and routing available at site 1.

    OK wel now the only solution left for you re-designing the IP addressing or if you want same  ip address either increase the scope or range of ip address per vlan or use DHCP server to provid Half the address to both sides. but the interface connecting interface must be a Layer 3 or Layer 2 ports.The only concern should be DHCP server vlan over lapping can be manage by Configuing VTP (Client/Server) .
              (Switch) ====wireless------------------wireless====(switch)
             Trunk (Layer2 port)                                                 Trunk (Layer2 port)
    and for vlan just if one dhcp server  nothign to worry  and incase of multiple server just load balance it will also provide the reduncency in you network.
    other option is simple using L3 approach and change the ip address only for resourches you want other people to access.

  • Connecting two networks with two internet connections

    Hi All
    The situation is this. Two firms situated next door to each other and linked by their businesses and by their family ties, wish to connect their two networks together. They both have internet connections. The reason is for security, in the event of one internet going down they can use the other one.
    As I see it, we could use a wireless bridge/repeater to connect the two ethernets together, turn off DHCP in both networks, and manually configure the IP addresses on one network to say 192.168.1.1 to 192.168.1.100 and set the gateway as the router address in that network, again manually allocated. Then on the other network set the scope to 192.168.1.101 to 192.168.1.200 with the router on that network set in this range.
    In the event of failure of one internet connection, it would just require the gateway to be changed for those pcs to access the router on the other network.  I know of a little program which would do that automatically.
    Would this work? If so which Linksys equipment would I need to bridge the two networks. I know some equipment will do the bridging and allow wireless clients to connect, so that would be useful, I know it slows it down by half, but this might be acceptable.
    Will there be other problems rearing their ugly heads which I haven't considered.
    The networks are not large, so manual IP configuration is not a problem.
    Thanks

    I presume both networks are using wireless connections.  If you can see your neighbour's network on your computer and vice versa, all you need is the passphrase to connect.  You may have to disable filter mac address in your router. 
    Greetings from Northern Ontario, Canada

  • Connecting two networks at home

    I have my verizon dsl wireless router connected downstairs and it is hooked up to my wii so I may watch movies, etc. Upstairs at my office I have my computers and printers and none have wireless capability. So the problems is how do I connect my computers and printer at my office to the internet? I am assuming that I can not connect them to another dsl router and plug that into the telehone jack! That is, I can not have more than one dsl modem connected to the telephone line. The other option I am thinkig is if there was a wirelsss switch then I can connect my office equipment to the wirelss switch and then have that linked to my dsl router via the wirelss network. The problem is that I am unable to find a wireless switch. Can I make a wirelss router into a wirelss switch? How? Don't all routers assume that the uplink is hardwired and not wireless??
    Please help!
    Ashok

    It's called a Wireless Ethernet bridge (also sometimes called a "gaming adapter" or "wireless ethernet converter").   Has one or more ethernet ports on it and acts as a wireless "client" connecting to an upstream wireless access point (i.e. your router).
    Your other option is "power line" networking.    You use them in a pair -- one end is usually a 4-port switch (where you plug in your client systems) and then other is a single port ethernet (which you plug into the router).

  • Connecting two networks to one sap server

    Hi There,
    Is it possible to connect to seperate networks to one SAP Server ?
    The server does have a spare network card
    Regards
    George

    Yes it should be easy if all devices have wifi. The iMac will have, hopefully the router has, but does the eMac? Do eMac's have wifi built in?
    If the router is wifi it'll have a wifi password, normally WPA, WPA/2 or WEP, either on the documentation or on a sticker on the bottom of the router. Turn wifi on on the Macs and they should see the network, type the password when prompted and they should connect.
    If the eMac doesn't have wifi you could connect to the router via an ethernet cable and it should be seen on the network.

  • Can wicd simultaneously connect two networks via different interfaces

    hi, recently, I installed wicd. I am tired for figuring out of NetworkManager stuff.
    however, for same reasons, I could not configure my ethernet and wireless interface at the same time.
    for example, in my case, I have enp0s25 and wlp3s0 interfaces. however, wicd only allow me to connect one at a time. especially when I connected enp0s25 via wicd-curses, it actually disabled the wlp3s0. (the interface is set down by wicd, but I still can see the available network, very strange)
    is there a way to deal with that ?

    Wicd is kinda strange, it usually picks the wired over the wireless (and there is an option for that).  You can get it, by allowing wicd to connect wirelessly, and manually dhclient the eth0 interface.  Netctl can help in this allowing both interfaces to go without manual intervention.  The only difference is you won't be roaming like you can in wicd.

  • Can I connect two apple tv on same network and same apple ID at a time ?

    Can I connect two apple tv on same network and same apple ID at a time ?

    Welcome to the  Discussion Forums.
    Yes you can do all that without needing to keep plugging things in and out. You will still need to manually turn on the receiver and turn down the volume from the tv though.

  • Is there a way to connect to two networks simultaneously?

    Here is my scenario:
    I am an audio technician who travels from venue to venue for work have to constantly switch between two networks to do my job.  I use MAC OS w/ the most current version 10.9
    Example:
    99% of the time, there is venue provided wireless internet via DHCP, w/ no wired option available.  I log onto it for all my internet related productivity.  At the same time, I need to stay connected to a manual/static ip local network to remote & monitor audio hardware (wireless mic's, dsp drives, mixing consoles, etc).  I have the ability to use either a wired or wireless connection for the local manual network (new airport express, or wired line). 
    I go to my network preferences in my system prefs and can see a green confirmation indicator that both networks are indeed connected.  However, depending on which network i give priority to by "setting service order", the other network drops.  For example, today Im using a wired line to remote/monitor my audio systems on my manual/static ip network and can stay connected as long as i set my ethernet connection at the top of the 'service order' list.  As soon as I go to launch my Safari browser it says I am no longer connected to the internet, eventhough my network system preferences show I am still connected.  The only way I can get the internet to connect is to reset the 'service order' and put wi-fi back on top.  As soon as I do this though, my manual wired audio network loses it's connection.
    I should note some settings.  Today's networks:
    wireless (internet):
    ip: 10.100.1.159
    sm: 255.255.0.0
    router: 10.100.255.254
    wired (audio network):
    ip: 192.168.0.128
    sm: 255.255.255.0
    router: 192.168.0.1
    Is there a way to stay connected to both, regardless of the 'service order'?  I have a brand new airport express if putting something like that in-line helps in anyway.
    Best,
    Brian

    Is there a way to stay connected to both, regardless of the 'service order'?
    There can only be one active connection at any given time, no matter how many networks you may be connected to.

  • Connecting to two networks at the same time

    Hi Kadin,
    I am looking for the same answer for a long time. I have two situations that requires to connect to two different metworks and that is when I travel with my portable Linksys router WRT54GC .
    1. I stay at a hotel with a wireless Internet network connection and I try to use the network to access the Internet and then (2) I also need to access my external Maxtor harddrive to which I am connected through my portable router WRT54GC .
    2. I have an almost identical situation but instead of the hotel network now I have a brand new T-Mobil cell phone made by ITC, which is called Wings and it uses a new way to connect my laptop to the Internet by using a Windows Mobile 6 Internet-share connection, which basically connects my laptop to the T-Mobile network and assigns it a IP address.
    The problem that I have is that in both cases I can connect to each one of the networks separately but not simultaneously.
    Any advise as to how this can be done. I also tried the Wireless WET54G as a bridge with similar negative results.
    Thanks,
    Pole

    Ok not real clear on your setup, but here is the "networking answer" why you can not connect to two networks.
    A device must have an IP address on the same subnet of the device you want to establish a connection or an IP route must be known to the network routers, since your internal address are most likely in the reserved private range, no internet router is not going to know how to deliver the packets to the correct hosts.
    the simple answer is assign a secondary IP address to the network adapter on your laptop.
    In the windows IP address properties for secondary address you can not set a default gateway. Windows only has 1 default gateway.
    good luck
    jwm

  • Connect to two networks, ethernet(LAN w/o internet), wireless(w/ internet)

    so i'm trying to connect to two networks, a wireless and a wired one
    the wireless(which connect to an access point) is a network which allows me to connect to internet, and the wired(regular router) one is a small home local network, which does not connect to internet.
    if i just have the wireless one on, unplug/disable wired one, i can connect to internet just fine, but if i do plug in ethernet cable, then all of the sudden i can't connect to internet anymore.
    in my Network Coonections window, it does show that the wireless one has "Access to Network and Internet" while the wired one has "Access to Network only". I'd assume that the computer is smart enough to find its way to internet, but apparently not.
    is there a way to set a preference, so vista tries to find internet conncetion thru wireless first, before go on to the wired network?
    I konw this is technically possible, because on my mac, i can set in such way that it takes certain connection first
    thanks in advance

    I think I am getting it but still no joy.
    On the WiFi connection to FIOS Router I have manually set metric to 1.
    On Same PC in Ethernet I have removed gateway and set a metric to 10.
    Before I did this connection to Internet was very slow when the Ethernet cable plugged in and Interface Enabled. After removing gateway and setting metrics access to Internet AOK.
    I have working Homegroup, network printer but no Internet access from Hardwired PC.
    Cannot ping FIOS router @ 192.168.1.1 from hardwired PC. Destination host unreachable.
    NMAP Quick Scan 192.168.1.* never sees 192.168.1.1
    So, I'm still not routing properly.
    ken wood it director tlw sports company, llc the states
    ===========================================================
    ==========================================================
    Anyone can help me? 
    I somehow tried to delect the waste items in my computer.  However, I accidently delected Wireless internet LAN.  After that, my wireless won't work anymore.  How can I search and do the download so my wireless is back to work?  What
    is the whole name?
    Thanks,
    Yangpal

  • Connect to two networks?

    I'm using my next door neighbors wi-fi (splitting the bill with him). I'm trying to use my AE in (Bridge? mode) connected to my Lacie external harddrive. I set up the AE "internet" for "Off (bridge mode)" and my external harddrive shows up under "disks".
    My problem right now is that I don't know how to connect to both the neighbors Wi-fi internet network and my AE to wirelessly access my external harddrive? Is it possible to connect to two networks? Or is there a better way of doing this?
    Any help is greatly appreciated.
    Thanks

    Hello ianbroste. Welcome to the Apple Discussions!
    In order to "combine" networks, your 802.11n AirPort Extreme Base Station (AEBSn) would have to be configured to extend the wireless range of your neighbor's router. This would (potentially) only work if his router is also another 802.11n AirPort.

  • Networking Best Practices - Connecting Two Switches

    Connecting two switches together is an easy task, which makes it so frustrating when it doesn’t work. Here we will outline a basic scenario of connecting two switches and achieving connectivity. In these scenarios we will be using commands and settings that will work for most modern PowerConnect switches. However this does not cover all possible scenarios and the commands may differ slightly from switch to switch.
    For instance, in most cases you can use General or Trunk mode when connecting two switches. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID.  If you use Trunk mode, you will not have the default VLAN on those ports.  The ports will only allow tagged traffic.
    For more details on the difference between Access, General, and Trunk modes, follow this link.
    http://en.community.dell.com/support-forums/network-switches/f/866/p/19445142/20089157.aspx#20089157
    It is always a good idea to have the user and CLI guide for your switch, to reference any possible changes in command syntax.
    http://support.dell.com/support/edocs/network/
    Layer 2
    Layer 2 switches operate at the data link layer of the OSI model. Layer 2 is responsible for error checking and transmitting data across the physical media. MAC addressing sources and destination protocols are layer 2 protocols. Layer 2 switches use the MAC address of data packets to determine where those packets should go. It learns the MAC addresses of all devices and creates a segment/forwarding table.
    When a switch receives a frame with a destination address that isn't in its forwarding table, the switch forwards the frame to all other ports. If the destination machine responds to the server, the switch will listen to the reply and learn which port the destination machine is attached to. It then adds that MAC address to the forwarding table.
    The Dell PowerConnect Layer 2 switches have ports that all operate in VLAN 1 by default. If it is acceptable to have all traffic on the same broadcast domain, then you can simply leave the default alone, connect the two switches and traffic will flow.
     If you do not want all traffic on the same broadcast domain, then we need to look at adding additional broadcast domains through the use of VLANs.
     We will use 3 VLANs for the following scenario.
    VLAN 1=Management
    VLAN 2=Client
    VLAN 3=Server
    To create these VLANs we do the following commands (VLAN 1 is already created by default)
    console(config)# vlan database
    console(config-vlan)# VLAN 2
    console(config-vlan)# VLAN 3
    console(config-vlan)# exit
    We can then name the VLANs to help keep things organized.
    console(config)# interface vlan 2
    console(config-vlan)# name Client
    console(config-vlan)# exit
    console(config)# interface vlan 3
    console(config-vlan)# name Server
    console(config-vlan)# exit
    Once we have the VLANs created we can place a device in that VLAN by placing the port it plugs into, in access mode for the specific VLAN.
    So we have a workstation on port e2 we want to be placed in VLAN 2, we would issue the following commands.
    console(config)# interface ethernet 1/e2
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 2
    console(config-if)# exit
    The next port plugs into a server on port e3 we want on VLAN 3, we would issue these commands.
    console(config)# interface ethernet 1/e3
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 3
    console(config-if)# exit
    For the ports connecting the two switches together, we place the ports in trunk mode and specify the native VLAN and allowed VLANs.
    For the port e1 that connect the two switches to each other would be configured like this.
    console(config)# interface ethernet 1/e1
    console(config-if)# switchport mode general
    console(config-if)# switchport general allowed vlan add 2,3 tagged
    console(config-if)# switchport general pvid 1
    console(config-if)# exit
    Once these VLANs and port settings are made on both switches. A server connected to switch A on VLAN 3 should be able to communicate with another Server connected to switch B that is also in VLAN 3.  Without the use of a router the devices in VLAN 3 will not be able to communicate with devices that are outside of their broadcast domain (i.e. VLAN 2 devices could not reach VLAN 3 devices)
    Layer 3 + Layer 2
     Until recently, routers were the only devices capable of layer 3 protocols. Switches capable of routing are now available and in widespread use. In most cases we will connect our layer 2 switches to a Layer 3 capable switch to perform our routing for us.
     On the layer 3 switches we will use the same VLANs and setup that we did with the layer 2 switches.  Then we will add to the configuration.
     We can assign an IP address to each switch with the following command.
    Switch A
    console(config)#ip address 172.16.1.1 255.255.255.0
    Switch B
    console(config)#ip address 172.16.2.1 255.255.255.0
    Then we will enable routing only on Switch A
    console(config)# ip routing
    Switch A we assign an IP address to VLAN 2 and enabling routing on the VLAN.
    console(config)# interface vlan 2
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.20.1 255.255.255.0
    console(config-if-vlan2)# exit
    Switch A we assign an IP address to VLAN 3 and enabling routing on the VLAN.
    console(config)# interface vlan 3
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.30.1 255.255.255.0
    console(config-if-vlan2)# exit
    On both switch A and switch B we will keep things simple and use interface 1/e1 for the connection between each switch. Setting both switches 1/e1 to general mode, allowing the additional VLAN 2,3, and keeping the PVID of 1.
    console(config)# interface ethernet 1/e1
    console(config-if)# switchport mode general
    console(config-if)# switchport general allowed vlan add 2,3 tagged
    console(config-if)# switchport general pvid 1
    console(config-if)# exit
    We will have one client computer connect to switch A on port 1/e2 and one client connect to switch B on port 1/e2. These ports will be in access mode for VLAN 2, and the config should look like this on both switches.
    console(config)# interface ethernet 1/e2
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 2
    console(config-if)# exit
    We will have another client computer connect to switch A on port 1/e3 and one client connect to switch B on port 1/e3. These ports will be in access mode for VLAN 3, and the config should look like this on both switches.
    console(config)# interface ethernet 1/e3
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 3
    console(config-if)# exit
    On Clients connected to Switch A we will assign an IP address and gateway based on the VLAN they are in access mode for.
    Client connected to access port for VLAN 2.
    IP Address:172.16.20.11
    Default Gateway:172.16.20.1
    Client connected to access port for VLAN 3.
    IP Address:172.16.30.11
    Default Gateway:172.16.30.1
    On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
    Client connected to access port for VLAN 2.
    IP Address:172.16.20.12
    Default Gateway:172.16.20.1
    Client connected to access port for VLAN 3.
    IP Address:172.16.30.12
    Default Gateway:172.16.30.1
    External Connection
    At some point we may want traffic to have an external connection. To do this we can create a new VLAN for our point to point connection from Switch A to our router. We will use VLAN 7 for this and assign an IP address.
    console(config)# vlan database
    console(config-vlan)# VLAN 7
    console(config-vlan)# exit
    console(config)# interface vlan 7
    console(config-vlan)# name WAN
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 10.10.10.2 255.255.255.0
    console(config-if-vlan2)# exit
    On our router we will assign an IP address of 10.10.10.1
    Then place the port connecting the switch and router into access mode for VLAN 7.  In this case we use port e4.
     console(config)# interface ethernet 1/e4
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 7
    console(config-if)# exit
    We will then need to put in a default route with the next hop as the router IP address.  This allows the switch to know where to route traffic not destined for VLANs 2, 3, or 7.
    console(config)#ip route 0.0.0.0 0.0.0.0 10.10.10.1
    Next on the router we’ll need to add a route back so the router knows about the networks attached to switch A.  Generally adding a static route on most routers is done with the following command: 
    ip route {Network} {Wildcard Mask} {Next Hop-IP}
    In our case here are the 2 static routes we could use.
    Ip route 172.16.20.0 0.0.0.255 10.10.10.2
    Ip route 172.16.30.0 0.0.0.255 10.10.10.2
    The routing that we enabled on Switch A will enable traffic from the other VLANs to traverse over port 1/e4 to the router, connecting us to external traffic. The routes we added to the router allow the traffic to flow back to the switch over port 1/e4.
    Layer 3 + Layer 3
    In some situations we have two switches, each setup to route for its own broadcast domain, which we want to connect together. In this situation we no longer have a need to use Trunk or General mode between the switches. Instead we can create a common VLAN that will be used for the connection between the two switches.
    To create this VLAN we will run the following commands on both switch A and B
    console(config)# vlan database
    console(config-vlan)# vlan 6
    console(config-vlan)# exit
    console(config)# interface vlan 6
    console(config-vlan)# name Connection
    console(config-vlan)# exit
    On switch A we assign an IP address to VLAN 6 and enable routing on the VLAN.
    console(config)# interface vlan 6
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.60.1 255.255.255.0
    console(config-if-vlan2)# exit
    On switch B we assign an IP address to VLAN 6 and enable routing on the VLAN.
    console(config)# interface vlan 6
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.60.2 255.255.255.0
    console(config-if-vlan2)# exit
    On both switch A and B we place the connecting ports into Access mode for VLAN 6.
    console(config)# interface ethernet 1/e1
    console(config-if)# switchport mode access
    console(config-if)# switchport access vlan 6
    console(config-if)# exit
    We then need to make some changes to switch B now that it is layer 3 and not layer 2 and has its own broadcast domain.
    We will enable routing on Switch B
    console(config)# ip routing
    What used to be VLAN 2 and 3 will now be VLAN 4 and 5 for our separate broadcast domains.
    Switch B we assign an IP address to VLAN 4 and enabling routing on the VLAN.
    console(config)# interface vlan 4
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.40.1 255.255.255.0
    console(config-if-vlan2)# exit
    Switch B we assign an IP address to VLAN 5 and enabling routing on the VLAN.
    console(config)# interface vlan 5
    console(config-if-vlan2)# Routing
    console(config-if-vlan2)# ip address 172.16.50.1 255.255.255.0
    console(config-if-vlan2)# exit
    On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
    Client connected to access port for VLAN 4.
    IP Address:172.16.40.11
    Default Gateway:172.16.40.1
    Client connected to access port for VLAN 5.
    IP Address:172.16.50.11
    Default Gateway:172.16.50.1
    The end result should look like this.
     Troubleshooting
    If we are having issues with connectivity, we may need to place some static routes in place to help traffic to the next hop in the network.
    On switch A we configure a static route to help traffic to the next hop in the network, which is the router.
    console(config)# ip route 0.0.0.0 0.0.0.0 10.10.10.1
    The external router will also need a path defined back to all networks/VLANs.
    To check the status of a port we can use the command. Show interfaces detail, this will help us see the port status. For example to check the status of port 48, we would run this command.
    console# show interfaces detail ethernet 1/g48
     To check routing paths:
    console# show ip route
    The IP address of the network for each VLAN should be listed as C – Connected. Then also a path or default route to your upstream router.
    We can use basic ping commands from a client to help test where connectivity is dropping off at. By doing this we can narrow down where in the network to start troubleshooting.
    -Ping from client to default gateway, being the VLAN the client is in access mode for. If this fails then we may need to double check our client settings making sure the proper IP and gateway are being used.
    -Ping from client to the ip address of the switch the client plugs into. If this fails we may not have VLAN routing enabled on the VLAN the client is in.
    -Ping from client to another client on same VLAN, same switch. If this fails we need to check on client settings, IP address and gateway.
    -ping from client to another client on different VLAN, same switch. If this fails we need to double check the VLAN routing commands are in place.
    -ping from client to the ip address of the next switch in the network. If this fails then check Trunk port configuration from switch to switch, ensuring the VLAN is added to the Trunk port.
    -ping from client to another client on same VLAN, different switch. If this fails, check Trunk port settings.
    -ping from client to another client on different VLAN, different switch. If this fails then check trunk settings and VLAN routing configuration.

    Derek,
    I tried to draw my prefered setup for this network configuration.
    I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
    I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
    and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
    Hope this helps.
    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
    www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

  • HT4262 I have two networks one each in two cities.  Both are named the same but require different passwords. I am at my second location but cannot connect to his wifi network. How do I delet one network so I can connect to my second network?

    I have two networks one each in two cities.  Both are named the same but require different passwords. I am at my second location and cannot connect to this wifi network. How do I delet one network so I can connect to my second network?

    Just go to the wireless network preferences and empty out all the stored wireless networks.. then scan and connect to the local wireless.
    Select them and tap the - button below it.
    Once they are emptied out.. it might be good to reboot the computer with the remember networks unchecked.
    Start with a clean slate.

  • Problem connecting two storage networks

    Hello,
    I connect two datacenters with 10GB modules. I'm using single mode fiber, it has 10Km between datacenters. Now I need connect the storage network in both datacenters using the same fiber. The storage networks use FCoE.
    What solution can I use to connect the two storage networks. My budget is really limited.  
    Storage Network 1---------Network 1-------Fiber---------Network 2------Storage Network 2
    Thanks for the help.

    Brigid,
    There seems to be two aspects:
    One is to get the end points to coincide. You may tick View>Snap Guides, then click one path by the end Anchor Point and drag it to snap (Smart Guides say anchor when you are there).
    The other is to get rid of the gap in the stroke(s), You may join the paths into one, dragging across the coinciding Anchor Points with the Direct Selection Tool and Ctrl/Cmd+J, or you may keep the separate paths and change the Cap to Round in the Stroke palette/panel which will give you a rounded outer appearance); I presume the former is what you wish, in which case you may choose between Round and Miter Join.

  • Two network connections

    Is it possible to be connected to two network connections at the same time?

    Thank you Tom for that Green Star. You pushed me to the 100,000 points level. A major achievement for me that would not be possible without people like you. So I salute you for your kindness. I'll try not to forget your name - Tom O'Malley.

Maybe you are looking for