Trouble with bridge mode and port forwarding

I have a Westell Model 6100F DSL modem in bridge mode into my network and I'm having trouble forwarding ports. Is there any general guidance available to do this. I have set many of my friends networks up to allow port forwarding but all have been on other service providers, mainly cable. (my experience) My network is the only one I have had trouble with.
Basically, my question is, while in bridge mode, does the modem forward all incoming traffic to my NAT router or do I need to apply special port forwarding settings in the modem to allow this?
If bridge mode is the reason I cannot forward the ports, can someone explain how to set the WEstell 6100F back to factory defaults so I can start over. 
Any other suggestions?
Thanks in advance.
Paul

If bridge mode is set up correctly, your router should be holding the Public IP address (basically not something that is a 192.168 address) as shown at http://www.whatismyip.com/ and compared against what IP your router has.
If your router has the public IP, all problems lie with either your router or your PC's firewall and configuration. I'd check out portforward.com for some guides on forwarding ports for your router or poarticular application if you need some additional help.
========
The first to bring me 1Gbps Fiber for $30/m wins!

Similar Messages

  • How do I set up Full Bridge Mode for port fowarding?

    How do i go about setting up Full bridge mode, for port forwarding on my Airport extreme's ? I Have two working to get coverage in my house, but I guess they need to be bridged together

    For most routers, including the AirPorts, bridge mode disables both the NAT & DHCP services. Since NAT is disabled, all of the firewall ports on the AirPort are open and thus port mapping/forwarding would not be reqiured. Therefore if you configure your AirPort as a bridge, the port mapping optios will not be available.
    Since you have two AirPort routers, you would only need to configure the AirPort that is NOT in bridge mode for port mapping to allow communicaton coming in from the Internet. This would typically be the AirPort attached directly to the Internet.

  • Using an airport extreme in both bridged mode and guest network with DHCP

    I currently use a third-generation airport extreme in bridge mode to connect my various Mac servers To the Internet. I'm using bridge mode on the AirPort Extreme because I have up to five static IP address (only using three now) I am currently not using the wireless network, and none of the servers are serving DHCP. I am looking at the Newer airport extreme with guest network Wi-Fi. My question is, does the new airport extreme base station support bridge- mode for any devices and host DHCP for the guest network connecting wirelessly to the base station?

    The AirPort Extreme cannot be in Bridge Mode and support a Guest Network.
    The AirPort must be configured to provide DHCP and NAT services if you want to enable the Guest Network function.
    If you really do have a 3rd Gen AirPort Extreme, it will support the Guest Network feature if you connect the AirPort directly to a simple modem.....not a modem/router or gateway type of devices.......and configure the AirPort to provide DHCP and NAT services for the network.

  • Question about TC setup, bridge mode and security...

    Hello All
    I need some help...
    Have bought a 1 Tb TC to use with my existing ethernet/wireless all-Mac home network but have some specific queries.
    The system is set-up as follows:
    Cable modem > connected by ethernet cable to > 8-way Ethernet switch
    Connected via ethernet cable to the 8-way switch are: one MacBook (in another part of the house) and the TC (via its WAN socket).
    Elsewhere in the house, and _all connected wirelessly_ are:
    iMac G5
    Powerbook G4
    hi-fi (connected via an Airport Express)
    Airport Extreme basestation to which a HP Laserjet is connected via ethernet.
    Question:
    Before buying the TC, I used a spare Airport Express basestation in its place to act as the 'main' basestation and the IP addresses of each device on the network were 10.0.0.1, 2, 3, etc. I had the impression that my home network was not "seen" by the outside world as a consequence of this.
    Now, the TC seems only to work when in 'bridge' mode and it seems that the IP addresses are 196.xxx.x.100, 101, 102 etc. Does this mean that these devices are now visible to the outside world. Have I compromised my network security? I am worried that the outside world may have access to the contents of my TC, although my TC is password protected and the wireless network is 'closed'. What else should I be doing?
    Finally, should I have set up the network so that the cable modem feeds to TC directly, with the 8-way ethernet switch coming off one of the ethernet sockets on the TC?
    In all honestly, the instructions in the manual and the help guide are less than clear.
    Can anyone help?
    Thanks
    Daniel

    Section 4, here are my thoughts.
    1. Since you are currently seeing individual IP addresses like 196.xxx.xxx.100, etc., it sounds like your modem is also acting as a router. This also seems to be the case since the Time Capsule is only working in bridged mode (it wouldn't work in Share a Public IP address if another device is assigning private DHCP addresses). Now, you could still allow the Time Capsule to act as a DHCP server on your private network by enabling Connection Sharing as Distribute a range of IP addresses. This will create a private network within your private network where all the devices that are connected to your Time Capsule can see each other. If you leave it in bridged mode then you allow your cable modem to assign DHCP addresses and all devices that are connected to the Time Capsule or to your ethernet switch are on the same network.
    2. Assuming your cable modem is acting as a router you shouldn't have to worry about security, although you will have to access your modem's settings to make sure port forwarding isn't enabled and that the firewall is turned on (although I'm sure it is). I personally would plug the ethernet switch into the LAN port of the Time Capsule and allow the WAN port of the Time Capsule to be plugged into the cable modem. I also would just leave the Time Capsule in bridged mode as well, that's what I do for my own personal network.

  • Trouble with CCME 4 and VIC2-2FXO; IOS 12.4(9)T

    Trouble with CCME 4 and VIC2-2FXO; IOS 12.4(9)T
    I am having trouble making outgoing call or answering incoming call.
    When I try to call out from my IP 7961 phone, it fails with the message "unknown number".
    For incoming call, it rings but when I pick up the call nothing happens,
    Put the receiver back on hook, the phone carries on ringing. I am in UK
    and just trying to set up test system with one analogue line. Any help will
    be most appreciated. My config of the 2811 router is posted below. All calls ineternally works fine.
    Thank you for your help.
    hostname Test-CME
    ip cef
    no ip dhcp use vrf connected
    ip dhcp excluded-address 10.10.10.1 10.10.10.10
    ip dhcp excluded-address 10.139.139.1 10.139.139.10
    ip dhcp pool host
    network 10.10.10.0 255.255.255.0
    default-router 10.10.10.1
    option 150 ip 10.10.10.1
    ip dhcp pool data
    network 10.139.139.0 255.255.255.0
    default-router 10.139.139.1
    dns-server 10.139.139.5
    voice-card 0
    no dspfarm
    voice service voip
    allow-connections h323 to h323
    allow-connections h323 to sip
    allow-connections sip to h323
    allow-connections sip to sip
    supplementary-service h450.12
    h323
    sip
    header-passing
    registrar server expires max 3600 min 3600
    interface FastEthernet0/1
    no ip address
    no ip mroute-cache
    duplex auto
    speed auto
    no shut
    interface FastEthernet0/1.2
    description ** Data VLAN **
    encapsulation dot1Q 2
    ip address 10.139.139.1 255.255.255.0
    interface FastEthernet0/1.3
    description ** Voice VLAN **
    encapsulation dot1Q 3
    ip address 10.10.10.1 255.255.255.0
    ip http server
    ip http authentication local
    no ip http secure-server
    ip http path flash:
    tftp-server flash:S00104000100.sbn
    tftp-server flash:TERM41.7-0-3-0S.loads
    tftp-server flash:term61.default.loads
    tftp-server flash:term41.default.loads
    tftp-server flash:CVM41.2-0-2-26.sbn
    tftp-server flash:cnu41.2-7-6-26.sbn
    tftp-server flash:Jar41.2-9-2-26.sbn
    tftp-server flash:term70.default.loads
    tftp-server flash:term71.default.loads
    tftp-server flash:cnu70.2-7-6-26.sbn
    tftp-server flash:Jar70.2-9-2-26.sbn
    tftp-server flash:TERM70.7-0-3-0S.loads
    tftp-server flash:CVM70.2-0-2-26.sbn
    control-plane
    voice-port 0/3/0
    connection plar opx 202
    caller-id enable
    dial-peer voice 1 pots
    incoming called-number .
    destination-pattern 9T
    port 0/3/0
    telephony-service
    load 7914 S00104000100
    load 7941 TERM41.7-0-3-0S
    load 7961 TERM41.7-0-3-0S
    load 7970 TERM70.7-0-3-0S
    max-ephones 20
    max-dn 40
    ip source-address 10.10.10.1 port 2000
    calling-number initiator
    service phone videoCapability 1
    system message MKC CME
    url services http://10.10.10.1/voiceview/common/login.do
    url authentication
    http://10.10.10.1/voiceview/authentication/authenticate.do
    time-zone 21
    date-format dd-mm-yy
    voicemail 600
    max-conferences 8 gain -6
    call-forward pattern .T
    call-forward system redirecting-expanded
    moh music-on-hold.au
    web admin system name admin secret 0 test
    dn-webedit
    time-webedit
    transfer-system full-consult dss
    transfer-pattern 9.T
    secondary-dialtone 9
    create cnf-files
    ephone-dn 1 dual-line
    number 201
    label 201
    description Sarah
    name Sarah
    ephone-dn 2 dual-line
    number 202
    label 202
    description Vitthal
    name User2 Vitthal
    ephone-dn 3 dual-line
    number 203 secondary
    label 203
    description Neil
    name User3 Neil
    ephone 1
    video
    username "user1" password 201
    mac-address 0018.18EE.947F
    type 7961 addon 1 7914
    button 1:1
    ephone 2
    video
    username "user2" password 202
    mac-address 0018.18BB.B973
    type 7941
    button 1:2
    ephone 3
    video
    username "user3" password 203
    mac-address 0018.1885.6BA2
    type 7970
    button 1:3

    Hi
    Please find enclosed debug attachment for voice ccapi and ephone. First, I called from outside. Extension 202 rings but when I answered on extension 202 nothing happens. Replace the rceiever and the pone starts ringing again.Second step. I tried to call out by dialing 9 and then number but after a while phone displays unknown number.
    Thank you for your help.
    Vitthal

  • Are "Back to my MAC" and "Port Forwarding" mutually exclusive?

    I have been using APExtreme and Port Forwarding successfully for several weeks now. The PF is to allow access to game players on a PC which acts as a server on the web. All Good.
    One more thing, I have a ISP provided wireless modem/router to talk to the cable and the world. It seems to work either bridged or un-bridged.
    I have disabled the wireless on the ISP's modem/router. (Actually the ISP's device doesn't hold a candle to the APE.)
    Still all good.
    So the firewall is on in the APExtreme and none on the modem router, and I have a port defined for my gamers to get access to my server in the APExtreme.
    I now want to implement Back to my MAC on my MBP and my other Apple devices. I believe these use iCloud for which I have an account and it seems to be working well with my iPhone.
    In Properties, when I select BtmM, iCloud says communications will be slow if I have port forwarding on. Also I will not be able to use the router function in my Modem/router.
    I'd really like to have the modem/router firewall up, and do the port forwarding there, but the BtmM will likely not get through.
    So what does anyone suggest?
    Can I use BtmM and port forwarding without too much degradation?
    Please advise.
    Thanks
    Barry

    To best answer your question on whether the two are "mutually exclusive," let take a look at how Back to My Mac (BTMM) basically works.
    BTMM - General Requirements
    OS X Leopard 10.7.3+
    Active iCloud account. Each Mac & the AirPort router, that will be relying on BTMM, needs to be configured with the same account.
    A publicly reachable IP address for your router.
    A router that supports either NAT-PMP or UPnP. For AirPorts, be sure it is running 7.6.1+ firmware.
    BTMM uses TCP port 5354 and UDP ports 4500 & 5353 for communications.
    BTMM - Basic Communication Flow
    For a computer connected to the Internet via a router, BTMM "asks" the router for its configuration information. For a router, like your AirPort, that uses NAT-PMP, BTMM will ask the router to assign arbitrary public ports. In turn, the router will provide these port assignments (& the router's Public IP address) back to BTMM.
    BTMM then sends this information to the iCloud account. In background iCloud updates a special set of DNS entries to be used by BTMM. These entries are then made available to all BTMM clients using your iCloud account. When a computer, with BTMM enabled, uses your iCloud credentials, it automatically retrieves a list of all other computers/routers that are registered with the same account. All these devices should then appear under the SHARED section of the Finder.
    When attempting to connect to a remote computer (or router), BTMM creates a secure connection to that remote device using the information from the iCloud account.
    Once the connection is established, the devices can then communicate with each other.
    So potentially, unless you are using Port Mapping for any of the ports BTMM uses, they should not conflict.

  • Airport express in bridge mode and wrong IP

    Hi all,
    my airport express is driving me nuts!! I'm trying to set it up in bridge mode, just to share the printer and to use airplay, bridging the network of my ISP router, that works fine in wifi mode with all my devices (tested with: 2 MacBookPro, 3 iphone, 1 ipad).
    The issue is that I configure the AE to join my network (using airport utility), it restarts and works just for few minutes and then it drops the IP, and it turns out to not be visible even for airport utility.
    I've noticed that in the summary configuration page of airport utility the IP assigned to the AE is kind of  169.254.X.X that means that the AE is not reciving a valid IP from the router. But, if I press "manual setup" and load the internal configution, in the TCP/IP pannel there is a righ IP number.
    But it stops working anyway :-(
    I've already tried to configure it with a static IP num (in my IP range), but it did not work as well.
    Last thing: my AE is the old one, 802.11g.
    Any suggestion?
    thanks in advance and happy new year ;-)

    When the AirPort is setup to operate in Bridge Mode, all ports behave as if they were LAN <--> ports, so it would not make any difference which port is used. As a personal preference, and also to aid in troubleshooting, I use the WAN "O" port when configuring a network, if only to know at a glance which cable is which.
    The settings on the AirPort are interactive, so when/if you change the Network Mode to "create a wireless network", that will throw the AirPort back into router mode, so always check to make sure that the AirPort is in Bridge Mode as the last step before you click update to save the settings.

  • Trouble with Bridge CS5.1

    I am running the latest version of the Lion (10.7.2).
    After the upgrade of Camera Raw Bridge become unstable and useless for me.
    As soon as I try to click on the menu bar the Bridge freeze and it is not possible to do other than using the forced termination (opt / cmd / esc).
    I have reset the preferences, purge the entire Thummbnail Cache and reset to Standard Workspaces.
    I have taken the previous version from backup and made a restart. But the problem is still there.
    Is there anyone else who has experienced this?
    Will a reinstallation of Bridge solve the problem?
    Kind regards
    Venche Jensen.

    I will try to remove the ARC, and then try to revert to the previous version of ARC.
    I have tried to open a raw file via Photoshop. It wount work. I will giv you a feedback when done.
    Sendt fra min iPad
    Den 16. okt. 2011 kl. 18:38 skrev Omke Oudeman <[email protected]>:
    Re: Trouble with Bridge CS5.1
    created by Omke Oudeman in Bridge Macintosh - View the full discussion
    Since the menu bar on top hang too, I think it is a combination of problem the upgrade of Mac OS and Bridge + ACR.
    If you have the option to revert to the previous version of ACR (6.4) and check if this sorted things out it might be helpful for all other users. Personal I have not yet upgraded to Lion (I'm on 10.6.8) and have ACR 6.5 installed. It only gives me the problem that I can't choose an other location for the files in Adobe Photo downloader but that's fine, I always have the same folder i sent them to so that is working for me.
    If you have a back up inTime Machine or other Back Up try to find the 6.4 version. Or check the thread about Photodownloader to see how I retrieved it with re install.
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/3973971#3973971
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/3973971#3973971. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Bridge Macintosh by email or at Adobe Forums
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Trouble with internal keyboard and touchpad

    Hi,
    Yesterday I just out of nowhere started having some trouble with my keyboard and touchpad on my MacBook Air.
    The problem displayed itself on various ways. One thing was that I couldn't press regulary with the touchpad. When I was pressing one time, it acted like a pressed with two fingers. When I tried to type in my password on the administrator page, some of the keys didn't work at all and some started to act weird. For example when I was pressing the letter B, the "bar" which displayes where you are in the text (don't know the word in English) went backwards, and when I pressed the letter F it went forward. This seemes so weird and also gives me a hope that it might be some setting failure though B stands for backwards and F stands for forward.
    I could log in to the guestpage where I tried to write in "notes". In notes, no letters at all was working, only numbers. When I tried to shut the computer down from the apple symbol I was asked to write administrator name and password. When I tried to mark the name to write it, there wasn't a "bar" but a cross, but on the other hand did it work to write in the password field. But of course not B and F..
    Usualy I'd just press the on/off botton until the computer lockdown, unfortunately the botton doesn't work. So the only thing I could do was to let the battery die and hope that it would start when I recharged it and pressed start, this didn't go as well as I hoped, so now I'm stuck with a dead macbook air.
    Any ideas of what could be the problem or/and any solutions what might do the trick?
    Extremly greatful for any answers

    Yes you need to use a wired keyboard.

  • Trouble with LaCie disk and time machine

    HI everyone,
    I've been having trouble with using time machine to back-up to my 1 TB LaCie drive (purchased 5/12, unfornuately I was dumb and didn't register the drive and no longer have the box with the serial number and there is no serial number on my drive. The only problem I had up until the end of August was that every so often the LaCie drive (using my FW 800 port) would unmount after waking up from sleep.
    The end of August the drive unmounted for no reason while I was on the computer doing a task. Could not get the LaCie drive remounted (rebooting, etc. etc.) To make a long story short, ended up calling apple care who took me through resetting my SMC and PRAM to no avail. Was booted to higher level of support who walked me through trying to repair my drive using the disk utiltiy. When that didn't work, she walked me through erasing and reformatting the LaCie drive and starting a new time machine back-up. Every thing ok until about ten days ago.
    Last week, when I woke my iMac up from sleep, I got an error saying that the disk was not ejected properly and I could not mount the drive. Restarting did nothing, the disk did not  mount. Shutting down and rebooting seemed to solve the problem and the disk was mounted. Every so often I've had the problem with the disk unmounting after waking up from sleep before. So, I changed my energy sleep preferences. At the end of the day when I am done, I'd unmount the LaCie drive before putting the Mac to sleep using the apple menu.
    Today I came in to start my day, plugged the drive in and it would not mount. Tried rebooting nothing. Went into the disk utility, at first the LaCie drive passed the disk verify (6:26:25 and 6:26:38). Then I went into repair disk on the indented drive at 6:27:13, I wasn't sure what it is was doing, thinking that it had hung, I stopped the repair at 6:27:24. Exited disk utility, and the LaCie drive mounted. But I was getting a read only error when I tried to back-up using time machine. So, I went back into disk utility at 6:27:35, when I verified the disk (indented disk), I got an error saying the disk need to be repaired. After several minutes the disk could not be repaired. So, I erased and reformatted the drive. Ran a time machine back-up and it seemed to back-up everything on my hard drive. Just ran another verify disk and it passed.
    Is the drive failing? Have some other back-ups of my documents, my address book, iCal and am going to make a backup of some of my pref files and important e-mail files and am going to do some more back-ups after I am done.
    Have reached out to the women at apple care whom I talked to last August, but don't expect to hear back from her for at least 24 hours.
    Here is my disk utility log
    2013-11-07 06:26:25 -0500: Verifying partition map for “LaCie”
    2013-11-07 06:26:25 -0500: Starting verification tool:
    2013-11-07 06:26:25 -0500: Checking prerequisites
    2013-11-07 06:26:25 -0500: Checking the partition list
    2013-11-07 06:26:25 -0500: Checking for an EFI system partition
    2013-11-07 06:26:25 -0500: Checking the EFI system partition’s size
    2013-11-07 06:26:25 -0500: Checking the EFI system partition’s file system
    2013-11-07 06:26:25 -0500: Checking all HFS data partition loader spaces
    2013-11-07 06:26:25 -0500: Checking Core Storage Physical Volume partitions
    2013-11-07 06:26:25 -0500: The partition map appears to be OK
    2013-11-07 06:26:25 -0500:
    2013-11-07 06:26:25 -0500:
    2013-11-07 06:26:38 -0500: Verifying partition map for “LaCie”
    2013-11-07 06:26:38 -0500: Starting verification tool:
    2013-11-07 06:26:38 -0500: Checking prerequisites
    2013-11-07 06:26:38 -0500: Checking the partition list
    2013-11-07 06:26:38 -0500: Checking for an EFI system partition
    2013-11-07 06:26:38 -0500: Checking the EFI system partition’s size
    2013-11-07 06:26:38 -0500: Checking the EFI system partition’s file system
    2013-11-07 06:26:38 -0500: Checking all HFS data partition loader spaces
    2013-11-07 06:26:38 -0500: Checking Core Storage Physical Volume partitions
    2013-11-07 06:26:38 -0500: The partition map appears to be OK
    2013-11-07 06:26:38 -0500:
    2013-11-07 06:26:38 -0500:
    2013-11-07 06:27:13 -0500: Disk Utility started.
    2013-11-07 06:27:21 -0500: Verifying and repairing partition map for “LaCie”
    2013-11-07 06:27:21 -0500: Starting repair tool:
    2013-11-07 06:27:21 -0500: Checking prerequisites
    2013-11-07 06:27:21 -0500: Checking the partition list
    2013-11-07 06:27:21 -0500: Checking for an EFI system partition
    2013-11-07 06:27:21 -0500: Checking the EFI system partition’s size
    2013-11-07 06:27:21 -0500: Checking the EFI system partition’s file system
    2013-11-07 06:27:23 -0500: Checking all HFS data partition loader spaces
    2013-11-07 06:27:24 -0500: Reviewing boot support loaders
    2013-11-07 06:27:24 -0500: Checking Core Storage Physical Volume partitions
    2013-11-07 06:27:24 -0500: Updating Windows boot.ini files as required
    2013-11-07 06:27:24 -0500: The partition map appears to be OK
    2013-11-07 06:27:24 -0500:
    2013-11-07 06:27:24 -0500:
    2013-11-07 06:27:35 -0500: Verifying volume “LaCie”
    2013-11-07 06:27:35 -0500: Starting verification tool:
    2013-11-07 06:27:35 -0500: Checking file system2013-11-07 06:27:35 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:27:35 -0500:
    2013-11-07 06:27:35 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
    2013-11-07 06:28:05 -0500:
    2013-11-07 06:28:13 -0500: Verify and Repair volume “LaCie”
    2013-11-07 06:28:13 -0500: Starting repair tool:
    2013-11-07 06:28:13 -0500: Checking file system2013-11-07 06:28:13 -0500: Volume repair complete.2013-11-07 06:28:13 -0500: Updating boot support partitions for the volume as required.2013-11-07 06:35:05 -0500: Stopped by user
    2013-11-07 06:44:56 -0500: Disk Utility started.
    2013-11-07 06:45:20 -0500: Verifying volume “LaCie”
    2013-11-07 06:45:20 -0500: Starting verification tool:
    2013-11-07 06:45:20 -0500: Checking file system2013-11-07 06:45:20 -0500: Checking Journaled HFS Plus volume.
    2013-11-07 06:45:20 -0500: Checking extents overflow file.
    2013-11-07 06:45:20 -0500: Checking catalog file.
    2013-11-07 06:45:59 -0500: Missing thread record (id = 5057741)
    2013-11-07 06:46:06 -0500: Checking multi-linked files.
    2013-11-07 06:46:19 -0500: Checking catalog hierarchy.
    2013-11-07 06:46:38 -0500: Invalid directory item count
    2013-11-07 06:46:38 -0500: (It should be 0 instead of 4)
    2013-11-07 06:46:38 -0500: Invalid volume directory count
    2013-11-07 06:46:38 -0500: (It should be 166840 instead of 166841)
    2013-11-07 06:46:38 -0500: Checking extended attributes file.
    2013-11-07 06:47:05 -0500: Checking multi-linked directories.
    2013-11-07 06:48:10 -0500: Checking volume bitmap.
    2013-11-07 06:48:12 -0500: Checking volume information.
    2013-11-07 06:48:12 -0500: The volume LaCie was found corrupt and needs to be repaired.
    2013-11-07 06:48:12 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:48:12 -0500:
    2013-11-07 06:48:12 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
    2013-11-07 06:48:12 -0500:
    2013-11-07 06:50:02 -0500: Verify and Repair volume “LaCie”
    2013-11-07 06:50:02 -0500: Starting repair tool:
    2013-11-07 06:50:02 -0500: Checking file system2013-11-07 06:50:02 -0500: Checking Journaled HFS Plus volume.
    2013-11-07 06:50:02 -0500: Checking extents overflow file.
    2013-11-07 06:50:02 -0500: Checking catalog file.
    2013-11-07 06:50:41 -0500: Missing thread record (id = 5057741)
    2013-11-07 06:50:48 -0500: Checking multi-linked files.
    2013-11-07 06:51:02 -0500: Checking catalog hierarchy.
    2013-11-07 06:51:20 -0500: Invalid directory item count
    2013-11-07 06:51:20 -0500: (It should be 0 instead of 4)
    2013-11-07 06:51:20 -0500: Invalid volume directory count
    2013-11-07 06:51:20 -0500: (It should be 166840 instead of 166841)
    2013-11-07 06:51:20 -0500: Checking extended attributes file.
    2013-11-07 06:51:47 -0500: Checking multi-linked directories.
    2013-11-07 06:52:55 -0500: Checking volume bitmap.
    2013-11-07 06:52:56 -0500: Checking volume information.
    2013-11-07 06:52:56 -0500: Repairing volume.
    2013-11-07 06:52:56 -0500: Missing directory record (id = 5057741)
    2013-11-07 06:52:56 -0500: Look for missing items in lost+found directory.
    2013-11-07 06:53:10 -0500: Rechecking volume.
    2013-11-07 06:53:10 -0500: Checking Journaled HFS Plus volume.
    2013-11-07 06:53:10 -0500: Checking extents overflow file.
    2013-11-07 06:53:10 -0500: Checking catalog file.
    2013-11-07 06:53:16 -0500: Incorrect number of thread records
    2013-11-07 06:53:22 -0500: Checking multi-linked files.
    2013-11-07 06:53:35 -0500: Checking catalog hierarchy.
    2013-11-07 06:53:53 -0500: Invalid directory item count
    2013-11-07 06:53:54 -0500: (It should be 5 instead of 6)
    2013-11-07 06:53:54 -0500: Invalid volume directory count
    2013-11-07 06:53:54 -0500: (It should be 166844 instead of 166842)
    2013-11-07 06:53:54 -0500: Invalid volume file count
    2013-11-07 06:53:54 -0500: (It should be 1056326 instead of 1056321)
    2013-11-07 06:53:54 -0500: Checking extended attributes file.
    2013-11-07 06:54:20 -0500: Checking multi-linked directories.
    2013-11-07 06:55:25 -0500: Checking volume bitmap.
    2013-11-07 06:55:26 -0500: Checking volume information.
    2013-11-07 06:55:26 -0500: Repairing volume.
    2013-11-07 06:58:06 -0500: Rechecking volume.
    2013-11-07 06:58:06 -0500: Checking Journaled HFS Plus volume.
    2013-11-07 06:58:06 -0500: Checking extents overflow file.
    2013-11-07 06:58:07 -0500: Checking catalog file.
    2013-11-07 06:58:12 -0500: Incorrect number of thread records
    2013-11-07 06:58:18 -0500: Checking multi-linked files.
    2013-11-07 06:58:31 -0500: Checking catalog hierarchy.
    2013-11-07 06:58:50 -0500: Invalid volume directory count
    2013-11-07 06:58:50 -0500: (It should be 166844 instead of 166842)
    2013-11-07 06:58:50 -0500: Invalid volume file count
    2013-11-07 06:58:50 -0500: (It should be 1056326 instead of 1056321)
    2013-11-07 06:58:50 -0500: Checking extended attributes file.
    2013-11-07 06:59:17 -0500: Checking multi-linked directories.
    2013-11-07 07:00:22 -0500: Checking volume bitmap.
    2013-11-07 07:00:24 -0500: Checking volume information.
    2013-11-07 07:00:24 -0500: Repairing volume.
    2013-11-07 07:03:03 -0500: Rechecking volume.
    2013-11-07 07:03:03 -0500: Checking Journaled HFS Plus volume.
    2013-11-07 07:03:03 -0500: Checking extents overflow file.
    2013-11-07 07:03:04 -0500: Checking catalog file.
    2013-11-07 07:03:09 -0500: Incorrect number of thread records
    2013-11-07 07:03:15 -0500: Checking multi-linked files.
    2013-11-07 07:03:29 -0500: Checking catalog hierarchy.
    2013-11-07 07:03:47 -0500: Invalid volume directory count
    2013-11-07 07:03:47 -0500: (It should be 166844 instead of 166842)
    2013-11-07 07:03:47 -0500: Invalid volume file count
    2013-11-07 07:03:47 -0500: (It should be 1056326 instead of 1056321)
    2013-11-07 07:03:47 -0500: Checking extended attributes file.
    2013-11-07 07:04:14 -0500: Checking multi-linked directories.
    2013-11-07 07:05:19 -0500: Checking volume bitmap.
    2013-11-07 07:05:20 -0500: Checking volume information.
    2013-11-07 07:05:20 -0500: The volume LaCie could not be repaired after 3 attempts.
    2013-11-07 07:05:21 -0500: Volume repair complete.2013-11-07 07:05:21 -0500: Updating boot support partitions for the volume as required.2013-11-07 07:05:21 -0500: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-11-07 07:05:21 -0500:
    2013-11-07 07:05:21 -0500: Disk Utility stopped repairing “LaCie”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    2013-11-07 07:05:21 -0500:
    2013-11-07 07:09:45 -0500: Disk Utility started.
    2013-11-07 07:11:45 -0500: Preparing to erase : “LaCie”
    2013-11-07 07:11:45 -0500:     Partition Scheme: GUID Partition Table
    2013-11-07 07:11:45 -0500:     1 volume will be erased
    2013-11-07 07:11:45 -0500:         Name        : “LaCie”
    2013-11-07 07:11:45 -0500:         Size        : 999.86 GB
    2013-11-07 07:11:45 -0500:         File system    : Mac OS Extended (Journaled)
    2013-11-07 07:11:45 -0500: Unmounting disk
    2013-11-07 07:11:45 -0500: Erasing
    2013-11-07 07:11:54 -0500: Initialized /dev/rdisk1s2 as a 931 GB HFS Plus volume with a 81920k journal
    2013-11-07 07:11:54 -0500: Mounting disk
    2013-11-07 07:11:54 -0500: Erase complete.
    2013-11-07 07:11:54 -0500:
    2013-11-07 10:38:00 -0500: Disk Utility started.
    2013-11-07 10:38:12 -0500: Verifying volume “LaCie”
    2013-11-07 10:38:12 -0500: Starting verification tool:
    2013-11-07 10:38:14 -0500: Checking file system2013-11-07 10:38:14 -0500: Checking Journaled HFS Plus volume.
    2013-11-07 10:38:14 -0500: Checking extents overflow file.
    2013-11-07 10:38:14 -0500: Checking catalog file.
    2013-11-07 10:38:29 -0500: Checking multi-linked files.
    2013-11-07 10:38:29 -0500: Checking catalog hierarchy.
    2013-11-07 10:38:41 -0500: Checking extended attributes file.
    2013-11-07 10:39:04 -0500: Checking multi-linked directories.
    2013-11-07 10:39:31 -0500: Checking volume bitmap.
    2013-11-07 10:39:32 -0500: Checking volume information.
    2013-11-07 10:39:32 -0500: The volume LaCie appears to be OK.
    2013-11-07 10:39:32 -0500: Repair tool completed:
    2013-11-07 10:39:32 -0500:
    2013-11-07 10:39:32 -0500:

    I just got a call back from the upper level support person at apple care who had been advising me on my trouble with time machine and my LaCie 1 TB FWD. I had sent her much of the same verbiage as I posted here. As some of you have probably figured out, the verdict is that the drive is probably failing. She says this because I have had to do two erase and reformats. She thought that the intermitant problem that I have had with the drive unmounting when my iMac wakes from sleep could be related to the drive failing.
    In the meantime I have a secondary back-up (not using time machine) and the LaCie  1 TB FWD is working for the moment.
    Thanks to all who read all my verbiage.
    And in the meantime, I've learned something. I marked this question as solved. But I'm open to other things to try.
    Message was edited by: njtreehugger minor edits and update

  • AirPort Time Capsule. Read everything and tried everything. Can't get a guest network to work. Switched from bridge mode and still doesn't work. Anyone able to set up a guest network?

    AirPort Time Capsule. Read everything and tried everything. Can't get a guest network to work. Switched from bridge mode and still doesn't work. Anyone able to set up a guest network?

    I had a bright house cable modem that also had built-in wi-fi.
    Don't mean to be picky here, but if the "modem" had built in Wi-Fi, it was not a modem. It was a modem/router, also known as a gateway type of device.
    A device like this combines the functions of a separate modem and separate router in one package. Turning off the wireless on a device like this does not make a it modem.....it is still a modem/router or gateway with the WiFi turned off.
    I think that if I have them replace the current "complicated" modem with a "simple" one I should be able to get the guest network up and running.
    That would be correct. Hopefully, they offer this type of option for their customers.

  • WRT54G2 v1.5 and Port Forwarding.

    For some reason my WRT54G2 is not forwarding ports correctly.  I have a development server running Windows Server 2008 and IIS behind the WRT with the correct external ports forwarded to the corresponding internal ports however any outside connection to these ports times out.  To knock the firmware as being the issue out I downloaded the newest listed on the support site (1.5.00.019) and performed the 30/30/30 reset.  Still unable to see these ports open externally.  Finally out of frustration I dusted off my old router and opened up the ports to my machine and was able to hit the ports right away.  Is this an ongoing issue or anyone know of a surefire fix for this?

    Comcast (business with static IP) is the ISP.  My WAN IP is correct and I'm able to access the internet just fine on the server and wireless clients connected to it.  As far as ports open I currently have four; two of the ports are standard HTTP, one is for SSL, and one is for VPN.  All of which point to the same development server.  And as stated before I took my old router (WRT54g v2.0) and set it up with virtually the same settings and have been able to communicate with the server remotely.

  • We recently switched ISPs. To connect to the new ISP our Airport Extreme has to be in bridge mode. Now our Nintendo Wii won't connect to the Airport. Is it an issue with bridge mode that is causing this?

    We recently switched ISPs. To connect to the new ISP our Airport Extreme has to be in bridge mode. Now our Nintendo Wii won't connect to the Airport. Is it an issue with bridge mode that is causing this? We're running two Macs wirelessly with no problems.  And the Wii did connect before the switch.

    Hello and thanks for the reply.  I gave this a try, turned off Airport on one of the computers and tried the Wii again.  Still no connection.  I should say that we're also running an old G4 (wired) off the Airport as well, with no problems.  I've tried many things to make the Wii to work, including power cycling the Airport, turning off the security settings in the Airport, resetting the Airport to it's default and redoing the network, resetting the network setting on the Wii (several times), moved the Airport closer to the Wii, all with no luck.  The Wii "sees" the Airport but won't connect to it.  I'm at a loss for anything else to try, so any help is appreciated.

  • Dhcp setting and port forward

    I am using wrt54gx4. I have a IP camera connected to it. I can view the live images on the intranet and internet. Not too long ago my DSL company upgraded my DSL modem to a newer model. Then I can not connect to the internet by PPPoe. DHCP is fine. So the only connection type works is DHCP. But now I can not view the live images on the internet. I can only view the live images on intranet( I mean if I open web browser and type http:///192.168.xx.xxx:4545, 4545 is the port, I can view the live image), how can I solve this problem?

    You probably have the notorious double nat issue. I'm sure your new modem is actually a gateway so you can either put it into bridge mode and do PPPoE from the wrt54gx4, or more simply, turn the wrt54gx4 into an access point/switch by using option #1 in this guide. 
    After using option #1, you should open any necessary ports by accessing the gateway's GUI. 
    I don't work for Cisco. I'm just here to help.

  • Can a single Access Point support both bridge mode and Access Point mode at the same time

    Hi Guys
    Does anyone know which access point can work in both bridge mode and AP mode ?
    Cheers

    Well what are you trying to cover. If its really a large outdoor area, then look at the mesh AP. Those require a WLC. Autonomous or stand alone ap can perform bridging on one radio and client access on another. You can also look at AP that support indoor mesh that also controlled by a wlc. If your putting APs outdoors, then look at the outdoor mesh.
    Thanks,
    Scott Fella
    Sent from my iPhone

Maybe you are looking for