Computer Hope
Internet & Networking => Networking => Topic started by: squall_01 on May 14, 2009, 05:00:46 AM
-
I got a book that came with a copy of the OS. I didnt have the network connected at the time and thought that I could connect it later. Its supposed to be a wired rj45 connection. I followed the steps, Went to network config clicked devices clicked eth0 told it to start on boot and obtain an ip automatically but its not being seen by the others.
-
In a terminal window/at a shell prompt type the following commands: "ifconfig; route" and copy and paste the output here.
Then type "service network restart" and repeat the previous "ifconfig; route" and copy and paste the output here.
Ta!
-
I got it but its in a sxw file format.
-
.sxw is Star Office Writer text format. How did you copy the information?
-
Squall made a statement, not a question. ::)
-
manually, which I dont really feel like doing again.
-
manually, which I dont really feel like doing again.
Do you "feel" like sorting this out?
-
Are you able to copy/paste it to notepad or wordpad or something?
-
yes, how? I cant get it in the right format unless you want unicode. Also, updateing n such not sure if I would be able to send it.
-
Open Office will convert it. I'm trying to find others...
-
still updateing an such. I got it though.
[attachment deleted by admin]
-
Okay so we have here first:
eth0 Link encap:Ethernet HWaddr 00:01:02:3B:DF:A3
inet6 addr: fe80::201:2ff:fe3b:dfa3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:285 errors:0 dropped:0 overruns:1 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37909 (37.0 KiB) TX bytes:2430 (2.3 KiB)
Interrupt:10 Base address:0xb000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3619 errors:0 dropped:0 overruns:0 frame:0
TX packets:3619 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4425174 (4.2 MiB) TX bytes:4425174 (4.2 MiB)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 * 255.255.0.0 U 0 0 0 lo
This is the state of the ethernet interface before it's picked up an IP address. Then, once DHCP is complete:
eth0 Link encap:Ethernet HWaddr 00:01:02:3B:DF:A3
inet addr:192.168.0.34 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:2ff:fe3b:dfa3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:311 errors:0 dropped:0 overruns:1 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:42447 (41.4 KiB) TX bytes:5027 (4.9 KiB)
Interrupt:10 Base address:0xb000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3847 errors:0 dropped:0 overruns:0 frame:0
TX packets:3847 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4441198 (4.2 MiB) TX bytes:4441198 (4.2 MiB)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
So your Linux box has picked up the IP address 192.168.0.34 with a gateway of 192.168.0.1. Assuming there are no physical or authentication problems, you should be able to ping the gateway from the Linux box. Try it. Then try pinging something else that should normally work - www.google.com, for example. Success would look something like this:
(#:~)- ping www.google.com
PING www.l.google.com (209.85.229.99) 56(84) bytes of data.
64 bytes from www.google.com (209.85.229.99): icmp_seq=1 ttl=245 time=36.0 ms
64 bytes from www.google.com (209.85.229.99): icmp_seq=2 ttl=245 time=36.4 ms
64 bytes from www.google.com (209.85.229.99): icmp_seq=3 ttl=245 time=35.1 ms
If your ping attempt returns an IP address for www.google.com (as above), your network is complete. If no address is returned, then you have a DNS problem. Check out the contents of the /etc/resolv.conf file. They should be something like:
search local
nameserver 10.0.0.2
nameserver 212.23.6.100
nameserver 212.23.3.100
In this file the first line indicates that computer.local is on my local domain so if I do "ping computer", the resolver will automatically change this to "ping computer.local". The other lines are my DNS servers, starting with my local router, followed by my ISP's.
-
okay so here is what I looked into then, I notice that it said that it was inactive so I tried to active it. Came back can't active device, determining ip info for eth0. ping ($(%(#($@)@)$@)@) bytes data. Then its says that it came back with 3 errors and transmitted 4 packets. Windows said that it was an unreachable host.
-
Windows? I thought we were dealing with a Linux box?
-
did you even read the topic of this thread?
-
The topic states, Red Hat to Windows. It is not very descriptive. Even I thought, at this point, that you were still trying to work things out on the Linux side.
I'm assuming, at this point, you've migrated the "box" away from Red Hat to a version of Windows?
-
oh ha sorry I see why you thought that. NO I attempting to get the linux side working.
-
did you even read the topic of this thread?
If you can't be bothered to be civil, then I can't be bothered to help you any more. Sorry.
-
I am, thought that it had been staright forward but it wasnt.
-
I was checking post for something else when I saw that I made a post like this one a while back before I took any linux. If I got samba would that config it correctly then?
-
Samba would assist you in sharing files from a Linux box to a Windows network, if that's what you mean.
-
Are your DNS and Domain the same on both machines?
-
Its a peer to peer