LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   smb/nmb daemons not running (https://www.linuxquestions.org/questions/linux-networking-3/smb-nmb-daemons-not-running-203580/)

skippuff54 07-10-2004 10:26 PM

smb/nmb daemons not running
 
i have smbd and nmbd enabled during boot, and i watch them supposedly start during the boot process but then i access them in swat and they're not running. when the computer shuts down it warns me that they're not running.

when in swat i hit start, restart, or start all, they still don't run.

i initially thought this was a firewall issue but it occurs with the firewall off, too.

they used to run fine and although i couldn't see my suse box in xp net neighborhood i could at least see my xp on the suse.

now nothing's working and it seems arbitrary.

what can i do to get these running?

adz 07-11-2004 12:23 AM

Can you just run nmbd and smbd manually? What output do you get?

motub 07-11-2004 07:14 AM

What is the output of dmesg? If the daemons do in fact start during the boot process, it will be recorded there; it will also be recorded if they try to start and fail, or starts and then stops for some reason.

Does your network work otherwise? Can you ping the other computer?

skippuff54 07-11-2004 12:58 PM

Quote:

Originally posted by motub
What is the output of dmesg?
Linux version 2.6.5-7.95-default (geeko@buildhost) (gcc version 3.3.3 (SuSE Linu
x)) #1 Thu Jul 1 15:23:45 UTC 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000003ec0000 (usable)
BIOS-e820: 0000000003ec0000 - 0000000003ef8000 (ACPI data)
BIOS-e820: 0000000003ef8000 - 0000000003f00000 (ACPI NVS)
BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
951MB vmalloc/ioremap area available.
0MB HIGHMEM available.
62MB LOWMEM available.
On node 0 totalpages: 16064
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 11968 pages, LIFO batch:2
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI disabled because your bios is from 2000 and too old
You can enable it with acpi=force
Built 1 zonelists
Kernel command line: root=/dev/hda1 desktop resume=/dev/hda2 splash=silent
bootsplash: silent mode.
Initializing CPU#0
PID hash table entries: 256 (order 8: 2048 bytes)
CKRM Initialization
...... Initializing ClassType<taskclass> ........
...... Initializing ClassType<socket_class> ........
CKRM Initialization done
Detected 565.127 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 58972k/64256k available (1963k kernel code, 4828k reserved, 688k data, 2
16k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1114.11 BogoMIPS
Security Scaffold v1.0.0 initialized
SELinux: Disabled at boot.
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Celeron (Coppermine) stepping 03
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Looking for DSDT in initrd ...No customized DSDT found in initrd!
Freeing initrd memory: 1154k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfda95, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Transparent bridge - 0000:00:1e.0
PCI: Using IRQ router PIIX/ICH [8086/2410] at 0000:00:1f.0
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Initial HugeTLB pages allocated: 0
VFS: Disk quotas dquot_6.5.1
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH: IDE controller at PCI slot 0000:00:1f.1
ICH: chipset revision 2
ICH: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALLlct15 07, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: Hewlett-Packard CD-Writer Plus 9300, ATAPI CD/DVD-ROM drive
hdd: CRD-8483B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 14668290 sectors (7510 MB) w/418KiB Cache, CHS=15522/15/63, UDMA(66)
hda: cache flushes not supported
hda: hda1 hda2
ide-floppy driver 0.99.newide
mice: PS/2 mouse device common for all mice
input: PC Speaker
serio: i8042 AUX port at 0x60,0x64 irq 12
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 8
NET: Registered protocol family 20
Resume Machine: resuming from /dev/hda2
Resuming from device hda2
Resume Machine: This is normal swap space
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
ReiserFS: hda1: found reiserfs format "3.6" with standard journal
ReiserFS: hda1: using ordered data mode
reiserfs: using flush barriers
ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 18,
max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda1: checking transaction log (hda1)
ReiserFS: hda1: replayed 3 transactions in 1 seconds
reiserfs: disabling flush barriers on hda1
ReiserFS: hda1: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Trying to move old root to /initrd ... failed
Unmounting old root
Trying to free ramdisk memory ... okay
Freeing unused kernel memory: 216k freed
Adding 498004k swap on /dev/hda2. Priority:42 extents:1
ReiserFS: hda1: Removing [2648 59711 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59616 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59609 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59585 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59584 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59580 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59572 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59571 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59570 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59530 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59511 0x0 SD]..done
ReiserFS: hda1: Removing [2648 59314 0x0 SD]..done
ReiserFS: hda1: Removing [2648 18662 0x0 SD]..done
ReiserFS: hda1: There were 13 uncompleted unlinks/truncates. Completed
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@uk.sistina.com
subfs 0.9
usbcore: registered new driver usbfs
usbcore: registered new driver hub
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
PCI: Found IRQ 3 for device 0000:01:0a.0
eth0: Davicom DM9102 at pci0000:01:0a.0, 00:80:ad:08:ef:e6, irq 3.
NET: Registered protocol family 17
hw_random hardware driver 1.0.0 loaded
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel i810 E Chipset.
agpgart: Maximum main memory to use for agp memory: 26M
agpgart: AGP aperture is 64M @ 0xf8000000
USB Universal Host Controller Interface driver v2.2
PCI: Found IRQ 9 for device 0000:00:1f.2
uhci_hcd 0000:00:1f.2: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: irq 9, io base 0000ef80
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.5-7.95-default uhci_hcd
usb usb1: SerialNumber: 0000:00:1f.2
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
PCI: Found IRQ 10 for device 0000:00:1f.5
PCI: Sharing IRQ 10 with 0000:00:1f.3
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 49333 usecs
intel8x0: clocking to 48000
powernow: This module only works with AMD K7 CPUs
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
lp0: using parport0 (polling).
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
eth0: no IPv6 routers present
Non-volatile memory driver v1.2
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
hdc: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 48X CD-ROM drive, 128kB Cache
SCSI subsystem initialized
st: Version 20040318, fixed bufsize 32768, s/g segs 256
BIOS EDD facility v0.13 2004-Mar-09, 1 devices found
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A

Quote:

Originally Posted by motub
Does your network work otherwise? Can you ping the other computer?

no and no. my network used to work; well, one way - i couldn't ever see the linux machine from the xp.

skippuff54 07-11-2004 01:09 PM

Quote:

Originally posted by adz
Can you just run nmbd and smbd manually? What output do you get?
i can try, and there doesn't seem to be any problem with it; they're just not running:

SUSEBOX:~ # smbd
SUSEBOX:~ # smbd start
SUSEBOX:~ # nmbd
SUSEBOX:~ # nmbd start
SUSEBOX:~ # /etc/init.d/smb start
Starting Samba SMB daemon done
SUSEBOX:~ # /etc/init.d/nmb start
Starting Samba NMB daemon - Warning: daemon already running. done

it warns me that nmbd is already started, yet in swat it tells me that it's not running.

Wiz22 07-11-2004 01:34 PM

dont know if it makes a difference on suse since im running slack-based distro but try;

# Killall smbd nmbd
# smbd -D
# nmbd -D

i use them as a "restart" on my samba just to put in here

motub 07-11-2004 01:41 PM

If you can't ping the other computer, I don't see how Samba is supposed to connect to it.

Well, eth0 is there, in any case:
Quote:

eth0: Davicom DM9102 at pci0000:01:0a.0, 00:80:ad:08:ef:e6, irq 3.
but I wonder if this might not be a problem:
Quote:

eth0: no IPv6 routers present
(is there supposed to be an IPv6 router involved?)

and I also wonder why there is no message actually bringing eth0 up (which would certainly explain why the network doesn't work).

What is the output of ifconfig (as root)?

Celettu 07-11-2004 02:05 PM

Since I have the exact same problem I thought I'd join....the samba daemons just won't start, not manually or via swat. I can ping localhost, I can ping my pc's name (galahad), and I can ping every IP adress in the network, but I can't connect to the workgroup or my wife's Win2K box when I use "guinevere" instead of her ipadress.

I followed every step in O'Reilly's book so my smb.conf is extremely simple, but should work. When I tried

smbclient -U% -L localhost

and that's when things went wrong:

Error connecting to 127.0.0.1 (Connection refused)
Connection to localhost failed

This is the output of ifconfig:

eth0 Link encap:Ethernet HWaddr 00:0C:76:96:38:EA
inet addr:192.168.123.103 Bcast:192.168.123.255 Mask:255.255.255.0
inet6 addr: fe80::20c:76ff:fe96:38ea/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4822 errors:0 dropped:0 overruns:0 frame:0
TX packets:5164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3218445 (3.0 Mb) TX bytes:627197 (612.4 Kb)
Interrupt:11 Base address:0x2000

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:3296 errors:0 dropped:0 overruns:0 frame:0
TX packets:3296 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:344549 (336.4 Kb) TX bytes:344549 (336.4 Kb)

San

michaelk 07-11-2004 02:09 PM

Check the logs for errors. There should be a log for nmbd and smbd.

motub 07-11-2004 02:15 PM

Celettu, you don't have quite the same problem, since you can ping, and skippuff54 can't, but your problem is easy to see.

127.0.0.1 is the loopback address to localhost (your own computer). The entire reason it exists is to give you a way to "connect" to your own computer on locally-run servers, like Webmin or Samba-Swat, without going through the network. So you might want to go into your /etc/hosts file and edit it so that in addition to localhost being listed at 127.0.0.1, it reads something like this:

127.0.0.1 localhost
<ip.address.of.guinevere> guinevere
<your.internal.ip.address> your_hostname

And are you sure that you set the workgroup name in /etc/samba/smb.conf to the same name as the one Windows is using? Is the Linux user trying to connect added to the authorised and known users by the Win2K administrator? Is the Linux user added and enabled (by root) to and in smbpasswd?

Celettu 07-11-2004 02:29 PM

[QUOTE]Originally posted by motub

>127.0.0.1 is the loopback address to localhost (your own computer). The entire reason it exists is to >give you a way to "connect" to your own computer on locally-run servers, like Webmin or >Samba-Swat, without going through the network. So you might want to go into your /etc/hosts file and >edit it so that in addition to localhost being listed at 127.0.0.1, it reads something like this:

>127.0.0.1 localhost
><ip.address.of.guinevere> guinevere
><your.internal.ip.address> your_hostname

Did this, and that worked fine.

However, the samba daemons still don't want to start.

>And are you sure that you set the workgroup name in /etc/samba/smb.conf to the same name as the >one Windows is using?

Yes. CAMELOT. It's detected in Yast, and I can browse my wife's win2K box again. My own SuSe 9.1 doesn't show up in the Workgroup though....

> Is the Linux user trying to connect added to the authorised and known users by the Win2K administrator.

Yes, and I can even log in giving the username and passwords of other users on the Windows machine.

>Is the Linux user added and enabled (by root) to and in smbpasswd?

No. I don't know how to do this :)

San

skippuff54 07-11-2004 02:32 PM

edit: ping of xp machine successful. don't know what i was doing wrong the first time.

Quote:

(is there supposed to be an IPv6 router involved?)
nope not at all.

Quote:

What is the output of ifconfig (as root)?[
eth0 Link encap:Ethernet HWaddr 00:80:AD:08:EF:E6
inet addr:24.88.127.149 Bcast:255.255.255.255 Mask:255.255.252.0
inet6 addr: fe80::280:adff:fe08:efe6/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:567373 errors:0 dropped:0 overruns:0 frame:0
TX packets:3048 errors:0 dropped:0 overruns:0 carrier:0
collisions:215 txqueuelen:1000
RX bytes:35242512 (33.6 Mb) TX bytes:467365 (456.4 Kb)
Interrupt:3 Base address:0xd800

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:1488 errors:0 dropped:0 overruns:0 frame:0
TX packets:1488 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:128065 (125.0 Kb) TX bytes:128065 (125.0 Kb)

skippuff54 07-11-2004 02:54 PM

Quote:

Originally posted by Wiz22
dont know if it makes a difference on suse since im running slack-based distro but try;

# Killall smbd nmbd
# smbd -D
# nmbd -D

i use them as a "restart" on my samba just to put in here

SUSEBOX:~ # Killall smbd nmbd
bash: Killall: command not found
SUSEBOX:~ # smbd -D
SUSEBOX:~ # nmbd -D

nothing happens when i run the last two.

Celettu 07-11-2004 03:40 PM

I think this is the problem, but how do I solve it?

galahad:/usr/sbin # testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[test]"
Loaded services file OK.
<b>ERROR: pid directory /var/run/samba does not exist</b>
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

# Global parameters
[global]
workgroup = CAMELOT
wins support = Yes

[test]
comment = For testing only, please
path = /home/San/test
read only = No
guest ok = Yes

San

skippuff54 07-11-2004 04:07 PM

same here:

SUSEBOX:~ # testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[users]"
Processing section "[groups]"
Processing section "[pdf]"
Processing section "[printers]"
Processing section "[print$]"
Processing section "[/shared]"
Loaded services file OK.
ERROR: pid directory /var/run/samba does not exist
Server role: ROLE_DOMAIN_PDC
Press enter to see a dump of your service definitions

also wondering what i can do.

Celettu 07-11-2004 04:26 PM

*smacks head*

I solved this with....hold on to your horses....

mkdir /var/run/samba

Incroyable mais vrai. Things work now.

San

skippuff54 07-11-2004 05:32 PM

wow. :p

mkdir /var/run/samba did the trick. now, all machines can see each other. my firewall is still disabled however so i need to make sure everything works properly with the firewall up.

thanks for the tip, celettu!

skippuff54 07-11-2004 08:18 PM

now that i can see the xp box on the suse, i can't access it:

Unknown error condition in stat: Connection refused.

stumped again.

motub 07-11-2004 08:53 PM

What does the Event Log on the XP box say? (Control Panel=>Administrative Tools=>Event log is there somewhere). What do the logs in /var/log/samba and /var/log/samba3 say?

skippuff54 07-12-2004 03:05 PM

Quote:

What do the logs in /var/log/samba and /var/log/samba3 say?
apparently those logs don't exist

skippuff54 07-12-2004 05:38 PM

Quote:

What does the Event Log on the XP box say?
and where in this event log should i be looking? under all three categories (application, security, system) i don't see any events committed by a computer other than the xp itself; under security, it says that there are no items to view.

motub 07-12-2004 07:25 PM

Well, I'm not the network guru who runs the Win2K box on our network, but I asked him, and the most likely place this would be recorded would be the security log... but the security log is not enabled by default (the Admin has to turn it on specifically). But it is supposed to record stuff like failed logins and such (which this would count as, I suppose--we'll test it in a minute).

You turn it on in Administrative Tools=>Local Security Settings=>Select a policy and check the "Failure" box to log... failed logins.

Hang on.... Yes, that works. I just tried to access the workgroup using an incorrect password, and two log entries appeared in the Security Log saying that... someone tried to log in to a specific account with the wrong password or username, and that there had been an authentication failure.

So you might want to try that, and see if it helps you track down what's going on on the Windows end, if Samba seems to be working correctly. I don't know why you wouldn't have any logs for Samba; that seems odd, but offhand I don't know what to do about it.

skippuff54 07-12-2004 08:04 PM

motub,

thanks so much for all your help.

i tried what you said on the xp end, but quite frustratingly, i've found that smb and nmb are not running again. testparm returns no errors. i'm now completely confused about what's going on with this system.

-smb and nmb are enabled to start during boot
-on boot, smb and nmb apparently start without a problem
-yast tells me that neither daemon is running
-starting manually doesn't work
-the network, which formerly worked, then didn't, then showed up but returned an unknown error, is back to not working
-testparm returns no errors
-i can connect to the internet without a problem

motub 07-12-2004 09:07 PM

You have 2 network cards in your PC (one connected to the modem, and one connected to the network) or only one (and you get Internet via routing from the XP box)?

'Cause I'm thinking that either 1) there's a problem with your NIC (the network NIC)-- but that won't be the case if you get Internet from the XP box;

2) there's a firewall on the network somewhere (can't begin to guess which box, but I'd vote for the XP box, especially if you did a Windows Update or installed a Service Pack) that is stopping/blocking the internal network connections.

Stabbing wildly in the dark, this sounds like everything starts out working, and then is stopped... by the network going down? Which might cause both the Samba daemons to stop (sounds odd, but on the other hand, there's no use in them running if there's no network, and they do re-read their settings every minute or so)?

Does SuSE install a firewall by default? Have you configured it, if so? Have you checked your physical network connections (are all the cables securely placed, etc)? Can you try another NIC (maybe the one you have is going wonky)? Have you checked the SuSE site to see if there's anything that might be a little bit broken with regards to network connections or their implementation of the Samba server daemons?

This is pretty bizarre.

Celettu 07-13-2004 02:13 AM

The SuSe 9.1 firewall blocks samba by default, so I had to turn it off. I'll have to configure it, but I haven't figured out yet and I'm behind a router anyway so it's not that urgent. But with the firewall switched on, the network isn't found.

skippuff54 07-13-2004 10:26 AM

Quote:

You have 2 network cards in your PC (one connected to the modem, and one connected to the network) or only one (and you get Internet via routing from the XP box)?
just one network card in the pc. i have cable internet that goes from the cable modem into an 8 port hub and then out to the three computers on my home network (2 xp's and the suse)

Quote:

2) there's a firewall on the network somewhere (can't begin to guess which box, but I'd vote for the XP box, especially if you did a Windows Update or installed a Service Pack) that is stopping/blocking the internal network connections.
i'll double-check when i get home (at work now).

Quote:

Stabbing wildly in the dark, this sounds like everything starts out working, and then is stopped... by the network going down? Which might cause both the Samba daemons to stop (sounds odd, but on the other hand, there's no use in them running if there's no network, and they do re-read their settings every minute or so)?
this is what really puzzles me. the samba daemons both supposedly start during boot without a hitch, but then i view them in yast and they're not running for some reason. i haven't made a single change since before they were running.

Quote:

Does SuSE install a firewall by default? Have you configured it, if so?
it does, and it was giving me issues before so i just turned it off. my network wasn't up long enough for me to test my connections with the firewall enabled.

Quote:

Have you checked your physical network connections (are all the cables securely placed, etc)?
everything is good to go.

Quote:

Can you try another NIC (maybe the one you have is going wonky)?
i have one here that i've been looking at the whole time; i'm going to give it a shot soon, maybe tonight. i just want to have explored every config option and possible problem.

Quote:

Have you checked the SuSE site to see if there's anything that might be a little bit broken with regards to network connections or their implementation of the Samba server daemons?
not thorougly so i suppose i will look around a little more.

Quote:

This is pretty bizarre. [/B]
indeed.


All times are GMT -5. The time now is 06:15 PM.