Linux computer does not connect to windows-network.

pjotrb · 06-23-2009, 07:41 AM

hi,

I'm having a problem connecting my red-hat 7.2 machine to an existing windows network.
The lin18 (= name of the linux computer) doesn't show up in my network on the vista-computer.
Can anyone tell me why ??

ifconfig gives:
inet addr:192.186.2.240
UP BROADCAST RUNNING MUTICAST
RX packets: 0 errors 0 dropped 0 .. 0 .. 0
TX packets: 30 errors 0 .. 0 .. 0 .. 0
RX bytes: 0 TX bytes 3196

lsmod gives:
ipchains autofs 8139too ide-scsi scsi-mod ide-cd cdrom usb-uhci usbcore ext3 jbd

cat /etc/modules_conf:
...
alias eth0 8139too
...

ping 192.168.2.1 : Destination host unreachable

/etc/resolv_conf: nameserver 192.168.2.1

/etc/hosts:
127.0.0.1 localhost.localdomain localhost
192.168.2.240 lin18
192.168.2.247 desktop <= windows-vista computer

jomen · 06-23-2009, 08:53 AM

Quote:

ping 192.168.2.1 : Destination host unreachable

Which computer is that? DHCP-Server for both "lin18" and "desktop"?

Quote:

/etc/resolv_conf: nameserver 192.168.2.1

typo? (resolv_conf vs. resolv.conf)

ArcLinux · 06-23-2009, 09:42 AM

Is Samba running and setup correctly on the linux machine?

pjotrb · 06-24-2009, 01:03 AM

Quote:

Originally Posted by jomen

Which computer is that? DHCP-Server for both "lin18" and "desktop"?

typo? (resolv_conf vs. resolv.conf)

The 192.168.2.1 is my router

pjotrb · 06-24-2009, 01:05 AM

Quote:

Originally Posted by pjotrb

The 192.168.2.1 is my router

The router (192.186.2.1) should be the only dhcp-server

pj

pjotrb · 06-24-2009, 01:12 PM

Extra info: (the workgroup of my vista-pc = finofix)

samba deamons are running

smb.conf:
workgroup = finofix
[global]
hosts allow 192.168.2.1/192.168.2.256
interfaces = eth0
dns proxy = no

[lin18]
comment = lin18 share
path = /home/werkdir
force user = peter
force group = peter
guest ok = yes
readonly = no
force create mode = 0775
force directory mode = 0775

On my vista-machine using the explorer and then clicking on Network should show the lin18 ?

Please help someone ,

pjotrb

lazlow · 06-24-2009, 02:15 PM

Wouldn't 192.186.2.240 be on a different subnet than 192.168.2.1 ?

jomen · 06-24-2009, 03:47 PM

Would be a different subnet, of course, but I suppose it is another typo. See first post.
I'd first find out why the router, which is - from what I got - the dhcp-server for both the machines, is not ping'able from the linux machine.

pjotrb could check the default route of lin18 with

Code:

route -n

I also have a router which acts as the dhcp-server (just the subnet is 192.168.1.x instead of 192.168.2.x)
For me, ifconfig shows way more info than that given in the first post.

Code:

toy jochen # route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       127.0.0.1       255.0.0.0       UG    0      0        0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

toy jochen # ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:00:f0:92:9f:e6  
          inet addr:192.168.1.25  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::200:f0ff:fe92:9fe6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1660 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1847 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:708072 (691.4 KiB)  TX bytes:320394 (312.8 KiB)
          Interrupt:5 Base address:0x6800

pjotrb · 06-25-2009, 11:11 AM

Jomen,
My route -n is almost the same.
Difference: 172.0.0.0 has the gateway 0.0.0.0

My ifconfig eth0 also almost the same.
Difference: RXpackets: 0
RXbytes: 0

Is it a problem ?

jomen · 06-25-2009, 04:49 PM

pjotrb

Please be more careful!
It is almost certainly not this:

Quote:

Difference: 172.0.0.0 has the gateway 0.0.0.0

but this instead:

Quote:

Difference: 127.0.0.0 has the gateway 0.0.0.0

It is "almost the same" you say - please show us exactly!

You cannot even ping the router - which is giving out (via DHCP) the IP-adresses for your machines.
Are you sure your "lin18" linux machine has gotten an IP via DHCP from the router? (and not just a static one for instance...)

Quote:

Difference: RXpackets: 0
RXbytes: 0

looks as if the above guess might be correct.

I must admit that I'm already a little beyond my knowledge to be _really_ helpful here.
There certainly are people here who could help you out easily - when provided with enough information

pjotrb · 06-26-2009, 04:16 AM

hi jomen,
thanks for puttin the effort into it.

Your last remark about dhcp seems to be the problem.
When (1) /usr/sbin/netconfig : option "Use dynamic IP configuration (BOOTP/DHCP)"
and (2) service netwerk restart
then I get:
Bringing up interface eth0: Determining IP information for eth0 ... failed

So there seems to be a dhcp problem ?

jomen · 06-26-2009, 11:04 AM

Seems to be a dhcp problem, yes.
Could be the router not giving out an address (router misconfiguration), could be the linux machine not taking it (the dhcp-client), a firewall or even the cable itself.
The system logs should give you more clues.
If I got this right, then you are using Redhat 7.2 - which, from what I gather, is ancient - very old - from 2001.
That itself is not neccessarily a problem though.
But I have never used Redhat and know not where to look or what to do there.
It really ends here for me - sorry.