Message
Re: [disklavier] Connect Disklavier to Internet via crossover cable
2013-09-07 by Adrian Thomas
Adrian Thomas
On Sep 6 2013, George Frederick Litterst wrote:
>Good morning, everyone.
>
>Lawrence, it looks to me as though you have double network address translation (NAT) going on. Let me give you an example of how IP addresses and NAT work:
>
>All network devices have an IP address, which is similar to a phone number. Some devices have a public IP address that can be contacted directly by any other device, such as www.amazon.com. We normally don't see the actual numbers that represent the IP address of www.amazon.com, but it does have a numeric IP address which is why our computers can contact Amazon.
>
>In our homes, all of our devices typically access the Internet through a single router. The router has a public IP address (that we normally do not see) which is assigned by our Internet service provider. The router, in turn, supplies private IP addresses (which the rest of the world cannot directly access) to all of our local devices. These private IP addresses are similar to telephone extension numbers in a business. The business usually has one publicly-facing telephone number but many extensions assigned to the various phones through the building.
>
>When your computer attempts to access www.amazon.com, it sends a connection request through your router. Your router, in turn, creates a table in its connection log that tells it that your computer (which is assigned a particular private IP address) is attempting a connection to a particular public IP address (the address of www.amazon.com).
>
>When www.amazon.com sends back the information that draws its web page in your browser, www.amazon.com sends that data to your public IP address, which is your router. Your router looks at its table of network address translations and realizes that your computer requested this information and then forwards the data to it.
>
>This system of translating between public and private IP addresses is necessary because, with the current IP system, there aren't enough public addresses for every device in the work. NAT is complicated but basically works. The router also provides some firewall protection, preventing your devices from receiving data that they did not request.
>
>If you introduce a second router into the equation, you have introduced the potential for error.
>
>There are a variety of Internet communication protocols, some of which are simple, such as accessing email or accessing a web page. Other types of Internet communication involve unimpeded, peer-to-peer data transfer, such as a video conference. These peer-to-peer connections often do not do well when there is more than one router in the chain.
>
>I don't know how communication works with DisklavierRadio or DisklavierTV. But, I strongly suspect that your trouble is with double NAT. Hypothetically, it might be possible to finagle the settings of the ICS setup. However, I have no experience with that and cannot provide any guidance.
>
>I think that you will be better off with another solution. In many situations, a good solution is a wall-plugged network extender such as:
>
>http://www.amazon.com/NETGEAR-XE102GNA-Wall-Plugged-Enet-Exte/dp/B000ERAIQ0
>
>This device makes it possible to use the electrical wires in your wall as a network bridge between your piano and the router. Unless you have unusual home wiring that has isolated the wall plugs near your piano from those near your router, this is a great solution.
>
>Regards,
>PianoBench
>
>On Sep 5, 2013, at 10:17 AM, lawrence_chiu_tx3@... wrote:
>
>>
>> Windows calls it "ICS" or Internet Connection Sharing. The way it works is it sets up a VLAN on that port with Windows itself serving its own DHCP, gateway and DNS on that VLAN.
>>
>>
>>
>> Say the laptop uses the home wireless network and it is on subnet 192.168.0.0/255.255.255.0, after turning on ICS, ICS puts an IP address of 192.168.137.1 on the LAN port, and connecting the Disklavier shows it has the following settings:
>>
>> IP 192.168.137.202
>>
>> Netmask 255.255.255.0
>>
>> DNS1 192.168.137.1
>>
>> DNS2
>>
>> Gateway 192.168.137.1
>>
>>
>>
>> The laptop can ping the Disklavier at that IP address successfully.
>>
>>
>>
>> But when trying to use the Internet for say Disklavier Radio, the pocket controller says:
>>
>> Failed to connect to the Internet.
>>
>> Please confirm your network
>>
>> environment
>>
>> (CABLE,HUBS,ROUTER,etc), and
>>
>> restart your Disklavier.
>>
>>
>>
>> as if the Disklavier has no network connectivity.
>>
>>
>>
>> I have tested the ICS function by connecting another PC to the laptop's LAN port and ICS is working perfectly. The Other PC can hit the Internet, no problem in this scenario.
>>
>>
>>
>> Finally I tried both regular Ethernet cable and crossover-Ethernet cable, with the same result (Disklavier gets IP address but can't connect to Internet)
>>
>>
>>
>> Thank you for all the replies.
>>
>>
>>
>>
>>
>>
>> --- In disklavier@yahoogroups.com, wrote:
>>
>> Good evening, everyone.
>>
>> Lawrence, have you checked the IP address of the Disklavier in this situation and compared it to the IP address of the PC? I am wondering if the PC is functioning as a DHCP server and providing the Disklavier with an IP address or whether the Disklavier is getting an IP address from the address pool from the router, which would mean that it's IP address is similar to that of the PC.
>>
>> If the PC is providing it with an IP address, then there is double network address translation going on.
>>
>> Regards,
>> PianoBench
>>
>> On Sep 4, 2013, at 3:10 PM, lawrence_chiu_tx3@... wrote:
>>
>>
>> For those people who connect their Disklavier to the Internet, I guess many of you are using an Internet router or bridge. I was wondering if anyone has done this however since there is already a laptop connected for RemoteLive.
>>
>>
>>
>> Let's say the laptop has a LAN port and a Wireless card, so it has two network interfaces.
>>
>> The laptop is connected to the Internet via Wireless and everything is tested working.
>>
>> Then you tell Windows to "Share" the wireless adapter's Internet connection and select the LAN port to bridge to it.
>>
>> If you then test this by connecting a PC to it via the LAN port (the PC has no other ways to access the Internet), using an Ethernet "crossover" (usually orange color) cable, you can verify that this works just fine and the PC can get to the Internet.
>>
>> Now, If y ou connect the crossover cable to the Disklavier, it appears that the Disklavier will get its IP address, gateway, and DNS, but for some reason, the Pocket Controller still says it has no connection to the Internet. I was wondering why this is?
>>
>> Thank you.
>>
>>
>>
>>
>>
>
>