TCP/IP settings when using cross over cable to connect 2 PCs

[Matt]

I guess this question is OS independent. I want to connect 2 PCs with a
cross over cable for file sharings. What should I change on TCP/IP
properties settings? I changed IP address to something like 220.0.0.1 in PC1
and 220.0.0.2 in PC2, and subnet mask are 255.255.255.0 on both PCs, because
I think it will make them in the same network, but still not working.

any ideas??

 

[Karl Burrows]

you need to change the default gateway to the address of the other machine.

I guess this question is OS independent. I want to connect 2 PCs with a
cross over cable for file sharings. What should I change on TCP/IP
properties settings? I changed IP address to something like 220.0.0.1 in PC1
and 220.0.0.2 in PC2, and subnet mask are 255.255.255.0 on both PCs, because
I think it will make them in the same network, but still not working.

any ideas??

 

[John Wunderlich]

I guess this question is OS independent. I want to connect 2 PCs
with a cross over cable for file sharings. What should I change on
TCP/IP properties settings? I changed IP address to something like
220.0.0.1 in PC1 and 220.0.0.2 in PC2, and subnet mask are
255.255.255.0 on both PCs, because I think it will make them in
the same network, but still not working.

any ideas??

"Auto" Speed/Duplex sensing in cross connections doesn't always work.
Go to Network Control panel or Device Manager, find the Advanced
settings for the NIC card and set both ends to agree on speed/duplex.
I would suggest 100/full if available.

HTH,
John

 

[John Wunderlich]

you need to change the default gateway to the address of the other
machine.

Since there are only two computers on the same subnet, the Gateway does
not come into play and may be left blank.

-- John

 

[Rick T]

I guess this question is OS independent. I want to connect 2 PCs with a
cross over cable for file sharings. What should I change on TCP/IP
properties settings? I changed IP address to something like 220.0.0.1 in PC1
and 220.0.0.2 in PC2, and subnet mask are 255.255.255.0 on both PCs, because
I think it will make them in the same network, but still not working.

any ideas??

Isn't DirectCableConnection sort of independent of Networking ? (you
need what's called a "crossover cable" though)



Rick

 

[unjpm]

see weather the system are self pinging (to test self ping
127.0.0.1) each system
then connect the cables to end terminal and then try to
ping
use private IP address like 192.168.1.1and subnet mask of
255.255.255.0
check the properties of network neighorhood properties
that file and printer sharing option is selected or not

 

[jb]

I would try using the private IP address that was posted
in an earlier reply. I had this same problem before and
as long as your NIC's are functioning properly, use the
private IP and keep the numbers in the last octet 1 and 2
respectively.

 

[Chuck]

I guess this question is OS independent. I want to connect 2 PCs with a
cross over cable for file sharings. What should I change on TCP/IP
properties settings? I changed IP address to something like 220.0.0.1 in PC1
and 220.0.0.2 in PC2, and subnet mask are 255.255.255.0 on both PCs, because
I think it will make them in the same network, but still not working.

any ideas??

Matt,

Your problem may not be related to your ip addressing. Please read
the tutorials in these websites, and see if there are additional
details which you may have omitted in your setup.
http://www.cablesense.com/
http://www.homenethelp.com/

If these websites are not useful, please provide more detail about
your network. What specifically is not working? Can't share files?
Can't connect to each other? Names of computer, make and model of
computer, name and version of operating system? Ipconfig data for
each computer: Start - Run - "ipconfig /all >c:\ipconfig.txt" - Open
c:\ipconfig.txt in Notepad, copy and paste into your next post.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Steve Winograd [MVP]]

I guess this question is OS independent. I want to connect 2 PCs with a
cross over cable for file sharings. What should I change on TCP/IP
properties settings? I changed IP address to something like 220.0.0.1 in PC1
and 220.0.0.2 in PC2, and subnet mask are 255.255.255.0 on both PCs, because
I think it will make them in the same network, but still not working.

any ideas??

If both computers run Windows 98, Me, 2000, or XP (not 95 or NT), you
don't need to assign IP addresses. They'll automatically assign
themselves compatible automatic private IP addresses in the
169.254.x.x range. There will be a delay of about 1 minute at boot
time while the assignment occurs.

If you don't want the delay, assign IP addresses in one of the ranges
reserved for private networks by the Internet Assigned Numbers
Authority:

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

Examples of pairs of private network addresses are:

10.0.0.1 and 10.0.0.2, subnet mask 255.0.0.0
172.16.0.1 and 172.16.0.2, subnet mask 255.240.0.0
192.168.0.1 and 192.168.0.2, subnet mask 255.255.255.0

I suspect that something not related to IP addresses is causing the
problem that you're seeing. Without more information about your
setup,including how you're trying to connect the computers and what
exactly happens when you do it, it isn't possible for someone else to
say.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Noel Paton]

DCC is done via the parallel port - networking is done via an ethernet card
(usually)
The OP would appear to be talking about using ethernet connections.....

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read on how to post messages to NG's

 

[Zakar Miklós]

These IP settings are right. If you can't ping the other host you should
check if you can ping the localhost. If localhost replies then you should
check the cabling. if localhost doesn't reply then it's may a NIC driver
problem.
If you can ping the other host you should check the workgroup membership.

br miklos