[AuBrEy Online]

First I am having trouble networking FC4 to a Windows XP Pro based computer, using a crossover 5e networking cable ... I think the problem is the FC4 one .... I haven't a clue how to set it up, like in Widows!

Also Linux takes ages to boot up it goes though loads of prosceses .... I think this can be reduced!

Please help, someone!

[Tyler1989]

Your problem isn't with Fedora Core 4. Any networking between WIndows and Linux is a b-i-t-c-h. As for booting I never have had any problems on my machine how many megs did you assign to the boot process when you partitioned it?

[TheHeadFL]

Networking isn't that hard, come on... really...

AuBrEy, look for a "Samba configuration" GUI thing that is probably hiding in a GUI somewhere. Then you set it up with a name and workgroup, etc, just like a windows pc.

[mikepg]

I did what you mentioned above and when I brows the network only a windows network shows up. and there is nothing inside of that.

I have my /home/ folder shared and access to it everyone. It is set to read write and is visible..
What else do I have to do?

[AuBrEy Online]

I think our problems is .......

When I format my computer (Emacines) with a normal Windows I have to install drivers for the network to work.

Now I think that is the problem, I may have to find special Linux drivers for it.

[horndude]

ok here are the steps for linux networking hardware:
while logged in as root in a terminal:
lspci ------this will list all pci devices recognized by your system,check for the NIC your using

lsmod ---------this will list the kernel modules that are already loaded(kernel modules are like drivers in windows), check to see if one is loaded already for your NIC

no module loaded?load one....use modprobe or insmod to load one, not sure which one to use, look for it in /usr/src/linux~/drivers/net , you wont need to type the ".o" part, just its name without the ".o"

example insmod 3c509 or modprobe 3c509 will attempt to load the module for 3com509 series cards

now supposing the kernel already sees the NIC AND a module has been already loaded for it, then use ifconfig to set an IP address

example ifconfig eth0 192.168.0.2 up

if routing is needed add that with the route command:
route add default gw 192.168.0.1

the above two commands set up network sharing with a gateway @192.168.0.1

add appropriate dns#'s to /etc/resolv.conf and your done

some distro's like redhat and Fedora probably have a netconfig script, give it a try type netcon(tab key) for autocomplete and see what pops up, you will likely find a primitive GUI to do all of this

if using DHCP I cant help with that, they are all different with DHCP as how that is handled