Leopard + iChat + Time Capsule Port Forward

Hi,
Here are my settings
OS: Leopard
Modem: Motorola 2210-02
Router: Time Capsule
Macbook
I am trying to use video ichat with my girlfriend in Canada but I can't get it to work. (audio works)
Currently I am using the modem as a Bridge and I forwarded the ports on Time Capsule according to the guide for AEBS (http://portforward.com/networking/static-Mac10.4.htm). However, it's still not working.
Is the problem coming from the port mapping? => in the private ip field should i put the router or the macbook's ip.
Does it make a difference which setting i use as my DHCP beginning address? 10.1.0 vs 192.168.1
Should my dhcp reservations for my macbook (and other laptop) be within or outside the dhcp beginning and end address?
Sincerely,
Adama

It should work just setting it to Share An IP in the drop down.
I am not sure if the set up is exactly the same as a Base Station but you should have a pane like this
http://flickr.com/photos/90943061@N00/2043616510/
10:32 PM Wednesday; March 19, 2008

Similar Messages

  • Time Capsule: Port Forwarding Issue and DHCP with Westell 6100g Modem

    Ok two issues as of right now, but more down the road i think... Anyways, number one, i would like to be able to backup my computer using time machine and my time capsule.. Right now it works properly when inside the local network, was wondering if there was a way to backup when outside the network... i travel a lot and always have my macbook pro with me.. Also, i have a USB hard drive connected to the usb port on back of time capsule but its not showing up anywhere... is that only for printers??? that's not such a big deal, but would be nice to have access to that hard drive from multiple computers... OK so part two of my issues is, i have a WESTELL 6100g modem for DSL verizon service, which is crappy, but that's besides the point, it is a modem/router, so i have the time capsule connected directly to that westell.. the westell only has one Ethernet port, so that's wired to time capsule and then my computers are connected wirelessly and wired through the capsule. It seems that the westell is distributing the IP's and is controlling the port forwarding and what not.. I have tried a few things to give control to the time capsule but that didnt work.. i followed these directions on the web page http://www.dslreports.com/faq/vz/4._Hardware#13600 but it didnt work properly, i couldn't log onto the web at all.. Maybe im doing something wrong.... Anyways, what i really want to do is control everything that the westell is controlling right now with the time capsule... i want to give out IP's and also control port forwarding with the capsule.. Any way of getting that accomplished would be AWESOME... I'm somewhat intelligent when it comes to computers so i should understand everything you are talking about... please help!!!

    wattabing wrote:
    Ok two issues as of right now, but more down the road i think... Anyways, number one, i would like to be able to backup my computer using time machine and my time capsule.. Right now it works properly when inside the local network, was wondering if there was a way to backup when outside the network... i travel a lot and always have my macbook pro with me.
    If you have Back to my Mac (available online service from Apple's MobileMe), then you can perform the following actions with your Time Capsule remotely,
    1. Remote disk access to both the Time Capsule disk and a compatible disk connected via the Time Capsule's USB ports.
    2. Remote configuration.
    Also, i have a USB hard drive connected to the usb port on back of time capsule but its not showing up anywhere... is that only for printers???
    Printer, hub, or compatible disk.
    http://support.apple.com/kb/HT2421
    Anyway, it could be a setup issue for you, assuming you have Back to my Mac (MobileMe) then the procedure for Time Capsule services is shown in the following Apple support kb
    http://support.apple.com/kb/HT3486
    and for USB disk please see the following Apple support kb
    http://support.apple.com/kb/ht2426

  • Time capsule port forwarding problem.

    I'm trying to portforward minecraft the game to my LX195 hp mediasmart home server but everytime i do 25565 FOR all of the public and private UDP and TCP's and update it with my home servers static ip it doesn't work i always use canyouseeme.org to check if it's open and 25565 (the port) is always closed or connection refused
    Please help!
    Thanks

    1. Find your computer's IP address. In system preferences, click on "Network.: Then click on either Ethernet or Airport (depending on how you're connected to your network). Your IP address will be listed on the right and will likely be something like 10.0.1.3.
    2. Open Airport Utility, select your time capsule and select "Manual Setup." Click on the "Advanced" button, then on the "Port Mapping" tab. Click the + to make a new port map.
    3. Enter the port mapping information as followed:
    Service: Choose a Service (This doesn't matter)
    Public UDP Ports: 6890-6900
    Public TCP Ports: 6890-6900
    Private IP Address: 10.0.1.3 (This must be your IP address that you found in step 1)
    Private UDP Ports: 6890-6900
    Private TCP Ports: 6890-6900
    4. Click "Continue." Type in a description such as "MSN" and then click "Done." The other fields do not mater. Click "Update" at the bottom of airport utility to update these new settings.
    Once your airport device has restarted, the ports should then be forwarded.
    If this doesn't work properly, it is possible that your time capsule is connected to the internet through another router or router/modem. You must turn off the routing functions on either of the routers.
    You can also try enabling the default host in airport utility. This should forward all ports to a computer's IP address. Find it in Airport Utility / Manual Setup / Internet / NAT. Enter your computer's IP address in the "Enable Default Host At:" box and update.

  • Time Capsule port mapping is broken for L2TP Servers behind NAT config.

    I'm hoping that someone here can refute the below bug assertion... am I missing something?
    There is a bug with Apple’s Time Capsule/Airport Express Base Station (TC/AEBS) rendering L2TP servers on the LAN unusable:
    When TC/AEBS is used as a router providing NAT services to the LAN, it will NOT under any circumstance provide port mapping services for 500/UDP, 1701/UDP, & 4500/UDP making L2TP VPN servers on the LAN side of TC/AEBS are unreachable from the WAN/Internet side.
    *The conditions for my tests*:
    3 different external networks used for all tests: MacBook Air at home on TWC network, the Air on AT&T mobile dongle, & CentOS server at ThePlanet.
    MobileMe configuration was removed from both the TC/AEBS & Snow Leopard Server on the LAN.
    I used port 501 for my control-test; spot checks of other ports worked as well, though they were all < 10000.
    Simultaneous local and server monitoring of port traffic using
    tcpdump -vvv -i en0 -s 0 -X port 500 or port 1701 or port 4500 or port 501
    The TC/AEBS was configured to forward UDP ports 501, 500, 1701, & 4500 received from the WAN interface to the Snow Leopard Server on the LAN.
    The port forwarding was accomplished both 1) manually via AirPort Utility, and 2) automatically via Snow Leopard Server’s Server Preferences utility. Each was tested separately.
    *The tests*:
    Netcat with the following commands, in turn, on the server:
    nc -l -u 501
    nc -l -u 500
    nc -l -u 1700
    nc -l -u 4500
    which causes traffic to the udp port specified to be dumped to std out. Provides a confirmation of the tcpdump output.
    On the various external networks, nc -u WAN-address-of-AEBS.example.com 501 to send UDP packets on port 501. The output of the nc -l 501 command and the server-run tcpdump confirmed that packets left the client and made it to the server as expected. Remember, 501 is the control-test.
    For each test permutation on ports 500, 1700, & 4500, no packets made it to the server.
    Based on some web research, I’m not the only one to have found trouble with this configuration, but I haven’t been able to find any conclusive tests.
    I’ve filed a bug with Apple (#7720101) and encourage you to do the same.
    Message was edited by: WebMarc

    Confirmed here. This only seems to be a problem with Airport 7.5.x firmware though - I find the older TCs running 7.4.2 work as expected even with BTMM / MobileMe services active.
    I'm so glad you posted this - I haven't found it mentioned anywhere else and was beginning to feel very alone with this problem. I also found that having two TC 7.5s in the mix - one at both ends - also results in no response to SSH or Remote Desktop ports.

  • Lion to Snow Leopard using Time Capsule

    Hello folks. Despite all the perks of Lion, I have too many programs that arn't compatible with Lion. I don't think the downgrade from Lion to Snow Leopard was addressed IF also using Time Capsule in other threads. I'm no expert so I wanted to get details instead of piecing together random tibbits. But if I happen to miss that thread, please let me know. Thanks!

    Hello folks. Despite all the perks of Lion, I have too many programs that arn't compatible with Lion. I don't think the downgrade from Lion to Snow Leopard was addressed IF also using Time Capsule in other threads. I'm no expert so I wanted to get details instead of piecing together random tibbits. But if I happen to miss that thread, please let me know. Thanks!

  • Ipod dock connected to my usb time capsule port?

    Is it possible to sync my ipod connecting it to the usb port of my time capsule?
    Will itunes see my ipod this way? or just and external HD?
    I'm actually out of usb ports, so it would be great if i can do this.
    Thanks!

    I would recommend a USB hub instead. I don't know if it works but if it does it will be painfully slow for what you are doing.

  • Time Capsule + Ports

    When I try to open any ports my entire network crashes and I have to Factory Reset the Time Capsule to get back online...

    I suggest you use NAT-Port Mapping Protocol on your TIme Capsule. NAT-PMP will dynamically open ports required for any application trying to get to the Internet. It is similar to the PC world use of UPnP - Universal Plug and Play.

  • Airport Time Capsle port forwarding

    I am running ARD on Mountain Lion. I recently purchased the new 3TB Airport TimeCapsule. I am trying to configure it so that I can use ARD from work to remote into my MacPro at home, I have setup port mapping but it will not connect. What am I doing wrong?

    For the port mapping.. See Tessarex documents and check according to the airport utility you run.
    https://discussions.apple.com/community/wireless/airport?view=documents
    Failure to connect can be caused by a huge number of things.
    Have you tried firstly running ARD on the local network?
    Next, what is the setup of the network.. is the TC main router and only router?
    How are you getting the public IP of the TC?
    Have you tried BTMM and iCloud and check if they work?
    Is your work setup behind a firewall? Are you actually able to use ARD using say a 3G wireless connection via your phone?

  • Time capsule ftp port forwarding

    Hi.
    Just got a new time capsule and have discovered that the connection speed to my ftp server is MUCH slower.
    I've tried playing around with port forwarding but haven't managed to get it sorted out.
    I did discover during my attempts that switching the TC over to bridge mode fixed everything. Didn't want that security setup though!
    Current setup is modem (bridge mode) > ethernet > time capsule (wirelessly routing via nat-dhcp)
    I'm not quite sure what i'm doing with the port forwarding settings...i've tried changing the dhcp mode to manual on my mac
    i've also added various ports (21,22,80, 115) to the time capsules' port settings
    according to http://www.yougetsignal.com the only open port is 21
    any tips?? very grateful!

    You need to look carefully at how ftp gets through NAT.. and if the ftp client can open ports itself .. which way are you going, out or in?
    Is the client active or passive ftp? You think ftp is this simple protocol but there are variations and some handle NAT better than others.. it is also going to need specific ports opened higher up the range.
    Some clients allow you to dictate the port and others open ports at random.
    See the info here.
    http://slacksite.com/other/ftp.html

  • Port forwarding for Time Capsule

    Could someone be so kind as to forward instructions for portforwarding ports 80, 443,4125, and 554 on my time capsule?
    Im a novice user at best but I want to learn to set up security cameras for my small bussiness. Im useing an air link101 IP camera system.
    Any help would be great.

    Port forwarding on a Time Capsule is done in AirPort Utility's Advanced panel, Port Mapping tab.  You'll also need to use the Internet panel, DHCP tab, to reserve a fixed IP address to the camera so that the Time Capsule can forward to a definite address.

  • Making Snow Leopard Server services accessible through Time Capsule

    Sorry, this will be a fairly long explanation. I think this is the right forum but the question kind of spans several component elements.
    During the setup of Snow Leopard Server I let it configure the Time Capsule for services that it is providing, which I want to make available to both the local network and to computers coming in from the Internet. However, there seem to be some conflicts between Time Capsule ports and Snow Leopard ones.
    First my set-up: I have Verizon FIOS and have set up my Actiontech Router into bridge mode to the Time Capsule so that the Time Capsule grabs the public IP address. The Snow Leopard Server has a dedicated private IP from the Time Capsule through the DHCP reservation. I have a dynamic DNS setup which consistently points to the public IP address assigned to the Time Capsule. After starting services on Snow Leopard Server, I can see the port mappings created on the Time Capsule by the server allocated to the server's dedicated private IP address. However, the File Sharing (AFP, SMB) entry can't be enabled because the ports used for those services conflict with the ports opened by the Time Capsule to enable backups from client Time Machines (TCP Ports 548, 139). Therefore, any external access to those ports are going to the Time Capsule and not routed to the Snow Leopard Server.
    Two questions:
    1. Should I map the DNS hostname to the Time Capsule on the Hostnames screen on AirPort utility? While this will enable remote access to the Time Capsule (so that if my client computers are outside coming from the Internet), will this mess up remote access to the Snow Leopard Server?
    2. How do I get around the problem of the port conflicts between what Time Machine needs to get to the Time Capsule for backups versus enabling the ports for AFP and SMB on the server?

    I actually found an Apple support tip and am posting it here to answer the question:
    http://support.apple.com/kb/TS2963
    Bottom line: you can't have both devices doing file sharing unless you set up VPN access.

  • Time Capsule and Leopard - wireless dropouts

    I bought a new 24" iMac (Leopard) and Time Capsule 8 weeks ago, and set up a wireless network which also included my old 17" G4 iMac (OSX 10.3.9) with Airport Extreme card.
    From the very start I was having annoying, small problems with wireless dropouts on my Leopard iMac - sometimes it could find the TC, sometimes it couldn't. I decided that for my first Time Machine backup I should move the TC closer to my Leopard machine - it appeared to be an improvement, so I left it closer for a week or so. I then decided to move TC back to it's original position and had good connection for another month or so.
    This week, my wireless connection (Leopard to TC) has been steadily deteriorating until tonight I have been unable to get any wireless connection at all.
    I haven't been able to successfully use Time Machine for weeks.
    The whole time I have had excellent, constant, trouble free connection between my old iMac and TC.
    I've looked at forums and tried a few suggested fixes with no success - it's hard to describe how frustrating this is (I'm typing this on my old machine) as I have a number of online musical projects in progress which require daily, often hourly exchange of files.
    Surely Apple must have a fix for this!
    The problem is clearly not the TC, but more likely Leopard. I spent a fortune upgrading and am now completely dissatisfied after being a happy Mac user for many years.
    Does anyone have a surefire remedy for this? I really can't believe that there isn't one available.
    Rant over,
    HH

    It's likely your wireless network. Check this thread on cordless phones and TC.
    http://discussions.apple.com/thread.jspa?threadID=1679559&tstart=0
    Welcome to Apple Discussions!

  • Set up VNC on time capsule behind uverse?

    Please Help....
    I want to have the ability to VNC into my machine remotely. Along with a handful of other things I use, plex, back to my mac, remote access to the time capsule HDD,  ect. I had this all setup before perfectly with Time Warner using a dyndns.com account and my time capsule (worked flawlessly)
    Unfortunately I am stuck using Uverse in my new apartment with a 2wire router/modem as it's my only ISP option.
    I have a time capsule plugged into the 2wire (3801HVG) and the only way I can get VNC to work (port 5900) is to put my machine into DMZ mode and the time capsule in bride mode. I'm just afraid that this will be not very secure even with the software firewall turned on in my system prefs. With this setup my machine has the same public IP as the 2wire– essentially does not have a private ip. -"hello world here is my iMac!"
    Although with this setup I went to canyouseeme.com and after testing various random ports it could only see me on 5900. Which is exactly what I want but I'm still worried about my iMac's ip being the same as my public ip.
    I tried to port forward just the port I want to use in the settings for the 2wire (gateway.2wire.net) but it does not connect. Only if I put the machine in DMZ mode does it work.
    I've tried so many different setups and spent hours digging through the interwebs and I just cannot seem to make it happen.
    things I've tried / info you should know:
    1. disabling routing all together on the 2wire (not possible with my model I found out)
    2. tried separately putting both devices in DMZ mode (my machine, time capsule)
    3. forwarding ports on 2wire and time capsule
    4. time capsule in bridge mode, sharing a public ip, distributing a range of ip's
    5. I also have the wireless function of the 2wire router off
    6. I have tv through them as well
    7. I put in my own DNS servers from opendns.com
    8. called ATT and they attempted to open the ports for me which worked at first then I realized they put my machine in DMZ mode, then they transferred me to another company who wanted to charge me $150 for a week of support. (yuck)
    Is there anyone out there that could point me in the right direction to the best way to set this up? Or is it safe having my public ip the same as my iMacs?
    Thanks in advance.
    -Eric

    BUMP!
    Hello! Anyone out there have authoritative info on getting Back to My Mac working without opening DMZ using uverse 2wire router? Is opening DMZ  very risky even if you keep   appropriate firewalls  in place?
    I agree Uverse were wanks for this: the tech who installed my system said it would work just as it was w prior service (ie BTMM working perfectly). Now, I discover I can't remotely login, and ATT tries to farm me off to some $150 tech service for what they should have done @ the outset.

  • Mac Mini & Time Capsule as fileservers on the same network

    My Mac Mini is currently functioning as an AFP/SMB fileserver, and I have my Time Capsule forward ports 139 & 548 to the Mini to share publicly. This is working just fine and dandy, but I'm unable to use my Time Capsule as a backup drive. The error I get when I try to enable file sharing on my Time Capsule is:
    "Enabling “Enable file sharing” conflicts with one of your port mappings. The port mapping has been disabled. Update its public port to continue using it."
    But changing the port of my Mini file sharing breaks the AFP/SMB connections. Does anyone know how to configure the Time Capsule to forward ports to my Mini for file sharing, yet still allow file sharing internally for Time Machine backups? (Even better: allow my Mini Server to use the Time Capsule as a share point...)
    Thanks!

    Sorry, I'm a bit confused since you say in one sentence that:
    ....I am thinking about adding a new airport extreme....
    Yet, you mention AirPort Express in the rest of your post as a product that you are thinking about adding to the network.
    But first.....
    If you configured your current AirPort Express to "extend a wireless network", but did not notice any improvement in wireless coverage, then you may have likely forgotten that a setting on the Time Capsule must also be enabled to "Allow this network to be extended".
    So, if you did not also enable that option on the Time Capsule, it is true that you would not notice any improvement on the AirPort Express as far as extending the wireless network...because the Time Capsule settings would not allow the network to be extended.
    Is it still possible to use the time capsule as a backup disc for time machine still if I add the airport express?
    Yes. But before you add any new products, you might want to revisit the idea of using your current AirPort Express to extend....keeping in mind that both the Time Capsule and the AirPort Express must be configured correctly to allow the extension to occur.
    Post back if you need more details on this.

  • Time Capsule firewall allows broadcast traffic

    It appears that Time Capsule will forward broadcast traffic from the LAN side to WAN and allow responses back. I would have thought that when the Router Mode was set to "DHCP and NAT" that this wouldn't happen. It seems like this might be a security flaw.
    Here's my setup, and why I believe this is the case:
    Comcast Xfinity service -> Motorola SB6121 -> Time Capsule (latest generation 7.6.1 software) -> Netgear GS116 -> home network with airport express and various hard-wired and WiFi devices.
    The SB6121 cable modem is wired direclty to the WAN port on the Time Capsule. And then the first LAN port on the Time Capusule is wired direclty the Netgear switch. And then everything else is wired directly to the Netgear switch. The Time Capsule's DHCP server is set to hand out addresses in the 172.16.0.2 to 172.16.0.200 range and so everything in my home network should be getting addresses in that range.
    The SB6121 is not a gateway or router - its just a modem, but does still have a weird little DHCP server that is supposedly only active when the cable service is dead, but in practice (at least for me) seems to always be on. And there's no way to turn it off, at least from my end - perhaps Comcast could, but that's a black hole. This weird little DHCP server is hard-wired to hand out addresses between 192.168.100.11 and 192.168.100.42 and there's no way to configure it differently.
    What I see though I (which makes me think there is a security flaw in the Time Capsule firewall) is that DHCP requests from my home network are sometimes answered by the SB6121's DHCP server instead of the Time Capsule's. I say "sometimes" because most of my Apple equipment (laptops, iPhones, iPads and a Mac Mini) get configured with 172.16.0.X addresses. But most non-Apple equipment is getting 192.168.100.X addresses - this includes a Denon AV reciever and Comcast cable box. But I also have an Airport Express (latest version, 7.6.2 software) - its Router Mode is set to "Off (Bridge Mode)", but if its Internet -> Connect Using: is set to DHCP it also gets a 192.168 address.
    I thought maybe it was just the hard-wired devices getting the 192.168 addresses, but they're not. The Mac Mini is hardwired and gets the right address range. And then I thought that all WiFi devices were getting 172.16 addresses, but they're not. I have a "Nest" thermostat that connects to the WiFi and gets a 192.168 address.
    Obviously there are several problems here - having multiple DHCP servers on a network is a recipe for disaster. But it seems to me that the Time Capusule is mis-behaving. The weird little DHCP server on the cable modem on the WAN side of the Time Capsule shouldn't be accessible from my home network. The Time Capsule shouldn't be passing broadcast DHCPDiscover packets from the LAN side through to the WAN side.
    I've been all through the Time Capsule settings and don't see a way to further lock down the WAN-LAN connection. I suppose I could get a managed switch or "real" firewall to stick between the cable modem and the Time Capsule and use it to block traffic, but I shouldn't have to. And I suppose I could ask Comcast to disable the DHCP server on the cable modem, but I don't have the fortitue to sit on hold for hours trying to explain it to them. Or I suppose I could get a different cable modem that doesn't have the silly DHCP server, and maybe that's the ultimate answer, but I still think the Time Capsule has a flaw.
    I got the SB6121 plus Time Capsule combination specifically because I didn't want fidgety stuff to deal with. I could have gotten a router supporting DD-WRT if I wanted to play network engineer at home, but I do that at work and just wanted something I didn't have to debug or think about.
    Anybody in a similar situation or have suggestions?
    If you got this far, thanks for listening.
    -dave.
    (Oh yeah, I swapped the Time Capsule with the Aiport Express -- latest model with WAN and LAN ports -- and got the exact same behavior. I suspect that all Airport models just treat the multple ethernet ports as a dumb layer two switch and blindly forward ethernet broadcast traffic from one port to all the others.)

    Thanks for reporting this.. I think you should advise Apple of this flaw.. It is a serious flaw.
    The cable modems are always made with local IP address so you can check the settings and the DHCP in them is designed for using a block of public IP addresses.. ie.. if you were extremely rich.. you buy a block of IP addresses from the ISP, plug the modem directly to a switch. And every client that joined would get a public IP address. Since the ISP are not that generous as to actually hand out more than one IP, (our local cable ISP in Australia, Telstra actually gives out 3 for free). The modem however will switch from public to private IP address when it does so, once the first address is allocated. There is no security risk as that private IP has no internet connection. (Test it and see, but any device getting 192.168 address should have no internet connection). The Modem has no NAT.. so it is purely for internal purposes.
    When you tested the Airport Express, did you set it up to 172.16.x.x range as well?
    Could you please test if you haven't already the TC at its native IP address and range?
    Domestic routers often fail to work properly if used off their default range.. somewhere in the coding they have fixed some addressing, instead of correctly using settings you put in. This is not at all unusual actually. My advice to people is always stick with default unless you really want some pain.
    If you are happy with pain, I would ensure all names are set to SMB standard.. as it sounds like you know networks I presume you would already do this. Apple names are ghastly things.
    Stick to short, no spaces, pure alphanumeric names for everything.
    Make sure the dhcp range includes enough addresses that it cannot run out..the normal standard is 2-200.
    If the lease time is set to 1day default, set it to 20min.
    I would also turn off ipv6 (maybe only possible on the client). That does seem to lead to confusion.
    If necessary you should be able to use static IP reservation via the dhcp setting in the TC.. that might also help.
    Are you running a 5.6 utility to do the setup?? If not you must!!
    You can load it even into Mountain Lion with a bit of fiddling.
    Check logs and setup the reservation for any devices failing to get IP correctly.
    And yes, in the end you may have to simply use a more standard router.. and hive off the TC to bridged role.

Maybe you are looking for