locked
Problems adding additional clients RRS feed

  • Question

  • Here is the problem I am having.  I have an Apple Airport Extreme (yes I know)  :-)  I have the connector software on 1 PC and it's running and working fine. I am trying to install it on a second PC, however whenever I go to run it on a second machine, the connector installer can never find the server.  I know this is an issue with the router and port forwarding, because I have tested it.  For some reason, with the Airport, you can't forward (at least not to my knowledge) ports to multiple IP addresses.  You also cannot open the same ports to multiple IP addresses.  I am not sure why Apple designed the router like this, but it's pain.  Other than getting a different router that supports UPnP, does anyone know of another way that this can be accomplished?

    I am willing to consider a new router, but I'd like to exhaust all of my options before I do that.

    Any help would be greatly appreciated.

    Sunday, July 12, 2009 9:51 PM

Answers

  • DNS Suffixes and DNS Suffix Search lists like Connection-specific DNS Suffix  buffalo.rr.com are often causing name resolution trouble.
    Connector setup seems to use DNS heavily for resolving names. With above fields are filled in each call will attach the DNS suffix to the local name of your server, causing the machine to attempt the resolution of the name in the Internet, which of course fails.
    You should find the setting in the router (either in the DHCP settings or somewhere else) and remove it.
    After that reboot the router and the clients and check, if the Internet connection still works and that ipconfig /all no longer shows the suffix. (if it still does, try ipconfig /release and ipconfig /renew)
    As a workaround you could also try to add the server name and it's IP address to the hosts file on the client, located in Windows\system32\drivers\etc, with the risk, that each change of the servers IP address will lead to similar issues.
    Best greetings from Germany
    Olaf
    Tuesday, July 14, 2009 11:37 AM
    Moderator

All replies

  • Here is the problem I am having.  I have an Apple Airport Extreme (yes I know)  :-)  I have the connector software on 1 PC and it's running and working fine. I am trying to install it on a second PC, however whenever I go to run it on a second machine, the connector installer can never find the server.  I know this is an issue with the router and port forwarding, because I have tested it.  For some reason, with the Airport, you can't forward (at least not to my knowledge) ports to multiple IP addresses.  You also cannot open the same ports to multiple IP addresses.  I am not sure why Apple designed the router like this, but it's pain.  Other than getting a different router that supports UPnP, does anyone know of another way that this can be accomplished?

    I am willing to consider a new router, but I'd like to exhaust all of my options before I do that.

    Any help would be greatly appreciated.


    I am not familiar with that specific product, but generally speaking, you don't have to forward ports anywhere within your LAN (it should only be from your external IP to your server for Remote Access).  You should be able to "just find it" on the network.  Can you successfully ping your server, both by name and by IP address?  Can you type ipconfig /all from a command prompt on your PC that does work, the one that doesn't work, and your server, then post the results here?
    Monday, July 13, 2009 12:40 AM
    Moderator
  • Thank you for the reply.  I'll do it as soon as I can and post the answers.

    Thanks.
    Monday, July 13, 2009 12:42 AM
  • Here is the information.  The only thing I am missing is the ipconfig from the machine that doesn't work, however, it's going to be pretty much identical with the exception of the IP address.

    ========================================
    PC that works
    ========================================

    Microsoft Windows [Version 6.1.7100]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Paul>ping kelthuzad

    Pinging kelthuzad [10.0.1.8] with 32 bytes of data:
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128

    Ping statistics for 10.0.1.8:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

    C:\Users\Paul>ping 10.0.1.8

    Pinging 10.0.1.8 with 32 bytes of data:
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128

    Ping statistics for 10.0.1.8:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

     


    Microsoft Windows [Version 6.1.7100]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Paul>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Arthas
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : buffalo.rr.com

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : buffalo.rr.com
       Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
       Physical Address. . . . . . . . . : 00-22-15-1B-0E-E4
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2002:4cb4:c022:0:85a7:c8e6:f03d:4217(Pref
    erred)
       Temporary IPv6 Address. . . . . . : 2002:4cb4:c022:0:f952:933f:6c41:9682(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::85a7:c8e6:f03d:4217%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.0.1.199(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, July 12, 2009 7:49:24 AM
       Lease Expires . . . . . . . . . . : Sunday, July 12, 2009 11:49:31 PM
       Default Gateway . . . . . . . . . : fe80::216:cbff:fec2:be79%11
                                           10.0.1.1
       DHCP Server . . . . . . . . . . . : 10.0.1.1
       DNS Servers . . . . . . . . . . . : 10.0.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.buffalo.rr.com:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : buffalo.rr.com
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 9:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:c23:5c77:b34b:3fdd(Prefe
    rred)
       Link-local IPv6 Address . . . . . : fe80::c23:5c77:b34b:3fdd%12(Preferred)
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled

     

     

    =========================================
    PC that doesn't
    =========================================

    Microsoft Windows [Version 6.1.7100]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Paul>ping kelthuzad

    Pinging kelthuzad [10.0.1.8] with 32 bytes of data:
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=2ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128

    Ping statistics for 10.0.1.8:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 2ms, Average = 1ms


    C:\Users\Paul>ping 10.0.1.8

    Pinging 10.0.1.8 with 32 bytes of data:
    Reply from 10.0.1.8: bytes=32 time=4ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=4ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128

    Ping statistics for 10.0.1.8:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 4ms, Average = 2ms

    Monday, July 13, 2009 1:01 AM
  • Here is the information.  The only thing I am missing is the ipconfig from the machine that doesn't work, however, it's going to be pretty much identical with the exception of the IP address.

    ========================================
    PC that works
    ========================================

    Microsoft Windows [Version 6.1.7100]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Paul>ping kelthuzad

    Pinging kelthuzad [10.0.1.8] with 32 bytes of data:
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128

    Ping statistics for 10.0.1.8:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

    C:\Users\Paul>ping 10.0.1.8

    Pinging 10.0.1.8 with 32 bytes of data:
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time<1ms TTL=128

    Ping statistics for 10.0.1.8:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

     


    Microsoft Windows [Version 6.1.7100]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Paul>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Arthas
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : buffalo.rr.com

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : buffalo.rr.com
       Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
       Physical Address. . . . . . . . . : 00-22-15-1B-0E-E4
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2002:4cb4:c022:0:85a7:c8e6:f03d:4217(Pref
    erred)
       Temporary IPv6 Address. . . . . . : 2002:4cb4:c022:0:f952:933f:6c41:9682(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::85a7:c8e6:f03d:4217%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.0.1.199(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, July 12, 2009 7:49:24 AM
       Lease Expires . . . . . . . . . . : Sunday, July 12, 2009 11:49:31 PM
       Default Gateway . . . . . . . . . : fe80::216:cbff:fec2:be79%11
                                           10.0.1.1
       DHCP Server . . . . . . . . . . . : 10.0.1.1
       DNS Servers . . . . . . . . . . . : 10.0.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.buffalo.rr.com:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : buffalo.rr.com
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 9:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:c23:5c77:b34b:3fdd(Prefe
    rred)
       Link-local IPv6 Address . . . . . : fe80::c23:5c77:b34b:3fdd%12(Preferred)
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled

     

     

    =========================================
    PC that doesn't
    =========================================

    Microsoft Windows [Version 6.1.7100]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Paul>ping kelthuzad

    Pinging kelthuzad [10.0.1.8] with 32 bytes of data:
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=2ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128

    Ping statistics for 10.0.1.8:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 2ms, Average = 1ms


    C:\Users\Paul>ping 10.0.1.8

    Pinging 10.0.1.8 with 32 bytes of data:
    Reply from 10.0.1.8: bytes=32 time=4ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=4ms TTL=128
    Reply from 10.0.1.8: bytes=32 time=1ms TTL=128

    Ping statistics for 10.0.1.8:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 4ms, Average = 2ms


    It is important to include the one that doesn't work.  Otherwise, I don't know how you would expect anyone to assist.
    Monday, July 13, 2009 4:42 AM
    Moderator
  • DNS Suffixes and DNS Suffix Search lists like Connection-specific DNS Suffix  buffalo.rr.com are often causing name resolution trouble.
    Connector setup seems to use DNS heavily for resolving names. With above fields are filled in each call will attach the DNS suffix to the local name of your server, causing the machine to attempt the resolution of the name in the Internet, which of course fails.
    You should find the setting in the router (either in the DHCP settings or somewhere else) and remove it.
    After that reboot the router and the clients and check, if the Internet connection still works and that ipconfig /all no longer shows the suffix. (if it still does, try ipconfig /release and ipconfig /renew)
    As a workaround you could also try to add the server name and it's IP address to the hosts file on the client, located in Windows\system32\drivers\etc, with the risk, that each change of the servers IP address will lead to similar issues.
    Best greetings from Germany
    Olaf
    Tuesday, July 14, 2009 11:37 AM
    Moderator