Error No Interface Attached To This Zone
Contents |
Now Hey Guys, I have commissioned a spare TZ 190 to set up a site to site VPN with a TZ 210 in another state. I have got set up a dedicated ADSL2 Point to Point connection between the two sites and am a little confused as to how to
Sonicwall Create Untrusted Zone
proceed. I have the modem connected into the OPT port at the back of the TZ 170 and
Sonicwall Disable Interface Trust
on the 210 I have it connected to the x2 port. Both port's zones are unassigned, however I can see on the status screen both are registering in sonicos a default zone that comes with a brand new appliance is some traffic between them. I ran the VPN wizard on the TZ 170 setting up the local network with the current networks range: I set these up as Type: Network, Zone Assignment: Lan with the following settings: Network/Netmask: 192.168.1.0/255.255.255.0 And as the destination I https://support.software.dell.com/kb/sw3769 have set it to the other networks IP range: Network/Netmask: 10.75.20.0/255.255.255.0 On the TZ 210 I set it up but in reverse so the local and destination network are correct for the other site. For the IPSec Primary Gateway I have the WAN IP address of the respective sites. I'm just wondering, what do I do now that I have set this up, is there somewhere I initiate the connection on the sonic wall or is it just automatic when I have the correct details in? I'm thinking having https://community.spiceworks.com/topic/148260-sonicwall-site-to-site-vpn-confusion the OPT port and the X2 port's zone un-assigned that is having an affect on it, but not too sure what I should set them too. Would appreciate some help guys, I'm a little lost as to how to proceed. Because the connection is dedicated for communication between servers...am I even able to just correctly create a zone on those ports and have them talk? Thanks for your time. Reply Subscribe View Best Answer RELATED TOPICS: Ubiquiti Edgerouter Lite VPN Windows 7 client Old School VPN. ASA 5505 VPN Issue   11 Replies Mace OP Jay6111 Jul 20, 2011 at 7:24 UTC Gavan, Are you asking because the tunnel is not up and you can't communicate between sites, or just wondering if it should work the way you set it up? -Jay 0 Tabasco OP George G. Ioannides Jul 20, 2011 at 8:48 UTC Fidelity Systems is an IT service provider. Greetings, If I understand correctly, you are setting up a dedicated P2P between sites uisng your firewalls with an ADSL2 circuit, correct? Using this circuit, you are trying to establish a VPN tunnel? Once everything is configured, the connection will automatically initiate connection; once enabled. HIH 0 Tabasco OP Scott Lundberg Jul 20, 2011 at 8:54 UTC If you have a dedicated point to point (P2P) link, why create VPN tunnel at all? The VPN tunnel would be used if you are trying to create a P2P link across the Internet. If I am misunderstanding you, and you are trying to create tunnel using your e
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://serverfault.com/questions/446869/cant-attach-ec2-instance-to-network-interface and policies of this site About Us Learn more about Stack Overflow http://serverfault.com/questions/768774/i-can-not-attach-additional-network-interface-to-an-existing-amazon-ec2-instance the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: error no Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Can't attach EC2 instance to Network Interface up vote 0 down vote favorite When trying to attach a network interface, it says... No instances were found for this availability zone. My instance is in us-east-1c and my network interface is in us-east-1b. error no interface Is that significant? If so, how do I create the VPC in the same zone and if not then why this error? EDIT: I've re-created the VPC and the Network Interface is now us-east-1c and the EC2 instance is also us-east-1c. Same error message though! amazon-ec2 amazon-vpc share|improve this question edited Nov 8 '12 at 20:51 asked Nov 8 '12 at 19:37 Ian Warburton 176211 are the interface and the instance in the same VPC? They must be. –smcg Nov 8 '12 at 21:10 did you try putting everything in the same VPC yet? –smcg Nov 9 '12 at 20:22 Yes thanks I recreated the instance. :) –Ian Warburton Nov 10 '12 at 15:11 add a comment| 1 Answer 1 active oldest votes up vote 3 down vote accepted The subnet you are trying to connect to must be in the same availability zone as the instance. When you go to create a VPC, you usually create it with one subnet. Click "edit public subnet" and then select an availability zone. For example I see
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top I can not attach additional network interface to an existing amazon EC2 instance up vote 0 down vote favorite I need three network interfaces in one instance for my work.By default there is one eth0 but I want to add eth1 and eth2 in an instance. I created network interfaces using the same security rule that I used to create the EC2 instance in zone us-west-2a and my instance is also in this zone us-wes-2a My instance type is t2.micro now i choose the instance options and choosing the instance where i want to add ,then from actions ->networking->attach network interface gives this error No available network interfaces were found for this VPC or availability zone Could someone guide me to resolve this issue? thanks a lot. networking amazon-ec2 multiple-instances share|improve this question asked Apr 7 at 11:54 bhordupur 31 t2.micro only supports a total of 2 ENIs (eth0 and eth1), with a maximum of 2 IP addresses per ENI. Larger instances are required, if you need more than this. When you created new the ENI, you needed to create it on a subnet that is in the same VPC and same availability zone as the primary interface in the instance. Verify that? –Michael - sqlbot Apr 8 at 3:24