Stuck in subnet 127.0.0.*

mcuddy · n00b Joined: 06 Dec 2004 Posts: 71

I am having trouble in two areas and have linked both to a network issue.

1) I am having difficulty printing to a network printer that gets new addresses via DHCP every so often. I have to set up the printer (or at least modify the address) each type the IP address is released and renewed... Then it works fine. When I set it up, I get a warning saying that the subnet I supply 192.168.1.* is not the system's subnet - which is 127.0.0.*. I have been working with printers through kde control panel.

2) I cannot find other computers on my workgroup (or any workgroup) with smb4k. I can access the internet fine, but cannot access computers or printers through smb4k.

As far as I can tell, my IP is assinged properly, ifconfig replies that it is 192.168.1.something. depending on what systems are on when I boot. The netmask is 255.255.255.0 and the nameserver is 192.168.1.1. The problem, however, is that I cannot access my workgroup (named workgroup, just to be complicated)

cyblord · Guru Joined: 22 May 2006 Posts: 424

I had the same problem.

check this out:

https://forums.gentoo.org/viewtopic-t-464695-highlight-internet+dhcp.html

mcuddy · n00b Joined: 06 Dec 2004 Posts: 71

The DHCP is working fine (or at least no errors), I can connect to the internet with no problems, so it's not my card.. any other ideas?

BTW:
speedyX menus # ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:41:23:37:53
inet addr:192.168.1.7 Bcast:255.255.255.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5743 errors:0 dropped:0 overruns:0 frame:0
TX packets:4530 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6457546 (6.1 Mb) TX bytes:640107 (625.1 Kb)
Interrupt:11 Base address:0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:124 errors:0 dropped:0 overruns:0 frame:0
TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6200 (6.0 Kb) TX bytes:6200 (6.0 Kb)

Is it possible smb4k and kprint are looking at lo instead of eth0?