Dear Kyle,
You where right about the ip address not making a difference. I changed
it but with no luck.
I have not problem with using Windows WS_FTP and Linux, I can ping both
ways.
The ifconfig eth0 lists me out the normal information as expected.
I'm thinking that S.u.S.E. loading some other software which is grabbing
the port before nmbd gets hold of it. The reason I believe this is
because of the following. I removed Samba with YaST, and then rebooted
and then reinstalled Samba again with YaST, and immediately started smbd
-D and nmbd -D, and was able to make a connection, but when I rebooted,
something grabbed the port I believe.
This question about port 137 comes up infrequently, and I have not been
able to find an answer in dajanews or other news groups. I have found
the same question being asked about different flavors of Unix also.
Thanks for the help, if you have any further ideas I sure would
appreciate them.
Best Regards
Bryn Joynes
kyle wrote:
> Using 192.168.0.* shouldn't make a difference. Is your network card
> working with other applications. What do you get when you enter:
>
> ifconfig [network device]
>
> at the command line?
>
--
To reply to my e-mail, remove the REMOVE from my e-mail address. Thank
You.
Bryn Joynes
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
