Mailinglist Archive: opensuse (4054 mails)

< Previous Next >
SPAM: Trouble Connecting to Server Retry
  • From: Eric Hines <eehines@xxxxxxxxxxx>
  • Date: Mon, 02 Jan 2006 14:03:49 -0600
  • Message-id: <>

My last got labeled SPAM; this removes (I think) the full IP addresses and links. (Side note--many of you are able to send these without getting tagged as spam. How are you doing this? I'm using Eudora and Thunderbird, and both are getting the SPAM labels.)


I'm having trouble connecting to my Samba server, and at this point I think I'm having name resolution problems, rather than Samba problems. The immediate symptoms are that I cannot see my Samba server in my Windows Network Neighborhood. Addresses are 192.168 unless otherwise noted.

I'm running SUSE 9.3 on the server, which is running Samba, a dhcp server (which seems to be running correctly--everyone gets an address when they ask for one), and a dns server. NIC .1.2 faces the Internet and gets there through a Linksys router/switch on .1.1. A Win2k PC sits on a .2.0 subnet; this subnet's NIC is set to .2.2 (the PC itself gets IP .2.9). A laptop dual bootable between SUSE 9.3 and WinXP sits on a .3.0 subnet; its NIC is set to .3.1 (the laptop gets .3.9). Both of these subnets must go through the .1.2 NIC to get to the Internet; all devices have easy access to the Internet. Both the XP laptop and the Win2k PC have the same symptoms, so I'll just talk about the PC.

.3.0 ----.3.1--samba/dns/dhcp--.2.2---.2.9
Linksys .1.1

My /etc/hosts file on the SUSE has the following entries:

.2.2 lserver01_test1_biz lserver01 lserver0
.1.2 sserver_test_biz sserver
.3.1 lserver02_test1_biz lserver02 [in all cases, "." instead of "_"]

IP Forwarding is turned on on the SUSE box, and ddns is enabled via the dhcp server (and is evidenced by the resolver cache on the PC). The Win2k's resolver cache has both forward lookup and reverse lookup files for sserver,, and the lserver0x and names. The PC's WINS is pointed at the .1.2, .2.2, and .3.1 NICs.

I can ping all by hostname, as well as by FQDN; although it appeared that I could not ping sserver by hostname only until I added sserver and its FQDN to the PC's host file (which it reads as though it were an lmhosts file). I say "it appeared" because it looked like the forward and reverse look up files for sserver appeared in the PC's resolver cache before I made this addition, but I got too fast with a ping test and contaminated that datum.

Just in case the Samba server is involved in this, I have the following entries in its smb.conf:

netbios name = lserver0
workgroup = astra_ent [of which both the laptop and PC are members]
interfaces = .2.0/24 .3.0/24 lo [I can't use eth1 and eth2 as SUSE 9.3 assigns the ethx to different NICs on different boot ups]
name resolve order = wins bcast hosts

Any advice would be greatly appreciated.

Eric Hines

There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action.
--Bertrand Russell

< Previous Next >