- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Not certain of your question, but first, set up a single PC to connect to the SG565 unit. Information is entered from that PC.
The initial steps are:
1 Connect your administrative PC to the SG unit: - If you are setting up the SG560, SG565 or SG580, attach your PC's network interface card directly any network port on switch A (A1 - A4) using the supplied network cable.
2 Modify your PC's network settings to enable communication with the SG unit. Click Start > (Settings >) Control Panel and double-click Network Connections. Right-click Local Area Connection and click Properties. Note: If there is more than one existing network connection, select the one corresponding to the NIC to which the SG unit is attached.
3 Select Internet Protocol (TCP/IP) and click Properties. The Internet Protocol (TCP/IP) Properties dialog box is displayed.
4 Select Use the following IP address and enter: - IP address: 192.168.0.100 - Subnet mask: 255.255.255.0 - Default gateway: 192.168.0.1
5 Select Use the following DNS server addresses and enter Preferred DNS server: 192.168.0.1
Its like router on stick configuration??enter the interface which you have to configure and in that interface as mentioned below Hostname(config)#interface FastEthernet0/1 Hostname(config-if)#noip address Hostname(config-if)#no shutdown Hostname(config)#interface FastEthernet0/1.1 Hostname(config-if)#encapsulation dot1Q 1 native Hostname(config-if)#ip address x.x.y.y < subnet mask > interface FastEthernet0/1.2 Hostname(config-if)#encapsulation dot1Q 2 Hostname(config-if)#ip address x.x.y.y < subnet mask >
wow I'm sure you've figured this out by now seeing as this was posted on 8/12/2008. however for the record what you're seeing is phase2 information and that's the proxy id that your far end is showing 0/0.Did you make sure your ipsec sa's matched?
!--- Naming the PIX is optional.
PIX(config)#nameif ethernet2 fo security20
!--- Naming the interface is optional. It is recommended that you
!--- hardcode the speed/duplex.
PIX(config)#interface ethernet2 100full
!--- Bring up the interface.
PIX(config)#ip address fo 192.168.1.1 255.255.255.0
!--- Assign an IP address.
PIX(config)#failover ip address fo 192.168.1.2
!--- IP address for the failover link.
PIX(config)#failover lan unit primary
!--- This unit is primary
PIX(config)#failover lan interface fo
!--- The 'fo' interface is used for LAN failover.
PIX(config)#failover lan key cisco
!--- The Pre-shared key.
PIX(config)#failover lan enable
!--- Enables failover.
!--- Start the failover process.
This message appears on the console:
LAN-based Failover: trying to contact peer
LAN-based Failover: Send hello msg and start failover monitoring
If you're within a network and try connecting to computers on it with the WAN public IP, it simply won't work - you must use the network IP.
On an external Internet connection, it should connect fine to the public IP. If you have access to an external machine (remote desktop), or if you know of an FTP proxy, you can try it that way.
I also believe http://www.webftp.co.uk/ a web based FTP client would act as somewhat of a proxy, you could try that with the public IP and see how you go.