suse

lightwave · 10-19-2005, 11:35 PM

I saw similar problems But, unequal though on this forum.
I have a problem with SUSE 9.1. It is network related since I can not get through to the outside world by a ping command or browser launch. In browser I get error:

Unknown host <WEBSITE> with every site.

One thing I can do is ping my router and also even browse other machines on my network (windows XP). They can see Samba as well when on.
I am running router @ 192-168-0-1 and suse pulls a 192-168-0-100 valid address. So, I know the card works (eth0) no errors with ifconfig. I can not post since I am on a windows box right now for internet access.

Does anyone know what could be awry ?

thank you!!!!

adz · 10-20-2005, 12:26 AM

Do the other computers on your network have any problems? Do they all get their IPs dynamically assigned by the router?

jschiwal · 10-20-2005, 12:42 AM

Sounds like you don't have the default gateway set to the IP address of the router. Also check if you have DNS addresses, for finding websites.

lightwave · 10-20-2005, 02:22 AM

Adz,
Other machines have absolutely no problems connecting, dhcp, etc.

jschiwal,
I am at the default values it gives for these configs. Only because I put these back after trying other values. There is a place in yast to do this and there is a place to configure konquerer for proxy. Is this what needs to be done? At this point I think I tried all configs To my knowledge. Such as, detect auto, assign router / gateway, as proxy. I don't believe I have DNS addresses since I am not wanting to name resolve. Should I? Is there anywhere else that this need to or can be configured maybe?

Thanks,
(it feels like it is close since most everything else works but it just isn't able to reach internet)

lightwave · 10-20-2005, 02:42 AM

I just changed setting in Proxy under Configure Konquerer and selected -use the following proxy configuration and set it to the ip of my router. when launching a page it challenged mw with a password to the router. I entered though and it said there was an error in the proxy script and went back to my original problem.
Still not working

adz · 10-20-2005, 03:53 AM

No you don't set it as a proxy. Try putting the following code into /etc/resolv.conf:

Code:

nameserver 192.168.0.1

See if that works.

jschiwal · 10-20-2005, 03:53 PM

Sometimes when a network interface isn't configured properly, it is quickest to remove the adaptor in YaST and add it in again from the start. If this is a Cable/DSL router that provides DHCP and NAT services, the values for the IP and the DNS servers should be set by the DHCP server.
A proxy might be used if you are setting up a computer at work, and a gateway is used. In that case, the gateway proxy server is probably a different beast then the router. ( With a different IP address ).

lightwave · 10-20-2005, 05:59 PM

I hear ya here with proxy information. As a note here though, I never intended to use proxy or needed to use the functionality associated with it. Just to connect as you normally would plugging on to different networks etc is what i needed. I did try .conf setting(s).
I agree just blowing away the driver with the settings is what I did try as well with this issue. And config from the start. But, after multiple times of this I couldn't economically give much more time to this.
So, I am sorry to say I did not resolve the issue I was iniitially asking about and appreciate the help and input from you guys/forum.

But, I am happy to say I did resolve the issue and I am posting from the problem machine right now. The best way , (and I would most likely advise this to anyone in the future who has similar issues) , was I simply installed SUSE 9.3 over the top of the 9.1 install. (note: i reinstalled 9.1 first) killing the 9.1 install
This seemed to have the ability to recognize my configuration waaaay more efficiently. It did work before once or twice but it certainly didn't consistently. 9.3 is superior on this machine !
Also, I did not have to configure anything beyond simply going in to yast and accepting the default with the exception of ssid for the wireless connection. So, it had thrown me into playing with settings and this all seemed way too involved even upon consulting a SUSE thick book given to me by PhD (comp sci) at school. There is no config for proxy or edit needed.
Thanks for help And maybe if I get to know this OS better, I'll be able to help others in this forum too
j...

lightwave · 10-20-2005, 06:11 PM

Quote:

Originally posted by adz
No you don't set it as a proxy. Try putting the following code into /etc/resolv.conf:

Code:

nameserver 192.168.0.1

See if that works.

My interface was somehow defunk But you are certainly correct here as here is a copy of my good working resolv.conf:
### BEGIN INFO
#
# Modified_by: dhcpcd
# Backup: /etc/resolv.conf.saved.by.dhcpcd.eth0
# Process: dhcpcd
# Process_id: 5905
# Script: /sbin/modify_resolvconf
# Saveto:
# Info: This is a temporary resolv.conf created by service dhcpcd.
# The previous file has been saved and will be restored later.
#
# If you don't like your resolv.conf to be changed, you
# can set MODIFY_{RESOLV,NAMED}_CONF_DYNAMICALLY=no. This
# variables are placed in /etc/sysconfig/network/config.
#
# You can also configure service dhcpcd not to modify it.
#
# If you don't like dhcpcd to change your nameserver
# settings
# then either set DHCLIENT_MODIFY_RESOLV_CONF=no
# in /etc/sysconfig/network/dhcp, or
# set MODIFY_RESOLV_CONF_DYNAMICALLY=no in
# /etc/sysconfig/network/config or (manually) use dhcpcd
# with -R. If you only want to keep your searchlist, set
# DHCLIENT_KEEP_SEARCHLIST=yes in /etc/sysconfig/network/dhcp or
# (manually) use the -K option.
#
### END INFO
search slash
nameserver 192.168.0.1