• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

tying windows to linux for simple file shares

I think there is some information in the Linux FAQ thread about SAMBA (assuming you have a network already setup).
 
To get Linux and Windows to talk, you will need Samba installed and configured per the FAQ instructions, but the fact that you added 'two NIC's' in your post makes me wonder if you're asking about one being a gateway as well as file sharing...
 
What I meant to say was that each machine has a NIC. Althought rite now I'm still at square one because my linux machine found my NIC on boot up, configured it, then failed when starting eth0.
 
Originally posted by: wxjunkie
What I meant to say was that each machine has a NIC. Althought rite now I'm still at square one because my linux machine found my NIC on boot up, configured it, then failed when starting eth0.
Well then Samba won't help even if you did install it 😉 What kind of NIC do you have in your *NIX box?
 
I'm a linux newbie unfortunately. I've managed to lose my bottom taskbar in Gnome, and I have no idea where the logs are stored😱
 
Originally posted by: wxjunkie
I'm a linux newbie unfortunately. I've managed to lose my bottom taskbar in Gnome, and I have no idea where the logs are stored😱

At a command line try:

ifconfig -a

That should give you a list of networking devices. Pay attention to what it says for eth0. Then try:

ifup eth0 or ifconfig eth0 up (I cant remember which of these commands is correct)

And see what kind of messages it gives you.

Logs should be in something like /var/logs
 
both failed

What exactly should I be looking at in the ifconfig -a eth0 results? I notice there's no inet addr assigned.
 
Originally posted by: wxjunkie
both failed

What exactly should I be looking at in the ifconfig -a eth0 results? I notice there's no inet addr assigned.

What failed?

You can try assigning one with ifconfig. "man ifconfig" for more information.
 
sounds like your using the wrong module. iirc you need 2.4.xx to use fa311/312

As root: lsmod

you should see natsemi there ( im prety sure the fa311 uses that, im using a fa312 and it uses it. )

if you dont, then run

modprobe natsemi

that should load ok, if it doesnt then it uses a different chip...or somethin else is wrong

if it loads ok ( no errors ) and your using dhcp then run 'dhcpcd eth0' and you should get an ip
 
Okay, Natsemi's in there now, the machine can see the NIC. However, when I ran dhcpcd eth0 nothing happened. It eventually timed out.

Also, I can't get my modem recognized either, it's a Creative Modemblaster.
 
Originally posted by: wxjunkie
Okay, Natsemi's in there now, the machine can see the NIC. However, when I ran dhcpcd eth0 nothing happened. It eventually timed out.

Also, I can't get my modem recognized either, it's a Creative Modemblaster.

Try giving it a static ip address. If that works, you have bad cables or a bad port.
 
Back
Top