Can't set up ethernet connection with Windows XP

I’ve connected my openSUSE laptop with a Windows XP computer using an Ethernet cable that supports two-way traffic.

LAN settings on Windows XP
IP address: 192.168.5.1
Netmask: 255.255.255.0
Gateway and first DNS server: 192.168.5.2

LAN settings on openSUSE

http://i.imgur.com/gRAJV.png

What am I doing wrong?

Shouldn’t both be set to connect automatically in this situation?

So they should both be set to automatic config (DHCP)? If both computers ask each other which IP address it can use, doesn’t that create a conflict?

On Wed January 26 2011 12:36 pm, pdedecker wrote:

>
> I’ve connected my openSUSE laptop with a Windows XP computer using an
> Ethernet cable that supports two-way traffic.
>
> LAN_settings_on_Windows_XP
> IP address: 192.168.5.1
> Netmask: 255.255.255.0
> Gateway and first DNS server: 192.168.5.2
>
> LAN_settings_on_openSUSE
>
> [image: http://i.imgur.com/gRAJV.png]
>
> What am I doing wrong?
>
>
pdedecker;

Are you trying to have the Windows machine connect to the internet via the
OpenSuse machine? If so you will need two interfaces. This HowTo gives some
details.
http://opensuse.swerdna.org/suseics.html

On the other hand, if this is just for file/print sharing. All you need is
the IP and mask set. The gateway will always point to a router and DNS to a
DNS server. There is no indication that either of your machines is a DNS
server or acting as a router.

If there is no intervening switch between the machines you need whats called
a “crossover cable”. Perhaps thats what you meant with “supports two-way
traffic”. But it was not clear to me if you actually had a crossover cable.
Essentially all Ethernet cables support “two way traffic”. The only
difference between the two types is how the pins connect to the conductors.


P. V.
“We’re all in this together, I’m pulling for you.” Red Green

I want to set up a wired connection between my computer and a computer that will use RDP to connect with my computer. Both computers should ideally still be able to use their wireless card to surf the internet.

It’s a UTP CAT 5e cable. All I know is that I was able to connect two Windows machines with this cable using the trick I described earlier without the intervention of a switch. So I guess it’s a cross-over cable.

It makes sense if I think about it - otherwise I wouldn’t be able to send and receive traffic. :stuck_out_tongue:

On Wed January 26 2011 03:06 pm, pdedecker wrote:

>
> venzkep;2282766 Wrote:
>>
>> Are you trying to have the Windows machine connect to the internet via
>> the
>> OpenSuse machine?
> I want to set up a wired connection between my computer and a computer
> that will use RDP to connect with my computer. Both computers should
> ideally still be able to use their wireless card to surf the internet.

Why not just use the wireless for RDP?
>
> venzkep;2282766 Wrote:
>>
>> If there is no intervening switch between the machines you need whats
>> called
>> a “crossover cable”. Perhaps thats what you meant with “supports
>> two-way
>> traffic”. But it was not clear to me if you actually had a crossover
>> cable.
>>
> It’s a UTP CAT 5e cable. All I know is that I was able to connect two
> Windows machines with this cable using the trick I described earlier
> without the intervention of a switch. So I guess it’s a cross-over
> cable.
>
> venzkep;2282766 Wrote:
>>
>> Essentially all Ethernet cables support “two way traffic”.
>>
> It makes sense if I think about it - otherwise I wouldn’t be able to
> send and receive traffic. :stuck_out_tongue:
>
pdedecker;
In that case, do not even set a gateway or DNS server for the interfaces.
Make sure your firewalls are down while you are testing. They may be blocking
the traffic. Once you know you have a good connection then open appropriate
ports.

Make sure your applications are binding to the correct interface. See for
example the -I switch in “man ping”.

If you just get an ordinary patch cable, it is most likely a straight through
cable. On both ends pins 1,2,3 and 6 will be connected by the same color
conductors. On a crossover cable, you will see the conductors on pins 1 and
2 on end A connected to pins 3 and 6 on end B. And pins 3 and 6 on end A
connected to pins 1 and 2. Here’s a sketch:

end A pins conductor color end B pins
1 W/G 3
2 G 6
3 W/O 1
6 O 2

All the other pins/conductors are wired straight through.

W=white, G=green,O=orange

Pins 1 & 2 are designated for transmit and 3 & 6 for receive. Without a
switch/hub you need to connect the transmit pins of one end to the receive
pins of the other,

You need good eyes to see how the wires connect to the pins on a finished
cable, but it can be done.


P. V.
“We’re all in this together, I’m pulling for you.” Red Green

I already knew that the cable worked, because I used it to play Warsow from PC-to-PC. What I ended up doing is setting the XP’s settings to DHCP and using openSUSE’s DHCP server so that my computer could take the lead in setting up the network. Thanks to everyone who helped diagnose the problem! :slight_smile: