Help setting up ftp access needed

Hey all.
I have a powerPc running macOSX server and I experience difficulties setting it up so it can be accessed by a third party to say upload a file or something.
When I try to setup an account for a friend the work group manager tell me I'm on a node that is not visible outside my local network.
How do I authenticate for a visible one?

If he's accessing this machine, his account doesn't need to be visible to other machines on the network.
What that message is trying to tell you is that the account exists only on this machine and won't be shared to other machines in the network (which would be the case if this server was acting as a directory server).
For what you're trying to do here, that's fine - the user can authenticate using the account on this machine and you're set.

Similar Messages

  • Setting up FTP access on AEBS

    Hi everyone
    i've just purchased a new 24" imac and AEBS (the mac is spectacular). i've connected a Lacie Network Space 1TB to the AEBS and use it as a shared drive for our family.
    i've now tried to open FTP access to the Lacie and can;t get it to work. i've set up the Lacie with a user account, noted its IP address, and enabled it for ftp.
    i've then gone to the AEBS and followed the instructions in the apple manual "Designing Airport Networks 10.5" but i can;t get it to work. i've contacted Lacie who suggest its "my router" . I've searched thru this forum and others without success in nailing what i am doing wrong. i also called apple support here in Oz but they cant help either.
    Can anyone offer any advice or a checklist to get me thru?
    many thanks
    Carlo

    Hi DP
    i have searched through my Lacie info and cant find anything on ports. however, under the Port Mapping Setup Assistant in Airport Utility (which i stumbled through previously) i see it has assigned:
    PUBLIC TCP PORT : 21 and
    PRIVATE TCP PORT: 21.
    it also show the PRIVATE IP ADDRESS. 10.0.1.100
    to answer your other question, my lacie drive is available in Finder - when i click on it i see my files. and since it is connected to my AEBS i can see it also on other machines i have at home.

  • Setting up ftp access to my site

    I am using DW CS4 to create 3 low traffic sites and am serving the sites from my home desktop iMac.  I setup Virtual Hosting to allow access to my sites.  I am now trying to allow others to edit parts of the site and I believe that I must enable ftp access to the site.  I have enabled port forwarding of port 21 on my router but I am having problems.  I do the following to check ftp connection.
    In Terminal I enter  "telnet www.mywebsitename.com 21"  The response comes back "Trying (myIPaddress)...
    telnet: connect to address (myIPaddress): Operation timed out
    telnet: Unable to connect to remote host"
    I am reasonably sure that I must get this to work before I attempt to redefine the remote site definition using ftp within Dreamweaver CS4.
    Please be relatively simple with suggestions or questions, I am well aware of the fact that I am a bit of a novice trying to do rather complex things.

    Thanks for your help, I now have ftp access to my site working OK.  I 
    have redefined the site using ftp in the Dreamweaver site definitions 
    and I can upload changes with no problem.  However, i am now trying to 
    setup InContext editing capability to the site. W hen I go thru the 
    steps to add a site to the InContext Admin section the first steps in 
    the process work fine.  I am able to fill out the ftp settings with my 
    username and password and when I test the settings it comes back that 
    it is able to connect to the site.  The next step is where I run into 
    problems.  When I try to add the assets I get an error that says 
    either the folder does not exist or the user does not have the proper 
    permissions to open the root folder.  I have attached a screen shot of 
    the actual error message if it helps.  This is the odd thing.  I can 
    use the same username and password with another ftp Client program and 
    I have complete access to the root folder and all the files in it.  It 
    seems that if I have adequate permissions to view and change the root 
    folder with a generic ftp client program I ought to be able to open it 
    thru the incontext setup.  By the way the username and password I am 
    using to try to get this initially setup is the administrator username 
    and password for my server, so it seems to me there should not be a 
    permissions problem.
    Am I missing something obvious?
    Steve
    Here is the error log.  Note:   www.sonautosales.com is the name of 
    the root folder on the server.

  • Need help setting up remote access please

    I have a new server 2012 network with a server built specifically for remote access
    I need to set up simple remote access to LAN pc's, published apps, and to manage domain remotely
    this is only a test setup and I want some security but first want teh basics setup then I can lock down
    I ran the wizards and believe most things are done correctly when I added the roles, and firewall is allowing access to that server.
    when I try to connect from external I get the remote server's default IIS web page, no remote access options
    is there a simple checklist to test services internally and test the web page access internally?
    I am not sure what information you may need so please ask for any details that will be helpful
    Remote Gateway, licensing, web access and certificates have all been configured using the wizards
    David Sheetz MCP

    Hi David,
    Thank you for posting in Windows Server Forum.
    Initially to remote access the application through RD Web we need to use https://servername/rdweb. Also please check the following setting.
    In IIS: IIS Sites --> Default --> RDWeb --> Pages --> Application Settings --> DefaultTSGateway:
    Set that to your RD Gateway access URL.
    Then restart IIS.
    Your RemoteApps will then be able to find the proper gateway inbound.
    When you created your collection bring up its properties and make sure the URL is specified in RD Gateway settings too. This generates the correct settings in the RDP files.
    In addition, please checkthis article for information. Also please see whether you
    have configured RD RAP and RD CAP properly and try to uncheck the option “Bypass RD Gateway for local address” under deployment properties and verify the result.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Need help setting up ftp/home network

    I am hoping someone can help me here.
    I have an emac, imac dv se, and 2 powerbooks. They are all connected to the internet via airport cards. I want to allow all of these devices to access a firewire drive that is connected to the emac AND make those files accessible to me and my wife over the internet. what is the easiest way to do this and what additional hardware/software do I need?
    thanks in advance for the assistance!
    emac 1 Ghz SD 768   Mac OS X (10.4.1)  

    Turn on FTP in the sharing control panel. Use Connect to Server in the Finder with an FTP URL or use an FTP client or ftp in the terminal. With FTP you can do a:
    $ cd /Volumes/nameofthefirewiredrive
    then go from there.
    File Sharing on OS X only shares the "Public" directory in your home directory. You might be able to put a symlink inside Public to /Volumes/thedrivesname
    $ ln -s ~/Public/externaldrive /Volumes/externaldrive
    and try enabling Personal File Sharing and trying Connect to Server.
    If your wireless network uses DHCP, remember that the IP address of a given computer may change without warning if DHCP give it a different IP. You might have better luck using the Bonjour/Rendevous name of the computer to connect consistently.

  • Need help setting up FTP server.

    I have a networked video server that converts analog video from my security cameras to mpeg, it has an internal FTP client that I have pointed to a share on my server, with the correct login info. This will all occur on my intranet and if possible I do not want FTP open to the internet. I can not connect to the server via FTP. Any advice would be appreciated.

    John, this is all very vague.
    What is your FTP software? or if inbuilt to the OS, which OS is it?  Mac, Windows, other?
    When you say you can't connect to the FTP box, is this using your "Video server" (What OS is it)?
    Have you tried using another machine to connect to your server?
    More info please...

  • Help Setting up VPN access

    Morning all,
    Yesterday I completed the installation of my SRP527W to my existing LAN.
    I'm now trying to configure for VPN access and I'm not having much luck.
    I'm running Windows Server 2003 and i just did the following:-
    Manager Your Server - Remote Access/VPN Server - Manage this remote access/VPN Server - IP Routing - Static Routes and here I added our new Static IP address.
    So having done that, no one here can still access the server so i'm wondering if I need to set up the router to allow VPN traffic.
    Do I need to add individual profiles for people trying to gain access?
    Can someone give me some advice on what I need to do because it appears that when we can't seem to get past the router.
    Many Thanks
    *ADDITIONAL*
    I have now solved this - I needed to input the port forwarding settings to the router which now enables the pass-through.
    ISSUE RESOLVED

    OpenVPN will do the job for you - it's relatively easy to set up and it's cross-platform.

  • Problem setting up FTP

    I need some help setting up FTP. This may not be the right forum so feel free to redirect me.
    It has been a while since I tried to set up an FTP service on my Mac, certainly before 10.4.11 and before I went to my new u-verse router. I have some basic TCP/IP knowledge but things just aren’t clicking for me. I have done all the things I have done before but now when I connect to the FTP server on the local network, FTP tells me I am in Extended Passive Mode. What IS extended passive mode and how do I get back to active (interactive) mode? I have read the man pages and the section on ftp in my UNIX handbook. The question may be to simple for the books to address but it is not simple enough for me to solve. The server is on 100bT and the client is on WiFi from the same router. After I get FTP working on the local net I can redirect the port on my router for incoming internet access.

    Hi myplace,
    In extended passive mode, the FTP server operates exactly the same as passive mode, however it only transmits the port number (not broken into high and low bytes) and the client is to assume that it connects to the same IP address that was originally connected to.
    http://en.wikipedia.org/wiki/FileTransferProtocol
    Might see this also...
    http://www.askdavetaylor.com/whydo_my_ftp_transfers_all_freezeup.html

  • Remote ftp access

    I cannot get remote ftp access to my NMH405. I have remote access through https://ciscomediahub.com/ and can browse through my files this way, but I need to have remote access through ftp as well. I have set ut ftp access and it is working locally on my home network.
    What is my ftp address? 
    Can someone please help me with this problem?
    Solved!
    Go to Solution.

    If it works in your home network that means that you've set it up correctly. What you need to do know is provide the FTP service to the outside world. This generally means that you want to open up your router on port 20 and 21 and point those to the mediahub's internal IP address. If that is done, you can connect to it from the outside world via ftp://<external_ip_address_whatever_that_may_be>
    Good luck,
    Stolsel

  • Setting up FTp with PureFTP

    Hi
    I am trying to set up FTP access so that my Lab can download files from me. I have read a post (http://discussions.apple.com/thread.jspa?threadID=449518&tstart=75) regarding almost exactly the scenario that I am attempting which was resolved successfully,but I am still having troubles.
    I am running 10.4.6 on a G4 933. I have a Linksys WAG54G router.
    I have attempted to set the ports as per the instructions in PureFTP but seem not to be getting anywhere.
    A friend that is attempting to log in to test it for me gets a password and username dialog bos but it just dissappears and nothing happens or, another friend just gets a message saying that the info is not correct.
    I have tried disabling the Mac OSX firewall and with it going, and it seems not to make a diff.
    Can anyone walk me through it from start to finnish?
    Thanks very much
    Craig

    Let's make your G4 ready to tango:
    1. Drop TextWrangler (you downloaded earlier) in you Applications folder and Open it (don't check to install the command line tools, you won't need 'em)
    2. From Text Wrangler-->File-->Open Hidden navigate to the /private/etc/ directory and open hosts file. You'll get a message that hosts file is owned by root, click yes to edit it
    a default hosts file looks like this:
    # Host Database
    # localhost is used to configure the loopback interface
    # when the system is booting. Do not change this entry.
    127.0.0.1 localhost
    255.255.255.255 broadcasthost
    ::1 localhost
    3. Add the IPs of your computers and the name(s) you wan to call them (same as SystemPreferences-->Sharing), for example:
    # Host Database
    # localhost is used to configure the loopback interface
    # when the system is booting. Do not change this entry.
    127.0.0.1 localhost
    192.168.1.1 router
    192.168.1.5 michelle
    192.168.1.6 Left Machine
    192.168.1.7 G5
    255.255.255.255 broadcasthost
    ::1 localhost
    Separate IP addresses from computer names with a "tab" not space. Also, unix doesn't like spaces between names so 192.168.1.6 <tab> Left Machine gives 2 aliases for the computer @192.168.1.6, one is Left and the other is Machine. If you want one name for each computer use "-" (i.e. 192.168.1.6 <tab> Left-Machine)
    Be careful not to delete any of the default lines
    4. Save your hosts file (you'll be asked for your Admin password),
    5. Open Utilities-->Terminal and type: lookupd -flushcache (press Return)
    6. Reboot the G4
    Doing the same for each of your Macs will only make things easier for you and your network. Just make sure that you use the same computer names (or just copy/paste the contents of the G4s hosts file to the rest of your Macs (do not drop the hosts file itself to the /private/etc folder in any other Mac(s))
    Hmmmm. manual....may have to go looking for that one.
    You can download a manual from Linksys support page. I see 2 versions of the WAG54G (Version 1, Version 2).
    Now, what you need to do is to let your router allow computers outside your LAN talk to your FTP server (G4). This process is called "port mapping" or "port forwarding".
    So log in to your Linksys router via the its web interface, go to Applications & Gaming-->Port Forwarding-->Port Range Forwarding and enable the following TCP ports: 20, 21, 989, 990. Make sure that all of them point to your G4 (192.168.1.5), check Enable, Save Settings and you're done.
    FYI here are the FTP TCP ports and their names:
    TCP 20: FTP Data
    TCP 21: FTP Control
    TCP 989: FTP Data over LS/SSL
    TCP 990: FTP Control over LS/SSL
    For example:
    Application: FTP Data + Control
    Start: 20
    End: 21
    TCP/UDP: TCP
    IP Address 192.168.1.5
    Keep your firewall(s) turned off for a while till we make sure that everything is working as it should.
    At this point, networking-wise your LAN is configured like the big boys, and it's ready to rock...
    Finally, about PureFTPd:
    What do you want to share via FTP (a folder? an entire HD?)?
    Have you setup PureFTPd yet? (Accounts, folders etc)?
    Go through PureFTPd documentation again to learn the basics. Since your server will be accessed only by people you know, don't bother with anonymous users, just create accounts for your colleagues.
    Let me know how your PureFTPd setup goes...
    PS, I see that you are in NYC, been to the new Applestore? I love the glass cube design.
    No, not yet, I'm currently doing a project in Berlin/Germany. It looks nice but I wouldn't go in the first days, I don't like long queues
    Macs running 9.x, Macs running 10.4.x, SGI workstations running Irix 6.5.x
    Message was edited by: fu

  • Need Help Setting Up Wide Area Bonjour

    The subject says it all.
    Please assume I am a newbie.
    I need step by step procedure.
    Do I need a registered domain?
    Is there a web page with simple instructions.
    I want to be able to share files with family across the web - so they can download full resolution photos etc. I want to host these locally as there are many photos and it is not practical to put them on a server.
    I have tried setting up ftp on my computer and cannot access it from outside my LAN - previous question on this has not come up with any answers.
    Please help

    I don't think there is an all encompassing single source or information for you to go to. There are too many variables and choices for any one solution.
    Unless you have a static IP number from your ISP, your IP address will change on occasion. Your guests won't be able to find your machine without knowing what your IP number is. I get around this by using the service at dyndns.com. The service is free and you can get a domain name that doesn't change. You run a program on your machine that updates the ip number for your server automatically (there are a couple of consumer level routers that provide for this kind of service and you don't have to run a program on your computer).
    You will need to have an FTP server program running. You can probably do it with the OS, but I never bothered to figure out how. I just use a program named Crushftp which is a standalone FTP server with a fairly simple setup and full controls over users and groups. Ben at CrushFTP has pretty good support and keeps his software up to date.
    In addition, you will need to setup port forwarding in your router. Almost every router used in the home environment has a NAT firewall that blocks incoming connections on most ports. FTP uses port 21 TCP and the service or port must be forwarded to the Lan IP number of the machine that's hosting the FTP server.
    There are several skills you will need to learn to make this all come together and work right. You will need to install a couple of programs, learn to setup your router, create user accounts and passwords on your FTP server, and then teach your users how to use an FTP client program like YummyFTP. The machine that runs the FTP server will need to be running 24/7 so that it can answer users when required.
    Or, just use a hosting service for this kind of activity, like .Mac - give them the $100 a year, unload your pictures, build a couple of web pages that are based on their fairly simple templates, and get on with using your Mac. Using a solution like this means you only have to learn how to use one service, and you don't have to dedicate a machine for the task. You will still have to read their help menu's and understand the system, but you don't have to setup, maintain, and backup the server.

  • How do you set up ftp services with outside of network access?

    What are the steps to set up a password protected directory for our clients to ftp files to?
    I've turned on ftp services and created a testftp directory, with access to everyome, but can't access the files. It never asks me for a password.
    We have AT&T dsl service. The connection goes to a Linksys router and on to multiple switches. Each of our users have assigned static ip's.
    Thanks for the help,
    Chas

    The Mac OS X Server Security manual has a discussion of setting up ftp and the share points and related. Here's the [Tiger Security|http://images.apple.com/server/macosx/docs/TigerServer_Security_Config021507.pdf] manual, and here's [Leopard|http://images.apple.com/server/macosx/docs/LeopardServer_Security_Configv10.5.pdf].
    If you'd prefer a description here rather than the manuals, what follows are the basics.
    I'm here assuming you have a firewall between the Internet and your server; a firewall attached to the DSL modem. If you have an external static IP and an internal private (192.168.0.0/16, 10.0.0.0/8, etc) via NAT, you'll need a firewall with reasonable port-mapping capabilities. If you're static and public throughout, you need only poke holes; you probably don't need the port-mapping stuff. (Or you could have a direct connection to your Mac OS X box; I don't usually configure things that way.)
    First, open your firewall and allow access via the ftp ports (port 20 outbound and port 21 inbound, typically) and open up the ephemeral port range.
    Then create a user and directory via whichever service you are using -- Workgroup Manager, Open Directory or otherwise. Within Workgroup Manager, you can set up share points; basically locations that the ftp daemon is permitted to touch.
    Then wander into Server Admin and enable the ftp server.
    Now if I wanted to do this without exposing my cleartext username and cleartext password over every hotel and coffee shop LAN I might use (and I'm not kidding; "ftp security" is an oxymoron), I'd create a username and its directory per your usual means, use Server Admin to configure and launch sftp daemon, and open up port 22 at the firewall. In my experience, sftp is easier to administer, and operates with ssh and with PKE authentication, and it doesn't post your password to Craigslist -- and beyond discussions of the (lack of) security, ftp tends to be somewhat fragile; it really gets into trouble traversing firewalls.
    Given my experience with ftp over the years, here is [why I don't want to use ftp|http://64.223.189.234/node/530] -- sftp is just so much easier to deal with, and to secure.

  • Can someone help newbie to set up ftp on Mac OS X (10.4.7)?

    I'm completely new to Macs and need help setting up an ftp account when using Airport Express. I would really appreciate it if someone would be willing to walk me through it. Many thanks.
    Kathryn

    Well 2 things:
    1.) If youre using wireless then you almost have to be using a wireless router/firewall/base sation etc.. You need to go into that device's admin program and set up Port Forwarding.All traffic actually comes through this device first and is then routed to the computers attached to (wireless or wired). You can access this by using Applications/Utilities/Airport Admin Utility if its an apple airport base station, or by going to the devices ip address on the network if its a thrd party like Linksys or D-Link or what have you. This ip address is typically something like 192.168.1.1 or 192.168.168.1by default but you may have changed that during setup.Consult the documentation of your device for the username and pasword if you havent reset it yet. If you poke around you should see something about port forwarding... go in there and forward port 21 to your computer's local ip address (example: 192.168.1.2) .Sine most of these wont forward to a DNS name and since youre using wireless and will be loggin on and off alot i assume youll need to set up your powerbook to use a static ip address. go to System Preferences>Network>TCP/IP and choose either Static or Staic IP with DHCP. Enter the appropriate info which you can get from the Router Status page.
    2.) Makes sure youre not giving your froend your local ip address. Which will probably be the one "Sharing" tells you t o give out.YOu need to give im the public ip address which will NOT start with 192 or 127... YOu can get this address from the router status page as well.

  • Need help setting up site-to-site VPN between two ASA 5505's

    We have been pulling our hair outtrying to solve this. Below is the running configs for both Sites. We have always used Junipers prior to this. It does not appear that the tunnel is getting created. Any help would be greatly appreciated
    Basic
    Network A: (Dallas)
    10.180.1.0 / 24
    Network B: (Georgia)
    10.180.2.0 /24
    Running Config on Dallas ASA
    : Saved
    ASA Version 8.4(4)1
    hostname ACH-DALLAS
    enable password baW0bWk3Oyn6cZhc encrypted
    passwd 2KFQnbNIdI.2KYOU encrypted
    names
    interface Ethernet0/0
    switchport access vlan 2
    interface Ethernet0/1
    interface Ethernet0/2
    interface Ethernet0/3
    interface Ethernet0/4
    interface Ethernet0/5
    interface Ethernet0/6
    interface Ethernet0/7
    interface Vlan1
    nameif inside
    security-level 100
    ip address 10.180.1.1 255.255.255.0
    interface Vlan2
    nameif outside
    security-level 0
    ip address 71.123.179.111 255.255.255.0
    ftp mode passive
    clock timezone CST -6
    clock summer-time CDT recurring
    dns domain-lookup inside
    same-security-traffic permit inter-interface
    same-security-traffic permit intra-interface
    object network obj_any
    subnet 0.0.0.0 0.0.0.0
    object network Route
    subnet 0.0.0.0 0.0.0.0
    object network Outside
    host 71.123.179.111
    object network Server
    host 10.180.1.3
    object service FTP
    service tcp source range ftp-data ftp destination range ftp-data ftp
    description FTP
    object network FTP_Server
    host 10.180.1.3
    description FTP Server
    object network Site-A-Dallas-Subnet
    subnet 10.180.1.0 255.255.255.0
    description Dallas
    object network Site-B-Georgia-Firewall
    host 173.227.90.194
    description Georgia Firewall
    object network Site-B-Georgia-Subnet
    subnet 10.180.2.0 255.255.255.0
    description Georgia
    object network Georgia
    subnet 10.180.2.0 255.255.255.0
    object network Dallas
    subnet 10.180.1.0 255.255.255.0
    object-group service DM_INLINE_TCP_1 tcp
    port-object eq ftp
    port-object eq ftp-data
    access-list inside_access_in extended permit ip any any
    access-list outside_access_in extended permit ip any any
    access-list outside_access_in extended permit tcp any object FTP_Server object-group DM_INLINE_TCP_1
    access-list outside_1_cryptomap extended permit ip object Georgia object Dallas
    access-list outside_cryptomap extended permit ip object Dallas object Georgia
    pager lines 24
    logging enable
    logging asdm debugging
    mtu inside 1500
    mtu outside 1500
    no failover
    icmp unreachable rate-limit 1 burst-size 1
    no asdm history enable
    arp timeout 14400
    nat (inside,outside) source static Dallas Dallas destination static Georgia Georgia no-proxy-arp route-lookup
    object network FTP_Server
    nat (inside,outside) static interface service tcp ftp ftp
    nat (inside,outside) after-auto source static any interface destination static obj_any obj_any
    nat (inside,outside) after-auto source static any interface service FTP FTP
    access-group inside_access_in in interface inside
    access-group outside_access_in in interface outside
    route outside 0.0.0.0 0.0.0.0 71.123.179.1 1
    timeout xlate 3:00:00
    timeout pat-xlate 0:00:30
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
    timeout tcp-proxy-reassembly 0:01:00
    timeout floating-conn 0:00:00
    dynamic-access-policy-record DfltAccessPolicy
    user-identity default-domain LOCAL
    http server enable
    http 10.180.1.0 255.255.255.0 inside
    no snmp-server location
    no snmp-server contact
    snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
    crypto ipsec ikev1 transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
    crypto ipsec ikev1 transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
    crypto ipsec ikev1 transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
    crypto ipsec ikev1 transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-DES-SHA esp-des esp-sha-hmac
    crypto ipsec ikev1 transform-set ESP-DES-MD5 esp-des esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
    crypto ipsec ikev2 ipsec-proposal DES
    protocol esp encryption des
    protocol esp integrity sha-1 md5
    crypto ipsec ikev2 ipsec-proposal 3DES
    protocol esp encryption 3des
    protocol esp integrity sha-1 md5
    crypto ipsec ikev2 ipsec-proposal AES
    protocol esp encryption aes
    protocol esp integrity sha-1 md5
    crypto ipsec ikev2 ipsec-proposal AES192
    protocol esp encryption aes-192
    protocol esp integrity sha-1 md5
    crypto ipsec ikev2 ipsec-proposal AES256
    protocol esp encryption aes-256
    protocol esp integrity sha-1 md5
    crypto ipsec security-association replay window-size 1024
    crypto map outside_map 1 match address outside_cryptomap
    crypto map outside_map 1 set pfs
    crypto map outside_map 1 set peer 173.227.90.194
    crypto map outside_map 1 set ikev1 phase1-mode aggressive
    crypto map outside_map 1 set ikev1 transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
    crypto map outside_map 1 set ikev2 ipsec-proposal DES 3DES AES AES192 AES256
    crypto map outside_map 1 set ikev2 pre-shared-key *****
    crypto map outside_map interface outside
    crypto ca trustpoint _SmartCallHome_ServerCA
    crl configure
    crypto ikev2 policy 1
    encryption aes-256
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 policy 10
    encryption aes-192
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 policy 20
    encryption aes
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 policy 30
    encryption 3des
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 policy 40
    encryption des
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 enable outside
    crypto ikev1 enable outside
    crypto ikev1 policy 20
    authentication rsa-sig
    encryption aes-256
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 30
    authentication pre-share
    encryption aes-256
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 40
    authentication crack
    encryption aes-192
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 50
    authentication rsa-sig
    encryption aes-192
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 60
    authentication pre-share
    encryption aes-192
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 70
    authentication crack
    encryption aes
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 80
    authentication rsa-sig
    encryption aes
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 90
    authentication pre-share
    encryption aes
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 100
    authentication crack
    encryption 3des
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 110
    authentication rsa-sig
    encryption 3des
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 130
    authentication crack
    encryption des
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 140
    authentication rsa-sig
    encryption des
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 150
    authentication pre-share
    encryption des
    hash sha
    group 2
    lifetime 86400
    telnet 10.180.1.0 255.255.255.0 inside
    telnet timeout 5
    ssh timeout 5
    ssh key-exchange group dh-group1-sha1
    console timeout 0
    dhcpd auto_config outside
    dhcpd address 10.180.1.51-10.180.1.254 inside
    dhcpd dns 68.237.112.12 68.238.96.12 interface inside
    dhcpd enable inside
    threat-detection basic-threat
    threat-detection statistics host
    threat-detection statistics port
    threat-detection statistics protocol
    threat-detection statistics access-list
    no threat-detection statistics tcp-intercept
    ntp server 64.147.116.229 source outside prefer
    webvpn
    group-policy GroupPolicy_173.227.90.194 internal
    group-policy GroupPolicy_173.227.90.194 attributes
    vpn-tunnel-protocol ikev1 ikev2
    tunnel-group 173.227.90.194 type ipsec-l2l
    tunnel-group 173.227.90.194 general-attributes
    default-group-policy GroupPolicy_173.227.90.194
    tunnel-group 173.227.90.194 ipsec-attributes
    ikev1 pre-shared-key *****
    ikev2 remote-authentication pre-shared-key *****
    ikev2 local-authentication pre-shared-key *****
    policy-map type inspect dns preset_dns_map
    parameters
      message-length maximum client auto
      message-length maximum 512
    prompt hostname context
    call-home reporting anonymous
    Cryptochecksum:8f338f323a8f642808bd20965b793291
    : end
    no asdm history enable
    Running Config on Georgia ASA
    : Saved
    ASA Version 8.4(4)1
    hostname ACHGeorgia
    enable password 8Ry2YjIyt7RRXU24 encrypted
    passwd 2KFQnbNIdI.2KYOU encrypted
    names
    interface Ethernet0/0
    switchport access vlan 2
    interface Ethernet0/1
    interface Ethernet0/2
    interface Ethernet0/3
    interface Ethernet0/4
    interface Ethernet0/5
    interface Ethernet0/6
    interface Ethernet0/7
    interface Vlan1
    nameif inside
    security-level 100
    ip address 10.180.2.1 255.255.255.0
    interface Vlan2
    nameif outside
    security-level 0
    ip address 173.227.90.194 255.255.255.224
    ftp mode passive
    clock timezone CST -6
    clock summer-time CDT recurring
    dns domain-lookup outside
    dns server-group DefaultDNS
    name-server 216.136.95.2
    name-server 64.132.94.250
    same-security-traffic permit inter-interface
    same-security-traffic permit intra-interface
    object network obj_any
    subnet 0.0.0.0 0.0.0.0
    object network Site-A-Dallas-Firewall
    host 71.123.179.111
    description Dallas Firewall
    object network Site-A-Dallas-Subnet
    subnet 10.180.1.0 255.255.255.0
    description Dallas
    object network Site-B-Georgia-Subnet
    subnet 10.180.2.0 255.255.255.0
    description Georgia
    object network Georgia
    subnet 10.180.2.0 255.255.255.0
    object network Dallas
    subnet 10.180.1.0 255.255.255.0
    access-list inside_access_in extended permit ip any any
    access-list outside_access_in extended permit ip any any
    access-list outside_1_cryptomap extended permit ip object Dallas object Georgia
    access-list outside_cryptomap extended permit ip object Georgia object Dallas
    pager lines 24
    logging enable
    logging asdm debugging
    mtu inside 1500
    mtu outside 1500
    no failover
    icmp unreachable rate-limit 1 burst-size 1
    no asdm history enable
    arp timeout 14400
    nat (inside,outside) source static any interface destination static obj_any any
    nat (any,outside) source dynamic any interface
    nat (inside,outside) source static Georgia Georgia destination static Dallas Dallas no-proxy-arp route-lookup
    access-group inside_access_in in interface inside
    access-group outside_access_in in interface outside
    route outside 0.0.0.0 0.0.0.0 173.227.90.193 1
    timeout xlate 3:00:00
    timeout pat-xlate 0:00:30
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
    timeout tcp-proxy-reassembly 0:01:00
    timeout floating-conn 0:00:00
    dynamic-access-policy-record DfltAccessPolicy
    user-identity default-domain LOCAL
    http server enable
    http 10.180.2.0 255.255.255.0 inside
    no snmp-server location
    no snmp-server contact
    snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
    crypto ipsec ikev1 transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
    crypto ipsec ikev1 transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
    crypto ipsec ikev1 transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
    crypto ipsec ikev1 transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-DES-SHA esp-des esp-sha-hmac
    crypto ipsec ikev1 transform-set ESP-DES-MD5 esp-des esp-md5-hmac
    crypto ipsec ikev1 transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
    crypto ipsec ikev2 ipsec-proposal AES256
    protocol esp encryption aes-256
    protocol esp integrity sha-1 md5
    crypto ipsec ikev2 ipsec-proposal AES192
    protocol esp encryption aes-192
    protocol esp integrity sha-1 md5
    crypto ipsec ikev2 ipsec-proposal AES
    protocol esp encryption aes
    protocol esp integrity sha-1 md5
    crypto ipsec ikev2 ipsec-proposal 3DES
    protocol esp encryption 3des
    protocol esp integrity sha-1 md5
    crypto ipsec ikev2 ipsec-proposal DES
    protocol esp encryption des
    protocol esp integrity sha-1 md5
    crypto map outside_map 1 match address outside_cryptomap
    crypto map outside_map 1 set pfs
    crypto map outside_map 1 set peer 71.123.179.111
    crypto map outside_map 1 set ikev1 phase1-mode aggressive
    crypto map outside_map 1 set ikev1 transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
    crypto map outside_map 1 set ikev2 ipsec-proposal AES256 AES192 AES 3DES DES
    crypto map outside_map 1 set ikev2 pre-shared-key *****
    crypto map outside_map interface outside
    crypto ca trustpoint _SmartCallHome_ServerCA
    crl configure
    crypto ca certificate chain _SmartCallHome_ServerCA
    certificate ca 6ecc7aa5a7032009b8cebcf4e952d491
        308205ec 308204d4 a0030201 0202106e cc7aa5a7 032009b8 cebcf4e9 52d49130
        0d06092a 864886f7 0d010105 05003081 ca310b30 09060355 04061302 55533117
        30150603 55040a13 0e566572 69536967 6e2c2049 6e632e31 1f301d06 0355040b
        13165665 72695369 676e2054 72757374 204e6574 776f726b 313a3038 06035504
        0b133128 63292032 30303620 56657269 5369676e 2c20496e 632e202d 20466f72
        20617574 686f7269 7a656420 75736520 6f6e6c79 31453043 06035504 03133c56
        65726953 69676e20 436c6173 73203320 5075626c 69632050 72696d61 72792043
        65727469 66696361 74696f6e 20417574 686f7269 7479202d 20473530 1e170d31
        30303230 38303030 3030305a 170d3230 30323037 32333539 35395a30 81b5310b
        30090603 55040613 02555331 17301506 0355040a 130e5665 72695369 676e2c20
        496e632e 311f301d 06035504 0b131656 65726953 69676e20 54727573 74204e65
        74776f72 6b313b30 39060355 040b1332 5465726d 73206f66 20757365 20617420
        68747470 733a2f2f 7777772e 76657269 7369676e 2e636f6d 2f727061 20286329
        3130312f 302d0603 55040313 26566572 69536967 6e20436c 61737320 33205365
        63757265 20536572 76657220 4341202d 20473330 82012230 0d06092a 864886f7
        0d010101 05000382 010f0030 82010a02 82010100 b187841f c20c45f5 bcab2597
        a7ada23e 9cbaf6c1 39b88bca c2ac56c6 e5bb658e 444f4dce 6fed094a d4af4e10
        9c688b2e 957b899b 13cae234 34c1f35b f3497b62 83488174 d188786c 0253f9bc
        7f432657 5833833b 330a17b0 d04e9124 ad867d64 12dc744a 34a11d0a ea961d0b
        15fca34b 3bce6388 d0f82d0c 948610ca b69a3dca eb379c00 48358629 5078e845
        63cd1941 4ff595ec 7b98d4c4 71b350be 28b38fa0 b9539cf5 ca2c23a9 fd1406e8
        18b49ae8 3c6e81fd e4cd3536 b351d369 ec12ba56 6e6f9b57 c58b14e7 0ec79ced
        4a546ac9 4dc5bf11 b1ae1c67 81cb4455 33997f24 9b3f5345 7f861af3 3cfa6d7f
        81f5b84a d3f58537 1cb5a6d0 09e4187b 384efa0f 02030100 01a38201 df308201
        db303406 082b0601 05050701 01042830 26302406 082b0601 05050730 01861868
        7474703a 2f2f6f63 73702e76 65726973 69676e2e 636f6d30 12060355 1d130101
        ff040830 060101ff 02010030 70060355 1d200469 30673065 060b6086 480186f8
        45010717 03305630 2806082b 06010505 07020116 1c687474 70733a2f 2f777777
        2e766572 69736967 6e2e636f 6d2f6370 73302a06 082b0601 05050702 02301e1a
        1c687474 70733a2f 2f777777 2e766572 69736967 6e2e636f 6d2f7270 61303406
        03551d1f 042d302b 3029a027 a0258623 68747470 3a2f2f63 726c2e76 65726973
        69676e2e 636f6d2f 70636133 2d67352e 63726c30 0e060355 1d0f0101 ff040403
        02010630 6d06082b 06010505 07010c04 61305fa1 5da05b30 59305730 55160969
        6d616765 2f676966 3021301f 30070605 2b0e0302 1a04148f e5d31a86 ac8d8e6b
        c3cf806a d448182c 7b192e30 25162368 7474703a 2f2f6c6f 676f2e76 65726973
        69676e2e 636f6d2f 76736c6f 676f2e67 69663028 0603551d 11042130 1fa41d30
        1b311930 17060355 04031310 56657269 5369676e 4d504b49 2d322d36 301d0603
        551d0e04 1604140d 445c1653 44c1827e 1d20ab25 f40163d8 be79a530 1f060355
        1d230418 30168014 7fd365a7 c2ddecbb f03009f3 4339fa02 af333133 300d0609
        2a864886 f70d0101 05050003 82010100 0c8324ef ddc30cd9 589cfe36 b6eb8a80
        4bd1a3f7 9df3cc53 ef829ea3 a1e697c1 589d756c e01d1b4c fad1c12d 05c0ea6e
        b2227055 d9203340 3307c265 83fa8f43 379bea0e 9a6c70ee f69c803b d937f47a
        6decd018 7d494aca 99c71928 a2bed877 24f78526 866d8705 404167d1 273aeddc
        481d22cd 0b0b8bbc f4b17bfd b499a8e9 762ae11a 2d876e74 d388dd1e 22c6df16
        b62b8214 0a945cf2 50ecafce ff62370d ad65d306 4153ed02 14c8b558 28a1ace0
        5becb37f 954afb03 c8ad26db e6667812 4ad99f42 fbe198e6 42839b8f 8f6724e8
        6119b5dd cdb50b26 058ec36e c4c875b8 46cfe218 065ea9ae a8819a47 16de0c28
        6c2527b9 deb78458 c61f381e a4c4cb66
      quit
    crypto ikev2 policy 1
    encryption aes-256
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 policy 10
    encryption aes-192
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 policy 20
    encryption aes
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 policy 30
    encryption 3des
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 policy 40
    encryption des
    integrity sha
    group 5 2
    prf sha
    lifetime seconds 86400
    crypto ikev2 enable outside
    crypto ikev1 enable outside
    crypto ikev1 policy 20
    authentication rsa-sig
    encryption aes-256
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 30
    authentication pre-share
    encryption aes-256
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 40
    authentication crack
    encryption aes-192
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 50
    authentication rsa-sig
    encryption aes-192
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 60
    authentication pre-share
    encryption aes-192
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 70
    authentication crack
    encryption aes
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 80
    authentication rsa-sig
    encryption aes
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 90
    authentication pre-share
    encryption aes
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 100
    authentication crack
    encryption 3des
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 110
    authentication rsa-sig
    encryption 3des
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 130
    authentication crack
    encryption des
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 140
    authentication rsa-sig
    encryption des
    hash sha
    group 2
    lifetime 86400
    crypto ikev1 policy 150
    authentication pre-share
    encryption des
    hash sha
    group 2
    lifetime 86400
    telnet 10.180.2.0 255.255.255.0 inside
    telnet timeout 5
    ssh timeout 5
    ssh key-exchange group dh-group1-sha1
    console timeout 0
    dhcpd address 10.180.2.51-10.180.2.254 inside
    dhcpd dns 216.136.95.2 64.132.94.250 interface inside
    dhcpd enable inside
    dhcpd dns 216.136.95.2 64.132.94.250 interface outside
    no threat-detection basic-threat
    threat-detection statistics access-list
    no threat-detection statistics tcp-intercept
    webvpn
    group-policy GroupPolicy_71.123.179.111 internal
    group-policy GroupPolicy_71.123.179.111 attributes
    vpn-tunnel-protocol ikev1 ikev2
    tunnel-group 71.123.179.111 type ipsec-l2l
    tunnel-group 71.123.179.111 general-attributes
    default-group-policy GroupPolicy_71.123.179.111
    tunnel-group 71.123.179.111 ipsec-attributes
    ikev1 pre-shared-key *****
    ikev2 remote-authentication pre-shared-key *****
    ikev2 local-authentication pre-shared-key *****
    class-map inspection_default
    match default-inspection-traffic
    policy-map type inspect dns preset_dns_map
    parameters
      message-length maximum client auto
      message-length maximum 512
    policy-map global_policy
    class inspection_default
      inspect dns preset_dns_map
      inspect ftp
      inspect h323 h225
      inspect h323 ras
      inspect rsh
      inspect rtsp
      inspect esmtp
      inspect sqlnet
      inspect skinny 
      inspect sunrpc
      inspect xdmcp
      inspect sip 
      inspect netbios
      inspect tftp
      inspect ip-options
      inspect icmp
    service-policy global_policy global
    prompt hostname context
    call-home reporting anonymous
    Cryptochecksum:8bf23063c95795ec4cd59cc0e051097f
    : end
    no asdm history enable

    I am fairly new to cisco. I dont have a direct terminal connection. I ran the debug command above and through the GUI I saved these two log files. When I started logging I sent a ping packet to the other side. I can see that the Dallas location attempted to create a tunnel. When I did the same thing from Georgia it did not appear to even attempt to create a tunnel. The other thing I am seeing is that on the Georgia ASA under monitoring->VPN->Sessions there is no status to the right. On the Dallas side I see that there is 1 inactive tunnel. Any suggestions
    Log file from Dallas:
    6|Jan 23 2013|13:43:28|106015|209.221.63.27|143|71.123.179.111|2347|Deny TCP (no connection) from 209.221.63.27/143 to 71.123.179.111/2347 flags FIN ACK  on interface outside
    6|Jan 23 2013|13:43:28|302014|209.221.63.27|143|10.180.1.55|2347|Teardown TCP connection 37396 for outside:209.221.63.27/143 to inside:10.180.1.55/2347 duration 0:00:04 bytes 1603 TCP FINs
    6|Jan 23 2013|13:43:28|302013|10.180.1.55|2348|209.221.63.27|143|Built outbound TCP connection 37398 for outside:209.221.63.27/143 (209.221.63.27/143) to inside:10.180.1.55/2348 (71.123.179.111/2348)
    7|Jan 23 2013|13:43:26|752008|||||Duplicate entry already in Tunnel Manager
    6|Jan 23 2013|13:43:24|302013|10.180.1.55|2347|209.221.63.27|143|Built outbound TCP connection 37396 for outside:209.221.63.27/143 (209.221.63.27/143) to inside:10.180.1.55/2347 (71.123.179.111/2347)
    6|Jan 23 2013|13:43:22|302013|10.180.1.55|2346|209.221.63.27|143|Built outbound TCP connection 37395 for outside:209.221.63.27/143 (209.221.63.27/143) to inside:10.180.1.55/2346 (71.123.179.111/2346)
    7|Jan 23 2013|13:43:21|752008|||||Duplicate entry already in Tunnel Manager
    6|Jan 23 2013|13:43:21|302014|209.221.62.17|80|10.180.1.58|2982|Teardown TCP connection 37393 for outside:209.221.62.17/80 to inside:10.180.1.58/2982 duration 0:00:00 bytes 1387 TCP FINs
    6|Jan 23 2013|13:43:21|302013|10.180.1.58|2982|209.221.62.17|80|Built outbound TCP connection 37393 for outside:209.221.62.17/80 (209.221.62.17/80) to inside:10.180.1.58/2982 (71.123.179.111/2982)
    6|Jan 23 2013|13:43:18|302014|209.221.62.17|80|10.180.1.58|2981|Teardown TCP connection 37392 for outside:209.221.62.17/80 to inside:10.180.1.58/2981 duration 0:00:00 bytes 668 TCP FINs
    6|Jan 23 2013|13:43:17|302013|10.180.1.58|2981|209.221.62.17|80|Built outbound TCP connection 37392 for outside:209.221.62.17/80 (209.221.62.17/80) to inside:10.180.1.58/2981 (71.123.179.111/2981)
    7|Jan 23 2013|13:43:16|752008|||||Duplicate entry already in Tunnel Manager
    6|Jan 23 2013|13:43:14|302014|209.221.62.17|80|10.180.1.58|2978|Teardown TCP connection 37390 for outside:209.221.62.17/80 to inside:10.180.1.58/2978 duration 0:00:02 bytes 59217 TCP FINs
    6|Jan 23 2013|13:43:12|302013|10.180.1.58|2978|209.221.62.17|80|Built outbound TCP connection 37390 for outside:209.221.62.17/80 (209.221.62.17/80) to inside:10.180.1.58/2978 (71.123.179.111/2978)
    7|Jan 23 2013|13:43:12|752008|||||Duplicate entry already in Tunnel Manager
    6|Jan 23 2013|13:43:07|302014|209.221.63.27|143|10.180.1.55|2328|Teardown TCP connection 37129 for outside:209.221.63.27/143 to inside:10.180.1.55/2328 duration 0:10:40 bytes 17496 TCP FINs
    6|Jan 23 2013|13:43:04|302014|209.221.62.17|80|10.180.1.58|2977|Teardown TCP connection 37388 for outside:209.221.62.17/80 to inside:10.180.1.58/2977 duration 0:00:01 bytes 28170 TCP FINs
    6|Jan 23 2013|13:43:02|302013|10.180.1.58|2977|209.221.62.17|80|Built outbound TCP connection 37388 for outside:209.221.62.17/80 (209.221.62.17/80) to inside:10.180.1.58/2977 (71.123.179.111/2977)
    6|Jan 23 2013|13:43:01|302014|209.221.62.17|80|10.180.1.58|2976|Teardown TCP connection 37387 for outside:209.221.62.17/80 to inside:10.180.1.58/2976 duration 0:00:00 bytes 668 TCP FINs
    6|Jan 23 2013|13:43:01|302013|10.180.1.58|2976|209.221.62.17|80|Built outbound TCP connection 37387 for outside:209.221.62.17/80 (209.221.62.17/80) to inside:10.180.1.58/2976 (71.123.179.111/2976)
    7|Jan 23 2013|13:43:00|609002|64.74.126.6||||Teardown local-host outside:64.74.126.6 duration 1:12:35
    7|Jan 23 2013|13:42:58|710005|10.180.1.58|3266|71.123.179.111|52698|UDP request discarded from 10.180.1.58/3266 to inside:71.123.179.111/52698
    7|Jan 23 2013|13:42:52|609002|118.2.120.3||||Teardown local-host outside:118.2.120.3 duration 0:10:26
    7|Jan 23 2013|13:42:50|609002|74.125.227.101||||Teardown local-host outside:74.125.227.101 duration 1:20:36
    7|Jan 23 2013|13:42:49|752008|||||Duplicate entry already in Tunnel Manager
    7|Jan 23 2013|13:42:46|609002|64.74.103.184||||Teardown local-host outside:64.74.103.184 duration 0:12:34
    6|Jan 23 2013|13:42:46|302014|23.66.230.74|80|10.180.1.55|2320|Teardown TCP connection 37080 for outside:23.66.230.74/80 to inside:10.180.1.55/2320 duration 0:13:01 bytes 2591 FIN Timeout
    7|Jan 23 2013|13:42:44|752008|||||Duplicate entry already in Tunnel Manager
    7|Jan 23 2013|13:42:39|752008|||||Duplicate entry already in Tunnel Manager
    7|Jan 23 2013|13:42:38|609002|74.125.227.130||||Teardown local-host outside:74.125.227.130 duration 1:12:35
    7|Jan 23 2013|13:42:38|609002|74.125.227.73||||Teardown local-host outside:74.125.227.73 duration 1:12:35
    6|Jan 23 2013|13:42:35|302015|71.123.179.111|500|173.227.90.194|500|Built outbound UDP connection 37383 for outside:173.227.90.194/500 (173.227.90.194/500) to identity:71.123.179.111/500 (71.123.179.111/500)
    5|Jan 23 2013|13:42:34|750001|||||Local:71.123.179.111:500 Remote:173.227.90.194:500 Username:Unknown Received request to establish an IPsec tunnel; local traffic selector = Address Range: 10.180.1.3-10.180.1.3 Protocol: 0 Port Range: 0-65535; remote traffic selector = Address Range: 10.180.2.1-10.180.2.1 Protocol: 0 Port Range: 0-65535
    5|Jan 23 2013|13:42:34|752003|||||Tunnel Manager dispatching a KEY_ACQUIRE message to IKEv2.  Map Tag = outside_map.  Map Sequence Number = 1.
    7|Jan 23 2013|13:42:34|609001|10.180.2.1||||Built local-host outside:10.180.2.1
    7|Jan 23 2013|13:42:32|609002|192.150.19.49||||Teardown local-host outside:192.150.19.49 duration 1:52:40
    7|Jan 23 2013|13:42:32|609002|10.180.2.1||||Teardown local-host outside:10.180.2.1 duration 0:10:42
    7|Jan 23 2013|13:42:32|609002|98.138.47.63||||Teardown local-host outside:98.138.47.63 duration 1:52:41
    7|Jan 23 2013|13:42:29|609002|184.84.130.70||||Teardown local-host outside:184.84.130.70 duration 1:12:35
    Log file from Georgia:
    7|Jan 23 2013|13:47:49|609002|10.180.1.1||||Teardown local-host outside:10.180.1.1 duration 0:00:02
    6|Jan 23 2013|13:47:49|302021|10.180.1.1|0|10.180.2.2|1|Teardown ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    6|Jan 23 2013|13:47:47|302020|10.180.2.2|1|10.180.1.1|0|Built outbound ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    7|Jan 23 2013|13:47:47|609001|10.180.1.1||||Built local-host outside:10.180.1.1
    7|Jan 23 2013|13:47:44|609002|10.180.1.1||||Teardown local-host outside:10.180.1.1 duration 0:00:02
    6|Jan 23 2013|13:47:44|302021|10.180.1.1|0|10.180.2.2|1|Teardown ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    6|Jan 23 2013|13:47:42|302020|10.180.2.2|1|10.180.1.1|0|Built outbound ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    7|Jan 23 2013|13:47:42|609001|10.180.1.1||||Built local-host outside:10.180.1.1
    7|Jan 23 2013|13:47:40|609002|10.180.1.1||||Teardown local-host outside:10.180.1.1 duration 0:00:02
    6|Jan 23 2013|13:47:40|302021|10.180.1.1|0|10.180.2.2|1|Teardown ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    6|Jan 23 2013|13:47:38|302020|10.180.2.2|1|10.180.1.1|0|Built outbound ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    7|Jan 23 2013|13:47:38|609001|10.180.1.1||||Built local-host outside:10.180.1.1
    7|Jan 23 2013|13:47:30|609002|10.180.1.1||||Teardown local-host outside:10.180.1.1 duration 0:00:02
    6|Jan 23 2013|13:47:30|302021|10.180.1.1|0|10.180.2.2|1|Teardown ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    6|Jan 23 2013|13:47:28|302020|10.180.2.2|1|10.180.1.1|0|Built outbound ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    7|Jan 23 2013|13:47:28|609001|10.180.1.1||||Built local-host outside:10.180.1.1
    7|Jan 23 2013|13:47:25|609002|10.180.1.1||||Teardown local-host outside:10.180.1.1 duration 0:00:02
    6|Jan 23 2013|13:47:25|302021|10.180.1.1|0|10.180.2.2|1|Teardown ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    6|Jan 23 2013|13:47:23|302020|10.180.2.2|1|10.180.1.1|0|Built outbound ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    7|Jan 23 2013|13:47:23|609001|10.180.1.1||||Built local-host outside:10.180.1.1
    7|Jan 23 2013|13:47:20|609002|10.180.1.1||||Teardown local-host outside:10.180.1.1 duration 0:00:02
    6|Jan 23 2013|13:47:20|302021|10.180.1.1|0|10.180.2.2|1|Teardown ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    6|Jan 23 2013|13:47:18|302020|10.180.2.2|1|10.180.1.1|0|Built outbound ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    7|Jan 23 2013|13:47:18|609001|10.180.1.1||||Built local-host outside:10.180.1.1
    7|Jan 23 2013|13:47:16|609002|10.180.1.1||||Teardown local-host outside:10.180.1.1 duration 0:00:02
    6|Jan 23 2013|13:47:16|302021|10.180.1.1|0|10.180.2.2|1|Teardown ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    6|Jan 23 2013|13:47:14|302020|10.180.2.2|1|10.180.1.1|0|Built outbound ICMP connection for faddr 10.180.1.1/0 gaddr 173.227.90.194/1 laddr 10.180.2.2/1
    7|Jan 23 2013|13:47:14|609001|10.180.1.1||||Built local-host outside:10.180.1.1

  • NEED info on How to Set Router to access just one website???

    Ok here we go again, Finally found out it's my Linksys not letting me onto one website..I had a 310N and thought that was the problem so went out and bought a 610N ..same darn thing just won't let me access one website I need to sell my goods for income. I remove linksys from my modem and plug it directly into one of my computers and I got the website..Yes it's a Linksys problem !!!
    I need some info on how to set up a access point in my router's setting to let me log on to this website www.denofangels or http://74.86.166.210/
    Is it time for me to call the support team??????????????
    I'm running XP on my computers, have 3 of the 4 computers using wirelessN adapters and on the main computer is the WRT 610
    Help Please ....linksysDoll
    Gone Nutz trying to figure out Linksys again!!

    MY Internet provider is Time Warner / Roadrunner cable..Does this help you to solve my problem. Nothing wrong with the modem..just my wrt 610N settings, I'm guessing it carried over from my wrt 310N..this was working fine until a couple of months ago and then nothing for this one website.
    I'm running XP
    Thank you in advance for any help or info
    Gone Nutz trying to figure out Linksys again!!

Maybe you are looking for