so...your modem is plugged into your pc? with an ethernet cable?

btw, i love your commitment!

Thanks detpenguin. Once again, very encouraging. This certainly has become a work in progress but little by little, step by step it's slowly coming together .

so...your modem is plugged into your pc? with an ethernet cable?

No, not directly, one cable goes from the modem to the router and another cable from the router to my pc. Now I don't know too much about routers, a friend of mine is staying with me for a while and she brought her laptop along with her router which I hooked up to my computer, but I wouldn't think that would make a difference, would it? If that were the case wouldn't it have affected my Windows internet connection?

it wouldn't affect your windows connection...windows seems to just automatically work...mine did anyways...and i'm hooked up to a hub...so yeah.

if your hooked up to a router, i gotta think this should work...
maybe try going through netconfig again, and rebooting...maybe you need to reboot for the modules to load?

so open a term

su
password
netconfig
hostname conductor
domain conductor.org
DHCP
don't worry about hostname here...
click ok to accept settings

reboot and see if your online?

that should work for ya....at least it's worth a try?

I'm totally confused on your network setup. You have a router. From there a ethernet cable goes from the router to your computer. your computer has a wi fi pci card in it. then the labtop internet uses the wi fi card.

That is a very strang setup. Did you run out of ports on your router to hook a wireless access point to it directly. I would have just used a switch myself.

So the fact that there is a wireless card has nothing to do with your internet connection, right? It's for a labtop?

root$ lspci

what does it say?

and what pci cards do you have?

seems like the laptop is the only wifi action happening, and the main pc is basically hardwired to the modem through the router, so as long as it's not a static ip, DHCP should configure and work..."should" being the operative word here...lol.

I would definetly advise you read a tutorial about linux on the web some where. They are all over the place. Learn the file system. Simple commands like ls, cd, mkdir,man,grep,ping,modprobe. learn what init does the king of all process and how it boots up your system and calls bsd style init scripts (since you have slack). This is all basic stuff you should know before attempting to install slack. Sorry, I don't mean to sound like an ass, but it is just the truth.

Actually even if it uses a dhcp. Most router will pass out the first ip (192.168.0.101) to whatever computer is connect to port one unless you specefically tell it otherwise. Then 192.168.0.102 to port 2 ans so on. So for simplisity you could just use a static config in linux and it will work.

Also a quick test to see if you network card is working is just to try to ping the router direct.

root$ ping 192.168.0.1

If this works you know the network card is working. Then it is just a matter of setting up your stuff through netconfig and editing resolv.conf.

root$ man resolv.conf

I would think that if you slammed in a Mandrake cd and installed it. Then went to a tutorial on the web and opened up a xterm and started messing around would have been much more effecient. Mandrake is a toy a retard could use it. That's what i did when i first started except i used Red hat. I messed around with everything until I trashed the system totally. Then when to mandrake and so on. The thing is I know it is only a matter of time before your system is trashed by you learning linux and you will have to restart. Slackware is not forgiving. One simple command at a prompt and it's gone. Unlike Mandrake or redhat, which warns you about everything and will not let you do certain things, like say remove glibc or delete your entire sbin directory without ever asking you if it's okay.

Whew! Lots of info for me to work with here.

I did two ping tests earlier, one for www.google.com (no good) then I did a ping test for 192.168.0.1 (good). I tried a static configuration but that didn't do it either.

As detpenguin says my pc is hardwired to the modem through the router, Lee's Powerbook has a built-in wireless card (airport) so essentially it shouldn't have any effect on my card unless as chris says the router is passing a different ip to my pc.

Basically chris the system's installed and ready to go, it's just this one last hurdle to get over and it's done. I know your not trying to be an ass but you should try and have a little faith in even a "newbie's" intellegence. Five years ago I bought my first computer (this one) and taught myself through trial & error, research and a little help from others (mostly trial & error) the nuts and bolts of the computing game which I became fairly proficient at it in a relatively short time, and guess what, I've still got the same old, somewhat underpowered Celeron 566 and haven't fried anything yet (knock on wood). In reality, this technology moves so fast, we're all newbies all the time.

Ok it's time to go and do some work on my Linux system. Thanks guys, talk to you tomorrow.

conductor

couple questions for ya...

what kind of modem is it? usb, serial, what make and stuff...

have you tried bypassing the router, and just plugging the modem into your pc?

if you can ping the router direct that means your gateway and stuff is set up right. just edit /etc/resolv.conf with a correct nameserver.

nameserver "ip_dns_server"

hell you could use any DNS server in the world if you wanted to. If there is other lines in there delete them for now and just have that one with a valid DNS server. then go ping "some .com address"

and one more suggestion...

check your /etc/rc.d/rc.inet1.conf file and see if you have DHCP enabled on eth0

the second paragraph down is what i'm talking about...this is mine

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""

make sure your USE_DHCP[0] says yes.

if not, open a terminal and type

su
password
pico /etc/rc.d/rc.inet1.conf

then scroll down and change the "no" to a "yes"

then hit

cntrl x
it'll ask if you want to save it, yes
and hit enter

and reboot so the modules load

Morning Guys,

It's a D-Link DSL-3000 ADSL modem.

Yeah I did try that detpenguin, but I only tried one option in netconfig - DHCP and it didn't work. I'm going to try that again later using a static config.

I'm wondering now if I might have to install the router's software on my computer in order for Linux to pickup the ip?
I do have the disk. But then on the other hand, by doing a static config using the router's ip numbers from my winipcfg you'ld think that would be sufficient.

I think the best thing to do right now is follow chris's advice and do those tests.

Tell me about "Lisa".

Forget about the router software ... don't need it. Go static in netconfig... edit /etc/resolv.conf and call it a day. I've done it a thousand times with routers and works every single time.

Ok. I got a ping from my ip address 192.168.0.100 but no ping from the dns servers/default gateway/dhcp server 192.168.0.1 "Destination Host Unreachable".