Upgraded from slackware 10.2 to 11 now no samba conectivity and strange network issue

flavanoid · 10-11-2006, 11:42 AM

Ok... my brain hurts.

I just just upgraded from Slackware 10.2 with a 2.4 kernel to Slackware 11 with the 2.6.17.whatever kernel. M'kay so I follow the instructions from /UPGRADE.TXT and CHANGES_AND_HINTS.TXT, merge the *.new files in /etc, reboot and everything works flawlessly, all hardware is detected and whatnot. Then I go to access my samba shares and nothing. So I start investigating, checking configuration files, troubleshooting. I issue and get:

Code:

root@bobert/#:smbclient -L bobert
Password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.23c]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

bobert being my

Code:

netbios name = bobert

in smb.conf

Now after much searching/googling/diagnosing I'm starting to suspect that the problem lies deeper than with samba and there is something wrong with my network setup.

So I run some network tests and and some weird things are happening. Now let me start first by stating some facts:

My computers hostname is bobert and my domain is set as workgroup, so I'm "bobert.workgroup".
My domain used to be set as MediaShare(you will see how this is relevant in a little bit).

In my smb.conf file my workgroup = workgroup and my netbios name = bobert
I just wanted to tell you all this so domains/workgroups and hostnames/netbios names aren't misunderstood.

Now... Here's some weird things that are happening with my network:

When I ifconfig eth0 down, then ifconfig eth0 up, I don't have any network connectivity, though it seems to grab all necessary info, except a default gateway address.

When I ifconfig eth0 down, then issue /etc/rc.d/rc.inet1, or just issue dhcpcd then it comes back fully functional

issuing ./rc.inet1 or dhcpcd, creates a resolve.conf with the line "search MediaShare", and /etc/dhcpcd/dhcpcd.eth0.info has a line that says DOMAIN='MediaShare', I manually changed them to "workgroup" but the automatically get changed back. MediaShare being my OLD domain name remember!

When I run netconfig I get a message that says:

"SKIPPING MOST OF THE CONFIG PROCESS"
You do not seem to have TCP/IP installed, so all I can really
set up for you is your hostname/domainname. This won't mean
much since you're not on the network, but it will let you have
the hostname you prefer shown at the login prompt.

And I most certainly DO have TCP/IP installed! My internet works even when it tells me this!

All I really want to do is restore samba connectivity, but I don't think this will happen until these network issues are ironed out...

Please, please, please help me out here, I'll be happy to provide any info you may need! Thanks for everything and anything!

gbonvehi · 10-11-2006, 11:56 AM

I've just checked and netconfig tries to see if bin/telnet can be read to determine if you've tcpip package.
Quoted from netconfig:

Code:

if [ ! -d proc -a ! -d bin -a ! -d tmp ]; then # cheap, but it works :^)
 cd /
fi;

#lots of stuff omited by me (gbonvehi)

else
 if [ ! -r bin/telnet ]; then
  cat << EOF > $TMP/tempmsg
You do not seem to have TCP/IP installed, so all I can really
set up for you is your hostname/domainname. This won't mean
much since you're not on the network, but it will let you have
the hostname you prefer shown at the login prompt.
EOF
  dialog --title "SKIPPING MOST OF THE CONFIG PROCESS" \
--msgbox "`cat $TMP/tempmsg`" 8 67
 fi
fi

Check that the file exists and it's permissions, and re-run netconfig so it can fully setup your network.

I know you say you've it, but just in case, from http://packages.slackware.it

Code:

tcpip-0.17-i486-39 in slackware/n
/bin/telnet

flavanoid · 10-11-2006, 01:42 PM

Here ya go:

Code:

root@bobert:/bin# ls -l telnet
-rwxr-xr-x 1 root root 71984 2006-08-13 16:19 telnet

says it's there...but 2006-08-13, hmmm... I just just upgraded 2006-10-9ish... I would think the date would reflect that. I'm gonna uninstall/re-install tcp/ip and see what happens... I'll letcha know in a second what happens...

flavanoid · 10-11-2006, 01:49 PM

No Dice...

merchtemeagle · 10-14-2006, 06:00 AM

I have got the same problem.

flavanoid · 10-14-2006, 09:22 AM

Well here is my status if your're interested... I actually got so frustrated with it that I completely re-installed slackware. After I did that some things were better some things stay the same:

"root@bobert/#:smbclient -L bobert" would list the shares but clients still wouldn't connect, you could browse through the directory hierarchy, but it wouldn't display the contents of those directories...

The ifconfig eth0 up/down issue stayed the same...

netconfig works again...

resolve.conf and dhcpcd.eth0.info are getting their info from my router(which it's domain name is set at MediaShare I'm smacking myself for that one...)

However I've effectively solved the samba problem by uninstalling the package of samba included with slackware 11, and installing the package included with Slackware 10.2(which is 3.0.20 I believe). Samba works like normal again!

The crappy part about that is I probably could've just done that without completely re-installing slackware, but oh well, at least my samba is functioning again!