Jump to content

sight4

Members
  • Posts

    10
  • Joined

  • Last visited

sight4's Achievements

New Here

New Here (1/7)

0

Reputation

  1. It looks as though I was correct about there being two different problems (if not more). Once I assigned a host name the computer boots up on the network everytime now. The problem of losing the network connection right away (less than 1 minute) still remains. I didn't see any significant clues in the log files. One thing I did notice there was a note about nss-mdns should be loaded. Any idea what nss-mdns is and is there any chance that could be related to my problem?
  2. When I am connected to the network for those few seconds the name servers are available. Those that I have listed are the same ones that the router has found. I don't think I am so far as to have a DNS problem because I can't ping anything except the local machine (127.0.0.1)-- not even the router(192.168.1.1). So when I type ping 192.168.1.1 I get a timeout. I did give the instructions listed above a try and as expected it didn't find linux.org. I think I need to go through the logfile and see what exactly happens between when the network comes up working and when the network stops working. This is based on the theory that some boot up command isn't executed until sometime after I am able to enter commands from console. The problem with that theory is it doesn't explain why sometimes the network comes up and sometimes it doesn't. Perhaps there are really two different problems. Now one question that does occur to me is where does the local machine get its name on the network? In my case, when I look at the router, it is a string of characters I can't type: a U with two dots over it, a lower case u also with two dots over it, a square box representing a character that can't be displayed, a D with a slash through it, a double comma, and a superscripted lower case a of diminished font size. Other linux machines I have been on have all had names assigned to them by the system admin and that is how they appear on the network. How do I do that here? Thanks
  3. A little more information here: I have changed my boot level to 3 so I would not come up in the KDE environment. The has had no effect. The system sometimes comes up online and sometimes doesn't find the network on bootup. When it does find the network on bootup the period of time it stays up varies from a few seconds to nearly a minute. Having the IPV6 mode enable or disabled does not appear to affect any of this.
  4. After I boot I do have an IP -- 192.168.1.105 and a gateway of 192.168.1.1. I had tried a static IP address when I first had the problem but it didn't help. Again now, it doesn't help. I added the alias line again and set a static IP address. Here are the results of issuing the various commands: eth0 Link encap:Ethernet HWaddr 00:13:D3:CD:64:D9 inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:5 Base address:0x4000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:60 errors:0 dropped:0 overruns:0 frame:0 TX packets:60 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5548 (5.4 KiB) TX bytes:5548 (5.4 KiB) Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 ;; connection timed out; no servers could be reached nameserver 204.127.203.135 nameserver 216.148.225.135 search localhost
  5. when I enter ifconfig I get ifconfig eth0 Link encap:Ethernet HWaddr 00:13:D3:CD:64:D9 inet6 addr: fe80::213:d3ff:fecd:64d9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:25 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:5 Base address:0x4000 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:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:896 (896.0 b) TX bytes:896 (896.0 b) when I enter netstat -r I get netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 169.254.0.0 * 255.255.0.0 U 0 0 0 lo 127.0.0.0 * 255.0.0.0 U 0 0 0 lo later, after a reboot, I entered the commands again and netstat -r gave a different result netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default * 192.168.1.1 UG 0 0 0 eth0 in both case there was no ability to use the network. That is a ping to 192.168.1.1 would not find the router. when I enter host linux.org I get host linux.org ;; connection timed out; no servers could be reached and when I enter cat /etc/resolv.conf I get cat /etc/resolv.conf nameserver 204.127.203.135 nameserver 216.148.225.135 search localhost
  6. The ethernet card is connected to a network switch to a LinkSys wireless router but I am not using the wireless features. That in turn is connected to a cable modem. When the computer is first turned on it does connect to the router getting the IP address 192.168.1.105 via gate way 192.168.1.1 which is indeed the router's address. It is found the DNS servers and I can access yahoo long enough to bring up the home page. After that it stops working. I tried adding the line to modprobe.conf as suggested but it didn't help any. Also, I've tried taking the network switch out of the path and that also didn't have any effect.
  7. The ethernet conroller is made by NVIDIA. I gave up trying to make this work by making adustments to the ethernet port and just did a new install of Mandriva. That was slightly succesful. I now have internet access for about one minute after a restart, then it goes away. Obviously there is something that happens shortly after boot up that is disabling my network access. After that brief period I can't ping my router. I don't think it is a firewall issue bacause I have all access permissions turned on. My security level is set to standard and the message from the Network Monitoring window is that the computer is not connected. I you have any other ideas, let me know. Thanks
  8. I have a new install of Mandriva. This is a dual boot system. Mandriva can't find the network. It finds the network card but doesn't get an IP address. When I boot this machine under Windows the network works fine. Only one NIC in the system.
  9. OK, I found a way to deal with this. From the command prompt I used mcc and then selected display. After making the change there and then rebooting I have increased the resolution as I want to. Hope this helps someone else in the future.
  10. I am absolutely new to Mandriva and loaded it up on a computer. When I run the KDE environment I can't get screen resolution any higher than 640 by 480. When I try to use the hardware configuration program "Change screen resolution" or "Configure your monitor" I just get an error message: "This program has exited abnormally". I tried to install a new video driver but that didn't work out either. This computer has an NVIDIA graphics chip set.
×
×
  • Create New...