can't access LAN in kubuntu9.04 though internet is active.

Asked by Mr. MInhaj

i am using wired DSL connenction(pppoe). i am also in a local areal network.
when i try to enter network from kde kickoff application launcher>computer>network
it shows samba shares,when i click it then it shows "unable to find any workgroups in your local network, this might be caused by an enabled firewall". i don't know what firewall prevails in my system.please help.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

can you ping the systems on your lan by name?
can you ping the systems on your lan by ip?

Revision history for this message
Mr. MInhaj (imhell99) said :
#2

when i ping an ip or name in my network as example 192.168.70.118 it reports
"179 packets transmitted, 0 received, 100% packet loss, time 179058ms"

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

ok

can you please provide the output of

ifconfig; route

Thanks

Revision history for this message
Mr. MInhaj (imhell99) said :
#4

thanks to actionparsnip
the output of ifconfig; route is

eth0 Link encap:Ethernet HWaddr 00:1f:d0:65:2c:ef
          inet6 addr: fe80::21f:d0ff:fe65:2cef/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:25398 errors:0 dropped:0 overruns:0 frame:0
          TX packets:245 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2030350 (2.0 MB) TX bytes:37395 (37.3 KB)
          Interrupt:253 Base address:0x8000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:134 errors:0 dropped:0 overruns:0 frame:0
          TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7088 (7.0 KB) TX bytes:7088 (7.0 KB)

ppp0 Link encap:Point-to-Point Protocol
          inet addr:172.17.32.46 P-t-P:172.17.32.254 Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1460 Metric:1
          RX packets:176 errors:0 dropped:0 overruns:0 frame:0
          TX packets:207 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:87144 (87.1 KB) TX bytes:30231 (30.2 KB)

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.17.32.254 * 255.255.255.255 UH 0 0 0 ppp0
default * 0.0.0.0 U 0 0 0 ppp0
northdakota@GNU-NEMESIS:~/Documents$

thanks

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

eth0 has no address assigned to it so will never be used, if you give it an address that suits your network, when you access addresses from that mask then eth0 will be used. At the moment the only device with any addressing is ppp0.

Give eth0 an address and you can accss your stuff

Revision history for this message
Mr. MInhaj (imhell99) said :
#6

Thanks to actionparsnip,
i assigned an address in terminal according to my network, then "ifconfig" shows that address(192.168.70.215 with my MAC address) with inet6 address.
THe problem remains still.
Thanks.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#7

You may need to add a static route to say that any IP with address 192.168.x.x use eth0

route add -net 192.168.70.0 netmask 255.255.255.0 gw 192.168.70.1 eth0

you will need to change 192.168.70.1 id that is not your routers internal IP address.

Should then be ok.

Revision history for this message
Mr. MInhaj (imhell99) said :
#8

thanks to actionparsnip,
actually i couldn't understand completely what you said last.
can you please write the commands that i need.
thanks.

Revision history for this message
Mr. MInhaj (imhell99) said :
#9

when i put the command sudo route add -net 192.168.70.0 netmask 255.255.255.0 gw 192.168.70.1 eth0
then "SIOCADDRT: No such process" is displayed.
thanks.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#10

strange. Not sure then. If you look into the route command you can find out how to add a static route to make all traffic destined for 192.168.x.x go via eth0

Then it will work just fine

Can you help with this problem?

Provide an answer of your own, or ask Mr. MInhaj for more information if necessary.

To post a message you must log in.