MandrivaUsers.org > Network Config

MandrivaUsers.org > Advanced Topics > Networking

xboxboy

Jun 3 2008, 09:35 AM

Hi all,
I got 2008.1 up and running now, but problem is I can not connect to the net if the other computer on the network (running windows) is already on line. I had to turn off the router and turn it on again. I have tried to connect via MCC with out restarting the router, but it wont happen.

Any suggestions?

Thanks all

[moved from Hardware by spinynorman]

ianw1974

Jun 3 2008, 11:29 AM

How did you configure the network card originally? Did you configure with DHCP or did you assign an IP address? And if so, was the IP address you assigned the same one as the Windows machine?

xboxboy

Jun 4 2008, 09:43 AM

No I didn't assign an address. I just let the install do its thing.

ianw1974

Jun 4 2008, 11:16 AM

OK. Can you post the IP address assigned to the Windows machine, as well as the Mandriva machine when both machines are on. Then we can see if there is some sort of conflict.

To get this under Linux, open a console window, and then type:

CODE

su (enter root password when prompted)
ifconfig -a

then copy and paste the information here so we can see. For Windows, you can get via the network icon by the clock, or you can open a command prompt and type:

CODE

ipconfig /all

and we can then see what is configured here. Ideally, what I need are:

IP Address
Subnet Mask
Default Gateway
DNS address

to get DNS address from Linux:

CODE

cat /etc/resolv.conf

then copy and paste here.

xboxboy

Jun 7 2008, 09:18 AM

Thanks IanW. Is there anything about linux your not amazing with?????

Finally got back to my pc.

Here are the results for ifcong -a

CODE

eth0      Link encap:Ethernet  HWaddr
00:0C:76:26:0F:EE
          inet addr:192.168.1.3  Bcas
t:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:76ff:
fe26:fee/64 Scope:Link
          UP BROADCAST RUNNING MULTIC
AST  MTU:1500  Metric:1
          RX packets:251 errors:0 dro
pped:0 overruns:0 frame:0
          TX packets:303 errors:0 dro
pped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
0
          RX bytes:237115 (231.5 KiB)
  TX bytes:45548 (44.4 KiB)
          Interrupt:18 Base address:0
xb800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:2
55.0.0.0
          inet6 addr: ::1/128 Scope:H
ost
          UP LOOPBACK RUNNING  MTU:16
436  Metric:1
          RX packets:16 errors:0 drop                                                                                                                        ped:0 overruns:0 frame:0
          TX packets:16 errors:0 drop                                                                                                                        ped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1152 (1.1 KiB)  TX                                                                                                                         bytes:1152 (1.1 KiB)

and cat /etc/resolv.conf

CODE

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.1
search home

Thanks

ianw1974

Jun 7 2008, 06:47 PM

OK, so we have IP 192.168.1.3 assigned to this machine. I also see DNS is 192.168.1.1 which is your router. So, what we can try now is see if you can ping the router:

CODE

ping 192.168.1.1

now if you see nothing, that means it can't see it. If you get some results back, they should look like this if it's working:

CODE

[ian@esprit ~]$ ping 10.1.1.1
PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data.
64 bytes from 10.1.1.1: icmp_seq=1 ttl=64 time=1.32 ms
64 bytes from 10.1.1.1: icmp_seq=2 ttl=64 time=1.32 ms

that is just example from my machine. So, if you ping your router, you should get a similar type of reply. If not, then please post the results here so we can see what's going on.

If the Windows XP machine is on and it doesn't work, switch the XP machine off, then try again. Now, I then want you to power on the XP machine again, and get the IP from this machine - because if it isn't working, it could be that both these machines are trying to use the same IP address. As mentioned before, you can do this by clicking Start, and then Run, and then typing cmd and clicking OK. Then after this, type:

CODE

ipconfig /all

then you can post the info here so we can see if it's the same or different.

PS - thanks for the vote of confidence

xboxboy

Jun 11 2008, 12:29 PM

Hi Ian,
Am on line now, both the windows and linux boxes running. No drama today. So when I pinged the router all was good.

Its only sometimes it wont connect. I am guessing that there is an address clash.

Whats your theory? Should I assign a permanent address to my linux box????

ianw1974

Jun 11 2008, 07:15 PM

When you next get the clash, check both the IP's on each machine so we can see what is going wrong. I tend to allocate IP's statically rather than via DHCP - but if you do this, you have to make sure that the DHCP range that the router is giving doesn't include the IP that you are going to give manually to the Linux machine.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.