Port Forwarding and Internet Sharing

Hey all,
I have a wireless network set up through a Time Capsule. My iBook is connected to this network via Airport. In addition, I have a computer with no wireless connected to my laptop via Ethernet. I have my System Preferences set up to Share Internet with Built-In Ethernet. The problem is this. I want to use the second computer (which accesses the Internet fine) as a server. The Airport does not recognize the second computer as a Client, but does see the iBook. I believe I need to Forward Ports to the iBook (local IP: 10.0.1.5) and then forward them again with the iBook to the other computer which has the local IP 196.168.2.2.
Is my thinking right in this? How would I need to configure this to make it work as I've explained?
If I'm unclear I can clarify.
Thanks,
Daniel

Hi Daniel,
I think the problem is, is that the Internet Sharing isa pass through connection.
Try this, in Network>Show:>Network Port Configurations, duplicate the Airport interface, make sure the on used for internet is dragged to the top of the list, then Manually configure if need be, the second one to join the local Network.

Similar Messages

  • Port forwarding through Internet Sharing

    Here's my setup:
    - I have a Linksys router, I have that connected wirelessly to my macbook, I have that setup for Ethernet internet sharing to my desktop pc.
    - I want to enable port forwarding so that I can access my PC through VNC.
    - My macbooks ip address is within 192.168.1.x and my desktop's IP address from the macbook is within 192.168.2.x
    - When I connect to my router and try to set up port forwarding I can only forward ports within the 192.168.1.x range.
    - I've tried a bunch of garbage to get it set up, one main thing I've tried was to st my PC's ip address statically to something withing 192.168.1.x, but my default gateway address is 192.168.2.1 so I'm not even sure if thats possible.
    - I really need some help with this, any would be very much appreciated.

    Hi guys. My setup is pretty simple. I have a Terayon cable modem hooked to an iMac. Im doing internet sharing to everybody. I don't need an access point and don't wish to have to buy a new one when I have such a beautiful machine right.
    So I want to do port forwarding using the internet share to connect an XBox360.
    The ports i want to configure are detailed in www.portforward.com
    Anyway I can't see how to do it but I know that for you guys this is all puppy chow. So i decided to give you guys the opportunity to be creative with this setup.

  • Port forwarding within Internet Sharing

    my xbox is connected to my macbook sharing the wireless internet, but i want to forward a port to my xbox. how do i do that? can't connect the xbox directly to the router.

    How did you get the xbox to share the internet connection?? I can't seem to get it to work with my setup for some reason.
    I've got a macbook connected through wireless. The xbox is plugged into the mac. the internet sharing is on. Web sharing is on. The Airport is set as the top priority port... Double checked all the firewall settings... The only thing I can think I haven't tried is a different type of cable... Do I need a cross-over? I'm totally stumped!

  • Error message about firewall and internet sharing

    hello all i have a question regarding the use of firewall and internet sharing.
    I have a PMG5 connected to internet through Airport. I've linked an Xbox 360 via the built-in ethernet port in order to access Xbox Live. I had to open specific UDP ports on the OS X firewall but it now works fine. However, in the Sharing Preference Pane, Internet Tab, i still get an error message saying that my Internet Sharing is disturbed by the settings of the firewall and sharing services, it says that i did not activate "personal web sharing" in the first two tabs...but i DID ! And there's no way to get rid of this error message.
    I know I know some may consider it's not a real problem because it's just an error message while the connection actually works fine but well, I tend to hate error messages when they're not supposed to show up. So if anyone know the answer, thanks in advance...
    Good day to everyone
    Vince, Paris...

    sorry about the delay in replying, was kinda busy
    well trashing the pref files was useless and i tried with another user, same thing. As for the second opinion, the problem was not about which port was used cause as i said the connection sharing works fine and anyway it was the correct port that was checked, it's just that i get an error message while there is no apparent error and everything works fine, i'm told that personal web sharing is not enabled but it is...
    Anyway as i said, it's probably not a real matter, as long as it works...which brings me to another thing. I've created a special protocol in the firewall to enable a proper dialog with the xbox. it's basically the same thing you do for ichat AV when you have video connection problems, you track down the concerned UDP port using terminal, you allow traffic and all... The protocol for the xbox worked great for some days, but now it seems it's not enough, the game set keeps trying on another port and i constantly have to update the protocol or deactivate the firewall...and enabling back all UDP traffic is not enough to solve it.
    In a way i think everything is linked, the initial error message when everything was fine and the current trouble. Any idea?
    thanks
    Vince

  • TS2972 How do you port forward for Home Sharing ?

    I want to home share with my apple tv and it's not working, so i think i need to port forward for home sharing on my apple tv. But i dont know how to port forward :S

    I use an application called port map. http://www.codingmonkeys.de/portmap/  Make sure you download the landlubbers version. When you open it add a port called minecraft with the port 25565

  • Time Capsule 2 TB, stops port forwarding and cannot be accessed by AAU

    Hi
    I am having the above problem off and on since purchasing the TC. It is dialing in PPOE (fiber optic), connects fine to internet and feeds internet reliably by wireless and wired connections. It will however stop port forwarding and allowing access by Finder or Airport Util. simultaneously at what appears to be random intervals.
    I can unplug the electric and power back on and all is fixed for a week or so. This of course causes havoc with time machine, web server on the network, vpn service etc.
    I have all the updates on AAU osx and I believe everything possible.
    I have the TC, a mini running osx server 10.6.3, a macbook pro, macbook air (Leopard). All running 10.6.3 except the Air.
    I run time machine on all the computers but usually do it manually to avoid 2 machines accessing the Tc at the same time, though sometimes I forget to turn TM off and 2 comps. may be trying to access TC through Time Mach. simultaneously.
    I also have another wireless router getting the internet and making a wireless network in a separate building.
    I have read all the posts but do not see any clear solution or mention of the port forwarding stopping along with access.
    Any help appreciated. If it's defective my year will be coming up, so I want to figure this out now.

    Hi Bob,
    Yes I did a hard reset in order to set it up. I then used the Airport Utility to give it a Network name and base station name that was different from the Wireless AC one upstairs. I left everything else set to defaults and used 'Create a new wireless network'. Added some passwords and then let it boot itself. It all worked ok but as I mentioned I can then only access this downstairs network. The Wireless AC one then refuses to connect afterwards. The only way I can get the Wireless AC to work is to switch off the Wireless N one and then reboot the Wireless AC.
    Maybe I need to change the DHCP port ranges or something ? Is it correct to have x2 networks ?. I dont see any other option given wireless wont reach and I cant cable between the two to create a bridged network.

  • Help with LTE and Internet Sharing for BUIlD Lumia...

    Nokia,
    I received the Lumia 920 when I was at BUILD 2 weeks ago. I followed the instructions and the phone mostly works on AT&T. I had a 900 so I assumed my LTE and Internet Sharing plan would easily transfer. Unfortunately that does not seem to be the case. I called AT&T gave them my IMEI number but it's not in their system and is not recognized as a Lumia 920. Because this is not an "AT&T phone" they wouldn't do much more to help. My data connection only ever shows 4G, never LTE as my 900 does and I cannot enable Internet Sharing even though it's on my data plan. I believe this is all controlled by the IMEI number.
    Is there anything Nokia can do to help us? I can't imagine I'm the only one having this problem! I'm going to try again to see if I can get the issue escalated and maybe they can force the IMEI number to be recognized as a 920.
    Thanks!

    Sorry I never came back to update. The fix, as has been noted already, is to make sure AT&T has your IMEI as another 920 or your old 900 so that you get LTE (which appears as "4G"). Then, in the Nokia Access Point config setting (under System Config), make sure LTE2 is selected, then install an additional keyboard (I tried both Spanish and Chinese). This will force an OTA update that seems to enable Internet Sharing. I had to redo it a second time when I updated my Nokia Access Point app last week, but I just re-installed a NEW keyboard and got Internet Sharing back. It hasn't gone away since, contrary to what others have experienced. For more info (and where I found the fix) see this XDA thread: http://forum.xda-developers.com/showthread.php?t=1971997

  • Airport and internet sharing turns off by itself

    Hi everyone, I have an imac that I purchased earlier this year, and I use internet sharing to get internet for my ipod touch. Until a few months ago, this worked fine but now airport and internet sharing turn off every time I restart the computer and I have to turn both back on every time. Is anyone else experiencing this problem or know hot to fix it?

    Hi and Welcome to Apple Discussions...
    Download and install the v10.5.8 combo update available here.
    http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate
    One of the "fixes" includes: - compatibility and reliability issues when joining AirPort networks.
    After the installation, repair disk permissions.
    Quit any open applications/programs. Launch Disk Utility. (Applications/Utilities) Select MacintoshHD in the panel on the left, select the FirstAid tab. Click: Repair Disk Permissions. When it's finished from the Menu Bar, Quit Disk Utility and restart your Mac. If you see a long list of "messages" in the permissions window, it's ok. That can be ignored. As long as you see, "Permissions Repair Complete" when it's finished... you're done. Quit Disk Utility and restart your Mac.
    Carolyn

  • OSX 10.6.8 and Internet Sharing to Ethernet

    I am trying to set up Internet Sharing so that I can connect my old MacBook Pro running 10.6.8 via ethernet to another device - I'm trying with xbox360 and Sony Blu Ray (BPD-S185) (for diversity of devices - I used to have it working on my xbox, but really want it working with the blu ray player but the network status feedback is better for problem solving on the xbox!).
    I have my MBP connected to my home network over Airport which has the following details:
    - IP: 192.168.1.5
    - Router IP: 192.168.1.1
    I have then enabled Internet Sharing through System Preferences to share my Airport connection to my Ethernet connection.
    I have the following Ethernet settings:
    - Configure IPv4: Using DHCP with manual address
    - (Ethernet) IP address: 192.168.2.1
    - Subnet Mask: (blank - not user accessable, changes to 255.255.255.0 when xbox turned on)
    - Router: (blank - not user accessable)
    - DNS Server: 192.168.1.1
    - Search Domains: (left blank)
    On the xbox I've set the network settings to:
    - IP: 192.168.2.2
    - Subnet: 255.255.255.0
    - Gateway: 192.168.2.1
    - Primary DNS: 192.168.1.1
    - Secondary DNS: 192.168.2.1
    When I then select 'Test my Xbox Live Connection'  it takes a while, the Network status shows 'Connected', however The Internet Failed.  I am informed that the 'Test Failed' and 'more information' tells me I have an 'Internet Error' with the following Status codes:
    W: 0000-000B
    X: 0000-000D
    Y: 0000-0000
    Z: 0000-0000
    ID0004-000
    L: 0015-10F1
    Q: 8007-0435
    T: Wired
    A: 192.168.2.2/255.255.255.0
    G: 192.168.2.1
    D: 192.168.1.1/192.168.2.1
    So, it looks as though the problem lies with the MBP and internet sharing on OSX.  I have extra suspicions that this is the problem, as connecting my Blu Ray player to my MBP via ethernet I also get a successful connection to the network, but no internet access.
    Pleeeeease can someone help?!?!  This is driving me nuts - a couple of years ago I had internet sharing working to let my xbox connect to the internet, so what's happened in the last few years to mean this won't work?

    If you want to back it up there, use the Disk Utility to create a disk image of it.
    If you want to import its contents to iMovie, iTunes, or elsewhere, use MPEG Streamclip and Apple's MPEG-2 playback component to convert the VOB files on it to a different format.
    (65437)

  • HT1433 Hi, my internet sharing was working perfectly in 10.6.8, sharing my vpn connection to my apple tv with no problems. I then upgraded to 10.7 etc and internet sharing stopped. I have since reverted my computer back to 10.6.8 but no luck still, though

    Hi, my internet sharing was working perfectly in 10.6.8, sharing my vpn connection to my apple tv with no problems. I then upgraded to 10.7 etc and internet sharing stopped. I have since reverted my computer back to 10.6.8 but no luck still, thoughts?

    Hi, my internet sharing was working perfectly in 10.6.8, sharing my vpn connection to my apple tv with no problems. I then upgraded to 10.7 etc and internet sharing stopped. I have since reverted my computer back to 10.6.8 but no luck still, thoughts?

  • NAT port-forwarding and WAN side IP addresses

    I have my Airport Extreme setup to forward port 21 to an FTP server on the LAN side of my network. The AE is connected via DSL to my ISP.
    When a client from the WAN side connects to my server, the server's LOGS don't list the IP of the client, rather it says the client connected from my assigned WAN IP. For example (fake ip's):
    Client ----> AE ----> FTP-SERVER
    130.129.12.3 76.99.89.3 10.0.1.2
    Log states client connected
    from IP: 76.99.89.3
    My previous Linksys router, with the same DSL modem and ISP, would report the client as connecting from 130.129.12.3.
    Am I missing something in how I am configureing my AE? Or, is this how the AE manages port-forwarding and there's nothing I can do about it?
    I used to use firewall rules to control access to the FTP server, i.e. rules set on the server. This can't be done anymore with the AE operating as it does.

    Seems to me that the NAT translation in the Airport 802.11n is such that it does not use the incoming IP of clients connecting from the WAN side to a computer on the LAN side. The ingoing and outgoing packets reach their respective destinations, it is just that the AE uses some kind of non-standard routing (at least not that I am used to working with).
    This is bad because it prevents the use of some forms of access controls on BSD and Linux servers on the LAN side, TCP Wrappers and iptables for example. This can create obvious security problems when WAN ports are set to forward to such a LAN client. We are already getting hit with robot-like script attacks on our server, this was a problem with our Linksys router, but with the above mentioned tools and scripts we were able to block abusive clients.
    Perhaps an Apple can work on resolving this issue in a future firmware release, at least make it an option... Anyone from Apple out there?
    jmj

  • Port forwarding and LAN traffic suddenly stopped working

    My WRT54G was chugging along happily for many months, and suddenly all port forwarding and local LAN traffic stopped flowing. All PCs behind the router on the LAN side can get to all WAN sites just fine, but they cannot ping one another. All of them can ping the router (192.168.1.1) just fine.
    Any ideas?
    Thanks,
    Curtis

    I solved this.  Turned out to not be the router at all, but the accidental enablement of the "Stateful Firewall" within my Cisco VPN client.  Once this option is turned on, the machine gets isolated from the LAN, even when the VPN client isn't visibly running.

  • Port Forwarding and Loopback with HomeHub 3B

    There have been a number of threads discussing port forwarding and loopback, so I thought it might be useful to summarise my experiences. I have two HomeHub 3Bs on separate lines, one is a standard broadband line, the other is on an Infinity connection. My experience is limited to these two specific devices :-)
    Port Forwarding does work but it is "temperamental" and "arcane" in the way you need to set it up. Although I have had it running perfectly, I have also had experiences where the router has refused to "accept" my changes. Tentatively, I put this down to the fact that I was running a Seagate GoFlex network drive on the network and this piece of equipment (definitely a Do Not Buy) was acting aggressively and screwing up the DDNS allocations. But ... YMMV
    One definite probllem with Port Forwarding is if you attempt to specify a range of addresses. I have failed to get this to work on both my hubs. In my case I was trying to forward (say) 8021-8022 to 21-22, and the router insisted on forwarding both 8021 and 8022 to port 21.  The cure is to set up each port as a separate rule within the same user-defined application.
    On Loopback, I know various people have said it doesnt work, but it has always worked fine for me, at both the locations where I have a HomeHub 3B. I use a DDNS service and I can test that my port forwarding is working by opening a Command Prompt window on my PC and typing  telnet mydomain.dyndns.web.com 21 or whatever. That command contacts my DDNS host to ascertain my IP address and then (attempts to) connect to port 21.
    If port 21 is closed on your router (i.e. you have no port forwarding in place) you will see the message attempting to connect to mydomain.dyndns.web.com... and, after a while that will time out, with Could not open connection to the host, on port 21: Connect failed. If you do have your port forwarding set up correctly then your application will respond in some appropriate mannerr. However, you do need to understand what youre doing, because the response of an application that is expecting HTTP data is simply to do nothing!  You will probably get a blank screen. If you type GET / HTTP/1.1 [note spaces] (which is not echoed to your screen, so be careful not to mistype it) you will receive a page of HTTP response data and HTML data. Thus proving that your port forwarding is working.
    If you do not have any port forwarding set up at all, you can still test the loopback function by attempting to connect to port 161. This port is open on the BT routers and telnetting to it will result in a blank screen (as opposed to the attempting to connect message).
    In summary: loopback works on the Home Hub 3B. Port forwarding also works to a degree but it is temperamental and does have some quirks, like not properly accepting ranges of ports. On this last point, at least, it would be helpful to get an acknowledgement from BT that this is a known fault.

    There have been a number of threads discussing port forwarding and loopback, so I thought it might be useful to summarise my experiences. I have two HomeHub 3Bs on separate lines, one is a standard broadband line, the other is on an Infinity connection. My experience is limited to these two specific devices :-)
    Port Forwarding does work but it is "temperamental" and "arcane" in the way you need to set it up. Although I have had it running perfectly, I have also had experiences where the router has refused to "accept" my changes. Tentatively, I put this down to the fact that I was running a Seagate GoFlex network drive on the network and this piece of equipment (definitely a Do Not Buy) was acting aggressively and screwing up the DDNS allocations. But ... YMMV
    One definite probllem with Port Forwarding is if you attempt to specify a range of addresses. I have failed to get this to work on both my hubs. In my case I was trying to forward (say) 8021-8022 to 21-22, and the router insisted on forwarding both 8021 and 8022 to port 21.  The cure is to set up each port as a separate rule within the same user-defined application.
    On Loopback, I know various people have said it doesnt work, but it has always worked fine for me, at both the locations where I have a HomeHub 3B. I use a DDNS service and I can test that my port forwarding is working by opening a Command Prompt window on my PC and typing  telnet mydomain.dyndns.web.com 21 or whatever. That command contacts my DDNS host to ascertain my IP address and then (attempts to) connect to port 21.
    If port 21 is closed on your router (i.e. you have no port forwarding in place) you will see the message attempting to connect to mydomain.dyndns.web.com... and, after a while that will time out, with Could not open connection to the host, on port 21: Connect failed. If you do have your port forwarding set up correctly then your application will respond in some appropriate mannerr. However, you do need to understand what youre doing, because the response of an application that is expecting HTTP data is simply to do nothing!  You will probably get a blank screen. If you type GET / HTTP/1.1 [note spaces] (which is not echoed to your screen, so be careful not to mistype it) you will receive a page of HTTP response data and HTML data. Thus proving that your port forwarding is working.
    If you do not have any port forwarding set up at all, you can still test the loopback function by attempting to connect to port 161. This port is open on the BT routers and telnetting to it will result in a blank screen (as opposed to the attempting to connect message).
    In summary: loopback works on the Home Hub 3B. Port forwarding also works to a degree but it is temperamental and does have some quirks, like not properly accepting ranges of ports. On this last point, at least, it would be helpful to get an acknowledgement from BT that this is a known fault.

  • Port forwarding and DMZ refuses to work properly on WRT54G wireless router.

    I have a network setup on the wireless WRT54G version 8 (with latest firmware) router and port forwarding and DMZ refuse to work correctly. I'm trying to use bittorrent and connect my xbox360 to my computer and neither work properly even after setting up port forwarding in the "Applications and Gaming" tab.
    here's a screenshot of my port forwarding page:
    http://img205.imageshack.us/img205/1497/linksysbg2.jpg
    here's a screenshot of the DMZ page (my computer's IP ends in 102 obviously):
    http://img510.imageshack.us/img510/2131/linksys1rf5.jpg
    now, I've experienced this type of problem before. On a different linksys router a year or 2 back I remember the DMZ never working on that one either and I eventually had to buy a d-link router which worked perfectly. I'm only using this wireless router because it's my roommates and he brought it up. Somebody please explain to me why this isn't working correctly. I am becoming more and more frustrated as I lose faith in linksys routers. Thanks

    Did you tired upgrade of the firmware on the router??
    Also after upgrade reset & reconfigure the router for few seconds ... so that the firmware works properly for longer time ....

  • Difference Between Port Forwarding and Port Triggering.

    Hi guys,
    I'm lost! The differences between port forwarding and port triggering is driving me nuts! It all seems very subtle to me. Can anyone explain to me (in a very simple way) what exactly are their differences. Thanks in advance!!

    Port Forwarding
    The big difference between this and port triggering is that forwarding is fixed.. you forward a port and it is always forwarded.. IE available to connection.. basically the forwarded port is excluded from the fire walling abilities of the router.  Second it is static and applies to one machine only. Whereas you could set port triggering to the router and thereafter any machine on the LAN can trigger it unless its already in use.. port forwarding must be specified for each individual machine.
    Port forwarding requires you to give each PC on the network its own unique static IP address.. Although there is ssh port forwarding that can be set dynamically. Most users only have the option of static ip port forwarding.
    The real downside of port forwarding is that it can be very tricky to set up... You may have to allow a series of ports on a machine and have to do that for each machine you want to allow through. Also routers often have limited abilities and may not allow you the ability to forward a port or select the service you require.
    Port Triggering
     This is a way of Dynamically assigning a service to a port WHEN it is required by an outgoing service. The port is initially not allowed so nothing can get in and you are protected by your network.  
    A good example of this is when using Yahoo! voice .. the voice works fine for a few minutes after you connect to Yahoo! then Yahoo! sends some kind of packet that requires a response from your PC... The packet is allowed in through your router no prob but the outgoing reply is not authorized to open a port on the router and is thus blocked. 
    'ope this helps

Maybe you are looking for