Re: kubuntu ethernet setup help, please

none wrote:

HI, I have been struggling with setting up ethernet between two kubuntu
computers.

Turn computers on.
Plug one end of a UTP crossover cable in each.
Watch the pretty green lights on the NICs.
Are they blinking ?
If so, congratulations - you have a functional Ethernet network.

Sarcasm aside, I suspect you mean *TCP/IP* networking.

Both of these computers are dual-boot with windows and I can
detect the network card in both through Kinfo center and through the
lshw command. I rebooted both into windows to check that the various
hardware was functioning and it was.

What a way to "check" ;-)
Do the following on each Linux box: run
#lspci -v
and check for the presence of your network cards, then run
#ifconfig -a
and check that there is at least an eth0 entry for each machine.
If there is, you have functioning hardware.

I'm certain that I have checked some box or incorrectly filled a field
somewhere.

Absolutely.
The *clue* is that you /have/ to fill some fields before you can get IP
networking to work.
You need to do at least 3 things:
1. assign an IP address to the interface,
2. set a subnet mask to define which network the machine belongs to, and
3. set a route or default gateway to the other box.

The last step is not explicitly necessary when both machines belong to the
same subnet.

Common values are: 192.168.x.y for the address, and 192.168.x.0 for the
network - where x may be anything you fancy.
The resulting subnet would be 255.255.255.0, or /24, depending on the tools
you use.

Because, what is easy for others is not working at all for me.
Is there any step by step guides available?

Dozens.

Are there any quick and easy ways to set this up.

Sure.
Assign 192.168.1.1 to Box #1, and 192.168.1.2 to Box #2.
Assign both a subnet mask of 255.255.255.0, and set the default gateway for
Box #2 (the one that *doesn't* connect to the Internet) to the address of
Box #1 - 192.168.1.1 again.

Now you can test IP connectivity by running:
#ping 192.168.1.2
from Box #1, or
#ping 192.168.1.1
from Box #2
Both should return replies - one per second, break it off with Control-C

I really only need some simple sharing of a
few folders and also share internet connection between the computer I am
writing from and the other.

That would be lesson #2 and #3 - Samba and iptables NAT, respectively.

One problem on the other is; that when I try to access Network Services
(which I believe is the way you access your network) I get a message
that either mdnsd can't be found.

You need IP connectivity first.

Any help would be greatly appreciated. I have set up ethernet networks
in windows but never really fully knew what I was doing

I understand completely.

but this seems even more difficult.

"Difficult" is a relative term.
Setting up a functioning "network" in Windows may seem easy, but then, as
you said, you can do that without having the slightest clue what you're
actually doing.
In Linux, you won't get away with that - you will certainly know what you're
doing, and why.
The obvious advantages being that you have at least a sporting chance of
fixing things when they break.

I also don't do engine work lol.

Not a clue what that is supposed to mean.
*You* want to configure networking, yes?
Then either you learn how or pay somebody who does know to do it for you.

Hmm I guess that means I did know what you meant.

--
All your bits are belong to us.

.

Relevant Pages

  • Re: Home Net Probs - AGAIN!!
    ... > the subnet mask was 255.0.0.0 as per the previous problem, ... > standard reboot and default back to factory settings - no change. ... rebooted the first two computers, and the network came back to normal. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Home Net Probs - AGAIN!!
    ... >> HELP CAREY!!! ... >> the subnet mask was 255.0.0.0 as per the previous problem, ... > rebooted the first two computers, and the network came back to normal. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Networks : Workgroups and Domains. How Do I Use Them?
    ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • Re: The Hard Problem for Behaviorists
    ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
    (sci.cognitive)
  • Re: The specified network name is nolonger available
    ... From your original post I assumed a larger network because you indicated ... a "router" between the computers. ... same assuming a class c network with the same subnet mask such as ... >> resolution problem. ...
    (microsoft.public.win2000.networking)