Aebs in bridgemode or not

when i bought my aebs two years or so ago, i got it finally working with the help of this forum. the modem/router/wlan station that came with the dsl (t-com, germany, "speedport w 701 v") has its wlan switched off. the aebs is connected to the t-com box and is set to bridge mode. i am using the aebs on top of the t-com box because its wlan (n, g-compatible) is faster than the t-com box's wlan (g), because the aebs can be configured wirelessly, and because it has the usb port i need for the printer. the setup works generally fine. current clients are: g5, macbook, logitech squeezebox and transporter, ps3.
when i updated the firmware on the t-com box the other night, i realized that its dhcp and nat can be turned off so that the t-com box operates only as a modem (the one function that's missing in the aebs for me).
i am now wondering if i should go down that route and "move" dhcp/nat from the t-com box to the aebs. HOWEVER, i am quite happy that my setup works fine (touch wood) and would only change it if there are clear advantages. are there any?
thank you for your thoughts.

i am now wondering if i should go down that route and "move" dhcp/nat from the t-com box to the aebs. HOWEVER, i am quite happy that my setup works fine (touch wood) and would only change it if there are clear advantages. are there any?
There really aren't any advantages for switching the NAT & DHCP responsibilities from the Speedport to the AEBS. Since your network is working, I suggest leaving it alone. The other adage, "If it works, don't fix it!" applies well here. In addition, the AEBS's firewall features are limited. You may find that your Speedport offers more options and would be better suited for the job.

Similar Messages

  • AEBS sees drive, but not the partition on it

    Hi folks,
    I try to connect a WD 1TB SATA2 drive in a Fantec USB enclosure* to my Airport Extreme Base Station. I have tons of stuff on the drive, "unified" from various older external and internal drives.
    Now, while Airport Utility "sees" the physical disk in the list of Airdisks, it does not actually mount the single HFS+ (Journaled) formatted partition/volume on it.
    1) It mounts nicely on my MacBook Pro, and I can also access it using MacDrive on my PC.
    2) I checked it using Disk Utility, everything is fine.
    3) I even checked it in Disk Warrior, and rebuilt the directory structure for good measure.
    4) The partition's name is only 14 characters, no spaces, no High ASCII characters.
    5) It mounts without problems on my Win XP PC with MacDrive 7 via USB.
    I tried rebooting the AEBS, but no success. Another, older 250 GB external drive (also HFS formatted) connected fine, the volume immediately appeared in Airport Utility, no restarting necessary (sadly it's an IDE enclosure, not SATA).
    *The Fantec enclosure uses a JMicron JM20336 SATA to USB chipset, if anyone cares to know.
    EDIT: latest Mac OS, latest AEBS firmware 7.3.2, latest Airport Utility on Mac and PC, etc.
    I'm stumped, why can't the AEBS see the volume?
    I hope anyone has an idea what's wrong. Maybe the enclosure is not compatible with the AEBS?

    Ok, I had the chance to test another SATA drive in the same HD enclosure, and Airport Extreme recognized the drive. It was formatted as FAT. Other partitions on the same drive were formatted NTFS, and the Airport warned me about a faulty disc.
    In any case, it is now verified that it is not the enclosure, but seemingly the drive itself that isn't recognized by the AEBS.
    Next, I did various tests to see what is wrong. Remember, this is a brand new 1TB Western Digital Green (3 platters, the most recent model). Other (smaller) drives in the same or other enclosures work fine.
    *Test 1:* format the drive using HFS (Journaled)
    Expected result: partition should mount as volume with name "xD".
    Actual result: partition does not mount (as can be seen on the screenshot)
    !http://666kb.com/i/b631xlvxyii0kboty.png!
    *Test 2:* format the drive as NTFS using MacFUSE
    Expected result: error alert by AEBS (faulty drive)
    Actual result: no luck (see screenshot above)
    NOTE: At this point, I didn't have the option in Disk Utility to format as FAT - I don't know why.
    *Test 3:* format the drive as NTFS using a Windows XP PC using the Management Console
    Expected result: error alert by AEBS (faulty drive)
    Actual result: error alert by AEBS (faulty drive)
    NOTE: After this test, the option in Disk Utility to format as FAT has reappeared. Maybe formatting in XP fixed some partition table error? Or the disk is now formatted in MBR mode rather than GUID?
    *Test 4:* format as FAT (using Disk Utility)
    Expected result: mount the partition
    Actual result: partition mounts! As you can see in the screenshot, the volume name is "XD" instead of "xD" because FAT only supports upper case volume names.
    !http://666kb.com/i/b632kbz0xp0lihk6u.png!
    *Test 5:* format the drive as HFS (Journaled) again
    Expected result: mount the partition
    Actual result: Disk Utility fails to delete the FAT partition (see screenshot)
    !http://666kb.com/i/b632se0dzj9fknwxi.png!
    At this point, I am trying a few things to delete the FAT partition. First, I reformat using FAT, which succeeds. Formating as NTFS also works. I click on the drive icon rather than the volume icon, and see that the disk IS using the Master Boot Record scheme. I guess this is why I can't format the partition as HFS...
    *Test 6:* re-partition the drive with 1 HFS (Journaled) partition, this time specifically setting MBR as scheme.
    Expected result: formatting will fail, because I guess HFS doesn't work on MBR partitioned drives
    Actual result: yup, Disk Utility fails to do this
    *Test 7*: re-partition the drive, using GUID with 1 HFS (Journaled) partition
    Expected result: partition mounts
    Actual result: partition mounts - SUCCESS!
    !http://666kb.com/i/b633840bd5mkinjw6.png!
    CONCLUSION:
    If a drive fails to mount in AEBS, there is most likely something wrong with the partition table. Try repartitioning the drive (either using GUID or MBR) and see if this fixes the problem.
    Hope that helps,
    Stefan

  • New AEBS 5x faster, but not everywhere ?!?

    the apple.com pages says it's 5 times the performance. so far so good, but the german and the UK page says it's 2.5 times faster.
    the german und UK apple online store gives me the information that it's 5 times faster (in the description) with a little "2.5x faster" square sign next to it.
    I'm confused now.
    Any other apple page and online store I had a look at (France, Ireland,Australia, New Zealand and of course US) says "5 times faster" in the description and in that square sign.
    Does anyone know what the deal is ?

    the apple.com pages says it's 5 times the
    performance. so far so good, but the german and the
    UK page says it's 2.5 times faster.
    the german und UK apple online store gives me the
    information that it's 5 times faster (in the
    description) with a little "2.5x faster" square sign
    next to it.
    In order to get the 5x speed you need to be using wide-channel operation.
    The following countries do not allow wide-channel operation: Austria, Estonia, Germany, Japan, Latvia, Slovakia, Spain, United Kingdom.
    Which means you only get the 2.5x advantage over 802.11g when using 802.11n - only between 802.11n devices.
    iFelix

  • Small Office AEBS Not Re-Connecting

    My apologies if this question has already been addressed.
    I have hooked up an AEBS in a small office. It seems to work well, but takes a long time reconnecting wireless computers. It is sometimes (almost always) necessary to restart the AEBS.
    The WAN port of the AEBS is connected to a T1 router from the ISP. A LAN port is connected to the uplink of a Linksys switch. There is a mixture of Macs and XP. All the Macs are wireless, including 2 Mac Mini's, a Macbook, a Macbook Pro, and a Powerbook G4 (mine).
    Again, everything works very well once I do a restart of the AEBS, but I do not understand why there is so much trouble reconnecting the wireless machines without a restart.
    Any help would be appreciated.
    David

    For anyone interested, the problem lay in the ISP's T1 router. They were broadcasting addresses conflicting with the AEBS. Once I changed the AEBS DHCP range from 192.168.1.x. to 10.0.1.x, everything started working fine.
    BTW- since I answered my own question, do I still get points? 8-)

  • AEBS does not recognize Ethernet connected PC

    I have successfully replaced my DLink wireless router with the AirPort Extreme. I have 2 wireless connections to Macs and two Ethernet connections to two other Macs. A PC is attached by Ethernet to the AEBS but it will not connect to the internet through the AEBS. It worked fine on the DLink. What suggestions do you have for me? Thanks in advance.
    Slater.

    figured it out myself. Darn complicated PCs.

  • Is Time Capsule Apple's way of admitting AEBS Disks does not work?

    The support/discussion area is full of posts from many of us who have struggled to find a working solution for our Airport Extreme Base Stations with an attached disk drive; our frustration and patience has been tested as this was a promised technology, advertised to work at sale of the AEBS. Moreover, Apple touted the wireless backup with Time Machine as Leopard got close to shipment, but pulled the technology at the last minute.
    So my question to Apple is, are you now admitting that AEBS + Disk simply does not work, and if so what are you going to do for those of us to bought into a technology promise that has simply failed?
    Any insight, suggestions, patches, or even communication would be a HUGE and welcome change given the misinformation we have endured to date.

    Interesting points from several of you. I am sure if these are global issue I might not have encountered them due to my light usage of AEBS external disk to date. That stems of course from my heavy usage of my Linux server mentioned earlier. I am sure that I might encounter some of them if a moved all my data onto an "Air Disk."
    It sounds however that the problems are more OS X / Air Disk Client issues than AEBS from this point of view. Without actively troubleshooting them it's hard telling. Just a couple thoughts - please ignore if already covered elsewhere:
    1. For the "after a couple days - vanished" issue: Have you also tried another OS other than OS X? (Windows, Linux, Solaris, BSD, anything with a samba client) Are you connecting via Air Disk or SMB? I do not know the internals of Air Disk, but I have been using the samba services of the AEBS.
    2. As for automount, this very much sounds like a problem with the Volume Manager in OS X. Have you sniffed the network to determine if the VM is sending out the request for mount?
    3. Finder not showing unless displayed/accessed via Desktop sounds 100% OS X problem.
    4. 10.4 vs. 10.5 issue again points to OS X.
    5. Access permissions: This is a common issue with NAS storage. Most times it comes back to end user not understanding the capabilities or poor/incomplete documentation of the product again causing misunderstanding. I would guess given the "it just works" mantra that the documentation is somewhat lack luster causing end user confusion.
    6. Time Machine Target: I agree and they should fix this. Especially with another near identical product being released. I expect an firmware update for the AEBS when TC is released.
    I am not trying to be a PITA, just trying to lend my knowledge/experience to the community. I have been working with carrier class networking and storage for nearly a decade. That being said, I don't expect this device to keep pace with those environments or feature sets. This is old news for that space, but cutting edge for the SOHO and consumer space. There will be bumps in the road caused by both the vendor and end user.
    I think the most important things to determine is if "Air Disk uses SMB/Bonj/etc or a proprietary application protocol. Then if the problem is with Air Disk or direct SMB access (or both.) Lastly it needs to be determined if this is a client (OS X / Air Disk) or server (AEBS) problem. These issues can not be solved until one device is pinpointed as the cause for each of these issues. Many of these in fact sound like client issues in OS X and it's supported applications. (Particularly TM sounds at fault since I can not use my SMB shares on my Linux server as a target.) I am willing to help troubleshoot, but only to an extent since we all paid Apple the money not me. =)

  • AEBS Gigabit or not?

    How can I tell if my AEBS has Gigabit or not. Purchased in June 2007.

    Launch AirPort Utility on the left you should see your Extreme
    Select it - and then to the right it will say one of the following:
    AirPort Utility Has found an AirPort Extreme with 802.11n (Gigabit Ethernet) -the one you want.
    AirPort Utility Has found an AirPort Extreme with 802.11n (Fast Ethernet)

  • AEBS Remote USB AirDisk Access

    First off, it was extremely nice to find out that after shelling out £139 for a router, i also had to shell out another £50 for a compatible modem as the AEBS does not support PPPoA connections, and the bog standard modem does not bridge PPPoA to PPPoE so that the AEBS can actually connect.
    Now i have my Draytek Vigor 100 and my AEBS is fully setup.
    The reason i got the AEBS was so that i could plug a usb hub in the back and use it as a home server.
    When im at home on the network, i can access the attached disks without a problem. Read/write speeds i am happy with and its pretty much perfect.
    Now connecting to the external drives remotely is a completely different story. I was under tha impression that they just mount themselves? Ive added them to mount at login etc. but still get nothing.
    I have absolutely no idea what so ever with how to remotely access the disk.
    I have spent hours and hours so far, mainly just establishing that the modem was not right, but now ive hit another problem
    Everything ive owned from Apple so far has been so so easy to setup + use, and this thing was advertised as easy to use. It has been the complete opposite.
    Any help please people?
    I do not have a static IP address and my connection sharing is set to Share a Public IP address - if that helps?

    Finally I've found something that works! I've become so **** frustrated with this whole process. Follow these exact steps:
    If You Have a Time Capsule or an AirPort Extreme Base Station with Shared USB Hard Drive
    If you have either a Time Capsule (which is basically an AirPort Extreme Base Station with a built-in 500 GB or 1 TB hard drive) or an AirPort Extreme Base Station (AEBS) with an attached USB hard drive, you can share out the Time Capsule/AEBS hard drive and make it accessible via the Internet. To do this:
    1. Start the Airport Utility.
    2. Select your Time Capsule or AEBS. Make a note of the IP Address shown on the right -- you will need it later.
    3. Click Manual Setup.
    4. Check your "Connection Sharing" setting under the Internet Tab. The following tutorial is valid if your "Connection Sharing" is to "Share a public IP address", the normal setup for a home network. You will need to have a static IP address, or use a free dynamic DNS service. If you have a different type of "Connection Sharing," you probably don't need a tutorial to set up remote access to your disk; adapt this one as needed.
    5. Click Disks (at the top of the dialog box), and then click File Sharing.
    6. Select (check) the "Enable file sharing" checkbox and the "Share disks over Ethernet WAN port" checkbox. It is strongly recommended that you also set Secure Shared Disks to "With base station password" and Guest Access to "Not allowed"; not making these changes may allow unauthorized users to access your Time Capsule/AEBS hard drive.
    7. Click Airport (at the top of the dialog box), and then click Base Station.
    8. Enter a Base Station Password and verify it in the Verify Password box.
    9. Click Advanced (at the top of the dialog box), and then click Port Mapping.
    10. Click the plus sign to add a new port mapping.
    11. In the Public UDP Port(s) and Public TCP Port(s) boxes, type in a 4-digit port number (e.g., 5678) that you choose. In the Private IP Address box, type the internal IP address of your Time Capsule or AEBS that you wrote down in step 2 (for example, 192.168.0.1). In the Private UDP Port(s) and Private TCP Port(s) boxes, type 548. Click Continue.
    12. In the Description box, type a descriptive name like "Time Capsule File Sharing" or "AEBS File Sharing". Then, click Done.
    13. When you have made all changes, click Update.
    Your Time Capsule/AEBS will restart. Once it does, you are now ready to connect to the Time Capsule/AEBS hard drive via the Internet. To do this when your MBA is away from home:
    1. In the Finder, click Go > Connect to Server.
    2. Type in the correct domain name or external IP address for your network, plus a colon and the port number you specified in step 11. For example, "www.myhomedomain.com:5678" or "123.123.12.123:5678".
    3. Click Connect.
    4. You will be prompted for your user name and password. The user name can be anything you like; the password should be the password for the Time Capsule/AEBS which you specified above.
    5. Click Connect.
    Voilà! You are now connected to your Time Capsule/AEBS hard drive from your MBA. You can access files, copy files back and forth between your MBA and the hard drive, delete files, whatever you want, as long as your MBA remains network-connected. The next time you go to connect, it should go even more quickly (especially if you save your password in your keychain, and if you add your home IP address/domain name to your list of Favorite Servers in the Connect dialog box).
    Note that the Time Capsule/AEBS will appear in the Shared section of your Finder's sidebar as a server, with the Base Station Name of the Time Capsule/AEBS as the server name.

  • Why is the AEBS bottlenecking my ReadyNAS devices leading to bad packets and TCP Retransmits?

    Bad Packets Unrecovered TCP Retransmits TCP Retransmits w ReadyNAS NV NV+ and Airport Extreme Base Station 5th Generation
    I got an Airport Extreme Base Station (AEBS), 5th generation this past November to bring my entire network up to gigE standards and extend my wireless range a bit. I have really liked the AEBS 5th Gen overall since I got it 3 months ago. It was easy to setup and update and things have been noticeably faster. I can also easily take my netbook, laptop, and iPad out to my shop some 80 feet away from my AEBS and still surf rather well wirelessly too. I couldn't do this even with my previous D-Link wireless-n setup.
    In December I picked up an old ReadyNAS NV+ to go along with my old ReadyNAS NV. When I finally started to setup the new network for my business in February, I noticed in the logs that I was getting a large numbers of bad packets, TCP retransmits, and unrecovered TCP retransmits. Previously, I had never had errors of any sort with any older network setups using linksys, dlink and netgear routers during the last 6 years.
    Eventually cables, switches, and routers can go bad which results in the errors I have been getting so I went through the "Troubleshoot My Performance Problem/Check for Network Errors" section of the link below to try and figure out what was causing my problem.
    (http://www.readynas.com/?p=310#Troubleshoot)
    My Initial Setup:
    Airport Extreme Base Station (AEBS):
    - 1 incoming Cat5e from Motorola Surfboard 6120, 
    - 2 Cat5e connections to my wifes work network with her business computer and VOIP phone.
    - 1 Cat 5e interconnecting the AEBS to my wired network on the HP Procurve Switch.
    The AEBS manages addresses via DHCP on my wired network for all of my devices on the HP Procurve 14008G Switch:
    - 1 to NV
    - 1 NV+
    - 1 MacMini 2010
    - 1 MacMini 2005
    - 1 networked Epson R-3000 printer
    1. Simple things first. Since I have always made all my own Cat 5e cable I figured I'd better get some better(?) cabling strait away. I went ordered new Cat 6 and Cat 6a cables to connect the NV, NV+, and my main Mac to the switch and connect the switch to the AEBS. The errors kept coming.
    2. Then I separately connected each NAS unit directly to my computer by setting up the static IP on my computer first. Once I reconnected each ReadyNAS with the computer directly they defaulted to a static IP.  Neither NAS had errors.
    (http://sphardy.com/web/readynas/how-to-direct-connect-to-your-readynas/)
    3. Errors were coming from either a bad Procurve 1400 switch or a bad AEBS. I hooked everything directly to my Airport Extreme and got lots of errors.
    4. I decided to check the switch also. I altered each ReadyNAS's default static IP to one of my choosing individually. Then I hooked both ReadyNAS units to my HP Procurve 1400 switch. I hooked the switch directly to my computer and got no errors from either NAS. I continue to get no errors the next day.
    5. When I first ran my tests I had Jumbo Frames turned Off. Currently, Jumbo Frames are On and there are still no errors and seems to be no slowness either.
    Conclusion:
    The Airport Extreme is the bottleneck causing the errors in my network.
    Perhaps there is something I can alter which will rid me of the errors, but this type of error makes the AE seem to be pretty shoddy. A newer state-of-the-art router should not be bottlenecking my rather archaic slow network devices. Apparently, the 4th Gen AEBS's couldn't do Jumbo Frames, but this current model is supposed to, but I see no setting for changing the MTU.
    Questions:
    What could be causing the bottleneck?
    Do I have a bad router?
    How could I analyze this problem?
    Has anyone else had similar issues and if so how were they resolved?
    Current Setup:
    All of my computers and NAS devices are hooked to my Procurve Switch each with its own Static IP.
    The switch is working flawlessly with no Errors.
    The network printer is now wireless and  connected via the AEBS.
    I am using wireless-n to connect to internet via the AEBS on my main machine.
    I am sharing the internet connection with the other Mac Mini on the switch and any other machine I plug into the switch (not ideal).
    Problem is:
    I am not a systems administrator and don't really want to tinker with setting up Static IP's for the machines I hook and unhook to the switch.
    I want the AEBS to manage addresses via DHCP so everything accessing my router will mindlessly be able to access all things on my network.
    Can the AEBS be made to not produce errors or do I just have a lemon.

    Hi Bob,
    That's the strange thing. When I had both GHz channels working on one SSID, once in a while my iMAC would pick the 5 GHz channel (44 seems the best for me). I always use channel 1 for 2.4 GHz because I get the fastest speeds with it.
    When the iMac would pick 5 GHz, the slowdown was very obvious. As I explained in my (long) first post, I immediately felt the difference. Now the $50K question - since the 5 GHz channel at that point was stronger than the 2.4 GHz one, why wasn't the speed faster? Why was it so slow compared to 2.4 GHz? That's what rattling my brain. If the 5 GHz signal's strong enough to get picked by my iMac, then why isn't there a commensurate speed increase? There must be something else going on here besides signal strength. If the 5 GHz spec says that I must have full strength to get 5 GHz speeds, then that makes sense. But I think it doesn't, that's why I believe I have a configuration problem somewhere, or a faulty AEBS.
    I might add that my firmware's up-to-date in the AEBS and AX, and Airport Utility too.
    I think heading to 4Runner's camp - even with high signal strength (and I would consider 3 of 4 bars high), the 5 GHz speeds aren't showing themselves.
    Here's some snap's of my AEBX's setup:
    I think my configuration's fine, although I've tried so many different options, I'm a little confused, but I know that changing the Multicast Rate doesn't have any noticeable effect on the speed. I also have "Use Wide Channels" checked, but as I said, the 5 GHz band is awfully slow for using both channels. I have set "N" only, so no "G" clients to slow it down.
    Mind boggling!

  • USB printer recognized by A.Express but not by new A. Extreme (gigabit)

    My Canon IP4300 was automatically recognized and worked without any problems with an old Airport Express. However, with my new AEBS (gigabit ports), the printer is no longer recognized, I don't see it in the printers tab (says none).
    Surprisingly, when a Windows PC connects to the new AEBS with the printer connected to the AEBS USB port (but not recognized in the Airport Utility), the windows PC finds the printer and can connect to it. So physically, the connection can be made, thus it has to be a problem with the Airport utility?
    Quite strange that AEBS printer 'plug and play' works better with Windows PC than with Apple computers. Other people experiencing the same problem?

    Nevermind. The Epson R220 works fine on the AEBS. Wrong USB cable was plugged into the AEBS.

  • Time Capsule Not Recognized by PC

    I've replaced my old router with a new Time Capsule (TC).  The router is connected to a Motorola SB6120 cable modem for internet access via my cable TV company.  Set up of the TC seemed to go smoothly, the network still has the same SSID and WEP security code as it did before, picked up automagically from the old router during the set up.  My wireless devices are a Macbook Pro (that I used to do the setup), an iMac, an iPad2, two iPhone4s (plural iPhones, not to be confused with the new iPhone4S), an HP Photosmart Premium All-in-One printer, and the problem - a Dell Inspiron N5010 PC running Windows 7 Home Premium SP1.
    After completing the set up I had to re-enter the WEP security code on each Apple device and the printer when they first tried to connect to the network, even though the code had not changed, but other than that one-time minor inconvenience they all connect fine.*
    The problem is with the Dell PC.  It can 'see' the network - the SSID shows in the list of available networks - and it sees excellent signal strength, but it connects with only "Limited Access".  Neither disconnecting from the network and reconnecting, nor disabling and re-enabling the network card, changes that.  Initially, running the Network Troubleshooting routine produced the following result:
    - The 1st (and only) stopping point was a request to confirm the WEP security code.  The code shown was correct, but I re-entered it and continued.
    - The troubleshooting routine then went through a series of other checks without stopping for user input or confirmation.
    - The troubleshooting routine ended by showing 2 Problems Found:
    1) the security code confirmation
    2) 'IP problem' (not the exact wording, but something about an IP address problem).
    After doing some research on the internet, I downloaded and installed Airport Utility on the Dell PC and tried to run it.  On launching Airport Utility I got this message on the screen, "Unable to find any Airport wireless device".
    Again I tried to run the Windows Network Troubleshooting routine.  Again the 1st item is to confirm the WEP security code after which the routine runs to completion without stopping.  Now there are 2 different problems found:
    1) Problem with wireless adapter of access point - Detected - triangle with ! inside
    2) Windows cannot connect to [SSID network name] - Fixed - circle with checkmark inside
    Any suggestions for what might be going on?  What hardware or settings I ought to check and report back on?
    Thanks in advance for and suggestions anyone can offer.
    * Aside: my iMac shows that the network security type is WPA2, not WEP, but it connects just fine anyway!

    Thanks again for your suggestions and instructions, now wish me luck!
    Yes, I do!!
    Never mind - Google is my friend!
    Sure is.
    2. how do I determine which of the two networks to use?
    Easy.. pick the best one. ie best signal strength and speed. 5ghz is better speed and poor range. 2.4ghz the opposite. At any point pick the best. Best signal / speed. Close to the router, it will be 5ghz.. further away 2.4ghz will be better. Try both.. it is a 10sec effort.
    The reason to do this manually is the TC is designed to swap channels automatically when there is interference.. It is also so the client on the computer (mac only) will auto swap between 2.4ghz and 5ghz for whichever is faster. So you have auto channels on top of auto band.. and even the Mac gets confused .. the PC has no idea.
    3. What channel should I set for the 5 ghz network?  (If I recall correctly, the TC is presently using channel 6 - does that apply to both networks?)
    No.. 2.4ghz uses channels 1-11 in USA.. 1-13 in Europe Australia..
    There are 3 non-overlapping channels, 1, 6, 11.. pick one and try it. Better still on the PC download the application inssider.. and you will see which channels are in use.. usually all of them if you live in a city in USA or moderately weathly country. Pick the channel with the lowest signal and use that. Since only those three channels are non-overlapping picking channel 9 for instance because nobody is using it, is pointless. Wireless on both channel 6 and channel 11 will then interfere with it. Use the lowest signal channel, out of the three, 1, 6, 11. (13 in Europe 14 in Japan).
    5ghz has a large range of channels, beginning from 36 up to 151 (at least in Australia) .. your country if different will vary. Use the lower channels if possible.. but there is not much interference yet on 5ghz. Usually you can just use 40 which meets lower end equipment. eg early versions of the AEBS and TC do not offer a large range of channels.
    4. Can I leave the security as WEP until I get everything working?  I understand that WPA2 is better
    WEP is equal to a strong door on a tent.. it is next to useless. It keeps out people who are not trying to get in. And offers 1min of difficulty to the guy with the knife. Use no security to do setup.. then use WPA2.. if something doesn't work with wpa2 you can use wpa at a pinch. Throw away any item not compliant with at least WPA. WEP is not a rated security for N wireless.. it could well not work or fall back to G wireless. So for testing just turn off security.. when it is working jump straight to wpa2.
    5. Why turn on the Guest account?  I don't see that it's used in the subsequent steps.
    If you ever want to write to or read the hard disk from PC.. you will have issues with security on Windows not matching the TC.. You do not need to use guest account (this is hard disk access not wireless btw).. if you never want to use hard disk. I added it for completeness. You can also fight your way through the difference in security between a Mac and a PC with win7 in particular.. loads of fun. If the disk is going to be on a private network and the TC has to be really, then use guest network. If anyone wants to break in it is no more difficult than holding down the reset for 1sec and it will reset all the passwords. So what more security do you need. Guest is fine.
    6. Will do.  I do have a workgroup specified on the 3 computers, but it's one that I created and it's not named <WORKGROUP>
    SMB uses workgroup name.. what name you use is irrelevant.. again this is for hard disk access. If you just want internet it is not necessary to worry about. Put into the workgroup name the name of YOUR workgroup. But it makes it appear in the windows networking as a network drive and that can be helpful.
    Somewhere on the Dell PC I've seen that both ipv6 and ipv4 show as not used, don't recall where I saw it though, and there did not appear to be any way to change it.
    You have internet connection it MUST use TCP/IP which has to be either ipv4 or ipv6 or both. That is how the internet works.. you cannot have neither. You change the settings in TCP/IP properties box associated with the wireless card.. go to device manager and the wireless device. Click on it and go to properties.. see TCP/IP and go the advanced.
    You need to learn to use the networking tools. 
    The key tool is ping.. that allows you to see if a device is available and responding on the network.
    Command window is same as terminal on the Mac.. (well near enough). You do low level commands.. both will do ping.
    You can also get all the settings in the network.
    Simple one is ipconfig in windows.. ifconfig in the mac.. that will show the IP address of all the network clients. In windows there is a full description if you do ipconfig /all
    These commands are very important to use and learn about.

  • Photoshop CC (64 bit): Entry Point not found

    Hi,
    Just updated the Photoshop CC (64 bit) and after update the whole thing does not work anymore. When you try to start Photoshop CC you get an ugly message stating:
    Photoshop.exe - Entry Point Not Found
    The procedure entry point
    ?ProposeSearchBounds@StructuralImageEditing@@YA?AVBox@1@AEB ...
    could not be located in the dynamic link library D:\Program Files\Adobe\Adobe Photoshop CC (64bit)\Photoshop.exe
    Any ideas? I really need the P CC so any help is valuable! The platform is Windows 8 / 64 bit and the P CC used to work..
    Update:
    The 32-bit version of P CC works. So it is only the 64 bit version that does not start.
    Message was edited by: Jari.O

    @ Talha1997,
    Please follow the below mentioned steps let me know if they work:
    1. Uninstall current Ps CC app, If there are any issues with CC uninstall then run the Cleaner tool to remove Ps CC :http://www.adobe.com/support/contact/cscleanertool.html .
    2. Restart your system
    2. Install Ps CC app from Creative Cloud
    3. Do not launch Ps
    4. Update to 14.1.2 via the Creative Cloud desktop application
    5. Once the updates are successfully applied, Launch Ps CC to verify.
    If it does not work please let me know, I would try to resolve it over a connect session.
    Regards,
    Ashutosh

  • Port Mapping Not Working...at all!

    I've been tyring to get port mapping working correctly since I got the AEBS a few months ago. I've scoured all over these forums and the entire internet and found not a single suitable answer. I have my macbook pro setup up wirelessly all works fine except port mapping.
    My macbook is setup up manually with a static IP of 10.0.1.2 and lets say i want to map the port 41952. In the port mapping setup assistant on the base station I leave the service setting on "choose a service", public UDP 41952, public TCP 41952, IP address 10.0.1.2, private UDP and TCP 41952. Then I update and router resets... then I use the network utility to check the ports and they're not showing as open, I've used various internet websites as well and the port comes up closed. What on earth am I not doing? Someone please help! or let me know if you are having the problem as well.
    Thank you for ANY help.

    You are not performing a valid test.
    No, Cable modem plugged into WAN port, the computer i'm trying to open ports on is using a wifi connection with the aebs.
    You can not test the AEBS to see if the ports are open from the LAN side of the AEBS. You must be on the internet (WAN) side of the AEBS to test to see if the port is open on the AEBS.
    ...the computer i'm trying to open ports on is using a wifi connection with the aebs.
    You aren't opening ports on the computer, you are opening ports on the AEBS.

  • How does the security model work for external USB disks attached to an AEBS

    I've attached a USB disk to my AEBS after partitioning it first on my MBP using Disk Utility. I created a single partition with a GUID partition table covering the entire disk. Next I deselected the "Ignore ownership on this volume" checkmark and assigned myself and my wife read/write access, my group read access, and the rest no access. Next, I hooked it up to the AEBS and created some test files. I noticed in Terminal that the files I created all had rwx access for user, group and others. Trying to chmod that into something less open, like rwx for me, rx for the group and nothing for others didn't work. Also I noticed that when I was logged in the files I had created had my name as the owner, but when my wife logged in, those same files were owned by my wife.
    What is happening here ? Who is the actual owner of the files on the external USB disk on my AEBS, and what are the real access rights (as they seem to depend on the actual user). On my AEBS I've setup "File sharing", "With accounts" and created accounts for both me and my wife, as well as disabled guest account access.
    I get the impression that the owner and access rights seem to depend on the actual user connected to the AEBS, but I'm not sure.
    Can anybody please enlighten me on the subject of AEBS access rights/ownership for USB disks ?
    With kind regards,
    Aloy

    All that I can provide is what has worked for me for years.
    The Time Capsule is setup as the router for the network, connected to a simple Zoom 5431J cable modem.
    Static Internet IP connection from the cable provider is 12.34.567.89
    By default, the Time Capsule is at 10.0.1.1 on the local network
    Port Mapping setup for the Time Capsule is......
    Public UDP Port 8884
    Public TCP Ports 8884
    Private IP 10.0.1.1
    Private UDP 548
    Private TCP 548
    The hard drive on the Time Capsule is accessed from a remote location at afp://12.34.567.89:8884
    The AirPort Extreme is connected by Ethernet to the Time Capsule and is it setup to operate in Bridge Mode
    The AirPort Extreme always receives a reserved local IP address of 10.0.1.2 from the Time Capsule
    The Port Mapping setup (on the Time Capsule) looks like this for the AirPort Extreme.......
    Public UDP Port 8888
    Public TCP Port 8888
    Private IP  10.0.1.2
    Private UDP 548
    Private TCP 548
    The USB hard drive connected to the AirPort Extreme is accessed from a remote location at afp://12.34.567.89:8888
    If you are still having difficulty, I would delete all of Port Mapping settings on the Time Capsule and Update the Time Capsule. Then, go back and setup the Port Mapping for the Time Capsule, check that to make sure that it is working, then setup the Port Mapping settings on the Time Capsule for the AirPort Extreme.

  • Airport works for ibook but not desktop?

    Hi All,
    I've got a G5 iBook and a G4 iMac. We've used a DSL modem to connect to the internet with no problems. Recently a friend gave me an airport extreme he no longer used. I've managed to get the iBook working on it, but the desktop doesn't find the server, even when connected with an ethernet cable. No, the desktop does not have an airport card. I'm a bit frustrated, would love some advice, direction, support, insults. Anything at this point.
    Cheers!
    Jenn
    iMac G4 Mac OS X (10.3.9)
    iMac G4   Mac OS X (10.3.9)  

    Slip o' the fingers the iBook is also a G4. Proofreading, anyone?
    Definitely got the LAN connected between the desktop and the AEBS properly.
    However on the WAN port- if I send the WAN between the DSL and the AEBS, then there is no input into the DSL from the phone service. In other words, there is one LAN and one WAN input on both the DSL and AEBS. Unless I can just pop a WAN cord into the LAN site on the DSL, and connect it to the AEBS? I'm not as edumacated on networking as I should be. Plus I'm disgusting myself with the use of acronyms, BTW. Ha.
    Cheers,
    JC
    iMac G4 Mac OS X (10.3.9)

Maybe you are looking for