samba - Nov 2001 - SuSE Linux 7.3 and Windows Networking

Dear sir or madam,
i've got a problem connecting a Linux machine with a Windows Me internet and
file share. This problem i didn't got it with SuSE 7.2. From SuSE told me 
that have been some changes on SAMBA from 7.2 to 7.3. I'd like to ask you if
some one could help me. I am looking forward for your anwser.
Yours faithfuly,
Bill Giannakopoulos

P.S. I can see the Win PCs but i cannot connect,see or share their folders
P.S.2 when i am trying to connect i am getting the following message.SERVER 
is the name of the computer

GetSMBShare:smbclient -L SERVER -U% -W MSHOME -d3
added interface ip=192.168.0.2 bcast=192.168.0.255 nmask=255.255.255.0
Client started (version 2.2.1a).
resolve_lmhosts: Attempting lmhosts lookup for name SERVER<0x20>
resolve_hosts: Attempting host lookup for name SERVER<0x20>
Connecting to 192.168.0.1 at port 139
error connecting to 192.168.0.1:139 (Connection refused)
Connection to SERVER failed

What happens when you just try:
smbclient -L SERVER ?
Can windows machines see and connect to this ME machine?
Joel
On Wed, Nov 14, 2001 at 06:53:19PM +0200, Basily* Giannakopoulo*
wrote:
> Dear sir or madam,
> i've got a problem connecting a Linux machine with a Windows Me
internet and
> file share. This problem i didn't got it with SuSE 7.2. From SuSE told
me
> that have been some changes on SAMBA from 7.2 to 7.3. I'd like to ask
you if
> some one could help me. I am looking forward for your anwser.
> Yours faithfuly,
> Bill Giannakopoulos
> 
> P.S. I can see the Win PCs but i cannot connect,see or share their folders
> P.S.2 when i am trying to connect i am getting the following message.SERVER
> is the name of the computer
> 
> GetSMBShare:smbclient -L SERVER -U% -W MSHOME -d3
> added interface ip=192.168.0.2 bcast=192.168.0.255 nmask=255.255.255.0
> Client started (version 2.2.1a).
> resolve_lmhosts: Attempting lmhosts lookup for name SERVER<0x20>
> resolve_hosts: Attempting host lookup for name SERVER<0x20>
> Connecting to 192.168.0.1 at port 139
> error connecting to 192.168.0.1:139 (Connection refused)
> Connection to SERVER failed
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

There is not much detail here.
Have you walked through DIANGOSIS.txt?
Joel
On Fri, Nov 16, 2001 at 01:54:41PM +0200, Basily* Giannakopoulo*
wrote:
> I tried these and i get the anwsers:
> GetSMBShare:smbclient -L 192.168.0.1 -I 192.168.0.1 -U% -d3
> added interface ip=192.168.0.2 bcast=192.168.0.255 nmask=255.255.255.0
> Client started (version 2.2.1a).
> Connecting to 192.168.0.1 at port 139
> error connecting to 192.168.0.1:139 (Connection refused)
> Connection to 192.168.0.1 failed
> GetSMBShare:smbclient -L 192.168.0.3 -I 192.168.0.3 -U% -d3
> added interface ip=192.168.0.2 bcast=192.168.0.255 nmask=255.255.255.0
> Client started (version 2.2.1a).
> Connecting to 192.168.0.3 at port 139
> error connecting to 192.168.0.3:139 (No route to host)
> Connection to 192.168.0.3 failed
> GetSMBShare:smbclient -L 192.168.0.4 -I 192.168.0.4 -U% -d3
> added interface ip=192.168.0.2 bcast=192.168.0.255 nmask=255.255.255.0
> Client started (version 2.2.1a).
> Connecting to 192.168.0.4 at port 139
> timeout connecting to 192.168.0.4:139
> Connection to 192.168.0.4 failed
> 
> So i can understand that network is working but i have not set up SAMBA 
> right. Can you please help me!Please!
> Thank you for the consurn
> Bill Giannakopoulos