« on: August 07, 2008, 07:28:57 am »
Howdy folks! -- I'm in about 3 months since my real interest in LinuxMCE; lots of research reading all your comments and watching the video over and over before I committed to get started. It's had its rough spots so far including multiple incompatible capture cards and IR remotes and gyro remote, getting a couple VAIO jukes over e-bay, and adding an additional SATA TB drive (I'll be writing an article on that later). I'm still hopeful that it'll all turn out in the end. I'm hopeful about getting it working and then helping friends do theirs; also hopeful for an iPhone 3G orbiter! This is my first post here. But enough of the introduction...
Despite my best efforts, I cannot for the life of me get the core/hybrid itself to connect to the internet. The givens:
--2 NICs (one external, one internal);
--DHCP at DSL router is ON. I allow wireless connections to the external network,
--DHCP-enabled DSL router goes straight to the external NIC on MCE and provides a 192.168.0.x IP to eth0;
--DHCP at LinuxMCE is ON. Devices hardwired to the internal hub get their 192.168.80.x from eth1 (192.168.80.1);
--internal network does great; I attach my Ubuntu Hardy lappy to an internal hub and I can get to the Net fine.
--external network does great; I attach my WinXP lappy over wireless and reach the Net fine.
!! But, no Internet directly from the core/hybrid.
--on install eth1 was external and eth0 was internal, I used the UI to switch these and their cables.
I reverified all network settings from KDE and it makes me wonder if I have to do some kind of core/hybrid configuration so that its own apps do some kind of BIND TO ALL NICs or something?
Thanks in advance for your comments (and salutations).
P.S. Modified: my NICs:
linuxmce@dcerouter:~$ lspci | grep -i ethernet
02:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
P.P.S. Modifed: answers to first round of responses:
basic network troubleshooting (from core/hybrid to internet):
-- bought a new ethernet cable for core/hybrid to dsl router. didn't fix it.
-- switching the internal/external cables at the core only made everything stop working. switched back.
-- ping to google is good...
linuxmce@dcerouter:~$ ping google.com
PING google.com (220.127.116.11) 56(84) bytes of data.
64 bytes from google.com (18.104.22.168): icmp_seq=1 ttl=255 time=151 ms
64 bytes from google.com (22.214.171.124): icmp_seq=2 ttl=255 time=151 ms
64 bytes from google.com (126.96.36.199): icmp_seq=3 ttl=255 time=148 ms
64 bytes from google.com (188.8.131.52): icmp_seq=4 ttl=255 time=148 ms
64 bytes from google.com (184.108.40.206): icmp_seq=5 ttl=255 time=163 ms
!! Aha! But ping to cnn is not so good...
linuxmce@dcerouter:/$ ping cnn.com
PING cnn.com (220.127.116.11) 56(84) bytes of data.
--- cnn.com ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 11000ms
Konqueror browser shows google.com, but chokes on cnn.com. cnn.com shows looking up address, then connecting to server, but never gets there. I think I'm very close now. Aha! sudo /etc/init.d/networking restart yielded the following:
DHCPRELEASE on eth0 to 192.168.0.1 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519120
I can get to cnn.com now, but not other addresses. Weird!
I can reach linuxmce.org, but not others. I don't get it.
See below for the process to reach this solution, but I had to "hard code" the ip address:
-- From the orbiter, advanced>kde desktop.
-- Then from the "K" menu at lower left, choose System Settings.
-- In kubuntu>system settings>network settings.
-- switch to administrator mode (at bottom) and enter your linuxmce password from installation.
-- Select the eth0 from the list and click [configure interface].
-- Switch from Automatic to Manual and OK.
-- Under the Domain Name Server list, moved the main DSL modem's address (in my environment 192.168.0.1) to the second position in the list. The first position shows the ISP's primary nameserver.