In news:752563f406cae@uwe Feenz via HWKB.com wrote:
> Hi, Im trying to set up a network using a crossover cable. I have
> successfully managed to ping them and get replys, I can share files
> and folders, and I can connect to the 2nd comp on a remote connection
> and use the internet from there. I have used the IP 10.0.0.1 on the
> main comp and 10.0.0. 2 on the second, with a subnet mask of
Hi Feenz, where did You get the IP 10.* range from?
I've just checked this: Class A = only 1 private address!
And the relating extract from RFC 1918:
http://tools.ietf.org/html/rfc1918
===
3. Private Address Space
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
We will refer to the first block as "24-bit block", the second as
"20-bit block", and to the third as "16-bit" block. Note that (in
pre-CIDR notation) the first block is nothing but a single class A
network number, while the second block is a set of 16 contiguous
class B network numbers, and third block is a set of 256 contiguous
class C network numbers.
An enterprise that decides to use IP addresses out of the address
space defined in this document can do so without any coordination
with IANA or an Internet registry. The address space can thus be used
by many enterprises. Addresses within this private address space will
only be unique within the enterprise, or the set of enterprises which
choose to cooperate over this space so they may communicate with each
other in their own private internet.
As before, any enterprise that needs globally unique address space is
required to obtain such addresses from an Internet registry. An
enterprise that requests IP addresses for its external connectivity
will never be assigned addresses from the blocks defined above.
In order to use private address space, an enterprise needs to
determine which hosts do not need to have network layer connectivity
outside the enterprise in the foreseeable future and thus could be
classified as private. Such hosts will use the private address space
defined above. Private hosts can communicate with all other hosts
inside the enterprise, both public and private. However, they cannot
have IP connectivity to any host outside of the enterprise. While not
having external (outside of the enterprise) IP connectivity private
hosts can still have access to external services via mediating
gateways (e.g., application layer gateways).
All other hosts will be public and will use globally unique address
space assigned by an Internet Registry. Public hosts can communicate
with other hosts inside the enterprise both public and private and
can have IP connectivity to public hosts outside the enterprise.
Public hosts do not have connectivity to private hosts of other
enterprises.
=== End of RFC1918 extract
> 255.255.255.0. Then if i try running the wizzards on either of the
> comps, it changes all my manual settings and the computers cant see
> eachother. Any ideas of how i can stop this from happening will
I think this is normal because You did reflect the "class A" = _single_ IP.
Also You did not say anything about private DHCP relations
(and where do You got Your "temporary" addresses from).
This reflects the usage of DSL routers.
> please. Also I want to be able to access the internet from the
> second computer without having to do it remotely, is this possible
> and how? Im going nuts here...I think Ive gone and changed all my
> settings and now i dont really know where im at...Thanks all
Every IP must stand for its own and no duplicate must appear
that might be otherwise assigned. Your 10.* stands for "single"?
I prefer the "192.168.*" setup. Not any problem so far.
On Your setup only ONE PC should supply the I-Net connection.
This PC might then be shared by the other one using the same
connection (may be via a LAN setup).
Most Lan switches do not need to specify an "UPLINK" because
they figure it out by themselve. Thus "crossover" ist not the problem.
Please supply a detailed layout of Your connections by both PCs.
One can have an I-Net connection via DSL Router/Modem and the
other one connects to this via LAN using this same DSL Router.
What OS are You using? WinXP-sp2 should be no problem.
Others might require special setups.
Horst