[tlinux-users:07536] Re: Network on Portege 7020CT

From your description, Lee, it looks like your network connection is
working fine.  But here are a few standard tools to check:
	/sbin/ifconfig, run without any other data, will show you status of
your network connections.  You'll always get an entry for 'lo' (loopback
device) unless you didn't get a good boot.  You should also get an
ethernet entry, most likely 'eth0'.  In the data block you can see the
IP address that your D-link dhcp server assigned as well as some other
data.  Given that you can get out to the internet this stuff _has_ to be
there.  The address block 192.168.n.n is 'non routable' and that's used
by D-Link and Netgear routers as the local address space.  The router
itself will, by custom, have 192.168.n.1 (n is usually 0 or 1). 
Assuming your other two machines were dhcp-assigned, they're probably 2
and 3 and your Portege will be 4.  Ifconfig reveals all...  
	Most SoHo routers also have a www interface in them so you can run up a
browser on any of your local machines and http://192.168.n.1 (getting
the right value for n) into the router and can see what numbers it has
assigned.  (On my Dell with SuSE 10.0, both my wired ethernet and my
neighbor's wireless picked up and I can do this surfing ... my neighbor
never changed the default password).  
	Armed with this kind of data, you should be able to ping all hands.
This is health, welfare and troubleshooting things -- my Netgear router
occasionally freezes itself and a quick ping will tell whether it's the
router or the cable modem on the other side that's gone silly on me.


Once the above stuff is working right (you can ping everybody), you're
ready to move onto the next step.  Getting some sort of application to
run.  The Samba coaching you got from another poster is applicable.  
	I don't run Samba as matter of course (because my home is a Windows
Free Zone) other than for configuration testing.  Rather I run ssh and
tunnel several things through it like X, ftp.  ssh is unix-ese for
secure shell and is an encrypted application-layer tunnel between
machines.  So any traffic that goes through that tunnel is encrypted
between end systems.  That's sorta silly between two machines at home
(again, other than for calisthenics), but I also use it to reach my
machine at the office.  Nobody at Microsoft seems to have figured out
that it's the security of the _data_ that counts -- if you want ssh on
your Windows boxes, you have to get it from third parties like putty.  


In unix (incl the Linux variants) there are always >1 way to do all of 
this stuff

On Thu, 08 Dec 2005 14:56:55 -0500
Lee Underwood <[email protected]> wrote:

> I have just installed Mandriva (Mandrake) 10.01 on a Toshiba Portege 
> 7020CT. It works fine (excellent!, in fact) except I can't get the 
> network to run. I have two computers (1-XP, 1-Win2000) currently 
> connected through a D-Link router. The router is also connected to 
> the cable modem for Internet connection. The Toshiba connects fine to 
> the Internet through the router/cable modem but I can't get it to 
> connect to the other two computers. Any suggestions? (Go easy, I'm a
> newbie.)
> 
> Lee
> 
> 
> -- 
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.1.371 / Virus Database: 267.13.12/194 - Release Date:
> 12/7/2005
> 
> 
>