Samba - FC7 / Windows XP

Hi,

I've got FC7 and Samba installed on my server (192.168.1.100), with a
very simple smb.conf file; testparm and smbclient both work on the
server, but when I run net view on Windows, I get an "Error 53" (The
network path was not found).

Results from testparm:

Load smb config files from smb.conf
Processing section "[share1]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
workgroup = MIDEARTH
netbios name = MYNETBIOS
interfaces = lo, eth1, eth0
bind interfaces only = Yes
security = SHARE

[share1]
path = /data

smbclient -L localhost -U% and smbclient -L 192.168.1.100 -Uroot
%password and smbclient -L server -Uroot%password all give the same
result:

Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]

Sharename Type Comment
--------- ---- -------
share1 Disk
IPC$ IPC IPC Service (Samba 3.0.28-0.fc7)
Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]

Server Comment
--------- -------
MYNETBIOS Samba 3.0.28-0.fc7

Workgroup Master
--------- -------
MIDEARTH MYNETBIOS

I don't know if it's significant, but bearing in mind I can specify
server in the smbclient command (instead of 192.168.1.100), and I can
ping 192.168.1.100 from my Windows machines, but I can't ping server
from them (ping request could not find server...)

If anyone has got any ideas what's wrong, I'd be most grateful!

Thanks,
Chris

On Jan 19, 12:02*pm, CCW <c.c.w...@gmail.com> wrote:
> Hi,
>
> I've got FC7 and Samba installed on my server (192.168.1.100), with a
> very simple smb.conf file; testparm and smbclient both work on the
> server, but when I run net view on Windows, I get an "Error 53" (The
> network path was not found).
>
> Results from testparm:
>
> Load smb config files from smb.conf
> Processing section "[share1]"
> Loaded services file OK.
> Server role: ROLE_STANDALONE
> Press enter to see a dump of your service definitions
>
> [global]
> * * * * workgroup = MIDEARTH
> * * * * netbios name = MYNETBIOS
> * * * * interfaces = lo, eth1, eth0
> * * * * bind interfaces only = Yes
> * * * * security = SHARE
>
> [share1]
> * * * * path = /data
>
> smbclient -L localhost -U% and smbclient -L 192.168.1.100 -Uroot
> %password and smbclient -L server -Uroot%password all give the same
> result:
>
> Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]
>
> * * * * Sharename * * * Type * * *Comment
> * * * * --------- * * * ---- * * *-------
> * * * * share1 * * * * *Disk
> * * * * IPC$ * * * * * *IPC * * * IPC Service (Samba 3.0.28-0.fc7)
> Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]
>
> * * * * Server * * * * * * * Comment
> * * * * --------- * * * * * *-------
> * * * * MYNETBIOS * * * * * *Samba 3.0.28-0.fc7
>
> * * * * Workgroup * * * * * *Master
> * * * * --------- * * * * * *-------
> * * * * MIDEARTH * * * * * * MYNETBIOS
>
> I don't know if it's significant, but bearing in mind I can specify
> server in the smbclient command (instead of 192.168.1.100), and I can
> ping 192.168.1.100 from my Windows machines, but I can't ping server
> from them (ping request could not find server...)
>
> If anyone has got any ideas what's wrong, I'd be most grateful!
>
> Thanks,
> Chris

Can't ping Samba server from Windows by hostname or IP address? Are
firewalls active on your Windows PCs? You shouldn't ned the interface
values. What does the rest of the smb.conf look like.

Try the same smbclient command to attempt a connection from your Samba
server to the Windows PCs using either the Windows hostname or IP.
smbclient -L {windows host/IP} -Uroot


Check your /etc/nsswich.conf file and make sure the host line reads as
(it needs wins):
hosts: files dns wins

On Jan 19, 10:54 pm, tek <kevind...@yahoo.com> wrote:
> On Jan 19, 12:02 pm, CCW <c.c.w...@gmail.com> wrote:
>
>
>
> > Hi,
>
> > I've got FC7 and Samba installed on my server (192.168.1.100), with a
> > very simple smb.conf file; testparm and smbclient both work on the
> > server, but when I run net view on Windows, I get an "Error 53" (The
> > network path was not found).
>
> > Results from testparm:
>
> > Load smb config files from smb.conf
> > Processing section "[share1]"
> > Loaded services file OK.
> > Server role: ROLE_STANDALONE
> > Press enter to see a dump of your service definitions
>
> > [global]
> > workgroup = MIDEARTH
> > netbios name = MYNETBIOS
> > interfaces = lo, eth1, eth0
> > bind interfaces only = Yes
> > security = SHARE
>
> > [share1]
> > path = /data
>
> > smbclient -L localhost -U% and smbclient -L 192.168.1.100 -Uroot
> > %password and smbclient -L server -Uroot%password all give the same
> > result:
>
> > Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]
>
> > Sharename Type Comment
> > --------- ---- -------
> > share1 Disk
> > IPC$ IPC IPC Service (Samba 3.0.28-0.fc7)
> > Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]
>
> > Server Comment
> > --------- -------
> > MYNETBIOS Samba 3.0.28-0.fc7
>
> > Workgroup Master
> > --------- -------
> > MIDEARTH MYNETBIOS
>
> > I don't know if it's significant, but bearing in mind I can specify
> > server in the smbclient command (instead of 192.168.1.100), and I can
> > ping 192.168.1.100 from my Windows machines, but I can't ping server
> > from them (ping request could not find server...)
>
> > If anyone has got any ideas what's wrong, I'd be most grateful!
>
> > Thanks,
> > Chris
>
> Can't ping Samba server from Windows by hostname or IP address? Are
> firewalls active on your Windows PCs? You shouldn't ned the interface
> values. What does the rest of the smb.conf look like.
>
> Try the same smbclient command to attempt a connection from your Samba
> server to the Windows PCs using either the Windows hostname or IP.
> smbclient -L {windows host/IP} -Uroot
>
> Check your /etc/nsswich.conf file and make sure the host line reads as
> (it needs wins):
> hosts: files dns wins

Thanks for the reply, I've got as far as:

- I can ping the server from both windows machines by IP (server IP
is 192.168.1.100), but not by name (server)
- I can ping all Windows machines from the server by IP address
- smbclient -L 192.168.1.103 -Uroot gives the following result:

Domain=[HW] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment
--------- ---- -------
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
SharedDocs Disk
C Disk
Printer2 Printer EPSON Stylus C48 Series
ADMIN$ Disk Remote Admin
C$ Disk Default share
Printer Printer Microsoft Office Document Image
Writer
session request to 192.168.1.103 failed (Called name not present)
session request to 192 failed (Called name not present)
Domain=[HW] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Server Comment
--------- -------

Workgroup Master
--------- -------


- when I run net view on windows, I get: the following result:

SERVER NAME REMARK
--------------------------------------------------------------
\\HW
\\MH
\\SERVER Samba
3.0.28-0.fc7
The command completed successfully

- When I run

net view \\HW (or net view \\192.168.1.103)

I get a successful result (it shows the correct shared folder) - all
the Windows machines give the correct results from all other Windows
machines, but when I run

net view \\server (or net view 192.168.1.100)

I get a System 53 error (network path not found).

This is the same error I get when I run:

net use N: \\server\share1 (or net use N: \\192.168.1.100\share1)

- Network Neighbourhood (view workgroup computers) shows the Samba
computer (as well as the other Windows computers), but when I double
click on it, I get

\\Server is not accessible, You might not have permission to use this
network resource. Contact the administrator of the server to find out
if you have access permission. The network path was not found

I have added wins to the hosts line of my /etc/nsswitch.conf file, and
the problems still persist

My full smb.conf file is now:

[global]
workgroup = MIDEARTH
; netbios name = MYNETBIOS
; interfaces = lo eth1 eth0
; bind interfaces only = yes
security = share

[share1]
path = /data
read only = yes
guest ok = yes

I had read somewhere that because I'm using my fedora server as the
internet gateway (hence why I've got 2 ethernet cards), I needed the
interfaces line in my smb.conf file - is this true?
Can anyone also explain the difference between the smb and nmb
services - I've googled but can't find any explanation (although I
know I need to be running both)

Sorry for th long post, and thanks in advance for any help.
Chris

On Jan 20, 10:57*am, CCW <c.c.w...@gmail.com> wrote:
> On Jan 19, 10:54 pm, tek <kevind...@yahoo.com> wrote:
>
>
>
>
>
> > On Jan 19, 12:02 pm, CCW <c.c.w...@gmail.com> wrote:
>
> > > Hi,
>
> > > I've got FC7 and Samba installed on my server (192.168.1.100), with a
> > > very simple smb.conf file; testparm and smbclient both work on the
> > > server, but when I run net view on Windows, I get an "Error 53" (The
> > > network path was not found).
>
> > > Results from testparm:
>
> > > Load smb config files from smb.conf
> > > Processing section "[share1]"
> > > Loaded services file OK.
> > > Server role: ROLE_STANDALONE
> > > Press enter to see a dump of your service definitions
>
> > > [global]
> > > * * * * workgroup = MIDEARTH
> > > * * * * netbios name = MYNETBIOS
> > > * * * * interfaces = lo, eth1, eth0
> > > * * * * bind interfaces only = Yes
> > > * * * * security = SHARE
>
> > > [share1]
> > > * * * * path = /data
>
> > > smbclient -L localhost -U% and smbclient -L 192.168.1.100 -Uroot
> > > %password and smbclient -L server -Uroot%password all give the same
> > > result:
>
> > > Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]
>
> > > * * * * Sharename * * * Type * * *Comment
> > > * * * * --------- * * * ---- * * *-------
> > > * * * * share1 * * * * *Disk
> > > * * * * IPC$ * * * * * *IPC * * * IPC Service (Samba 3.0.28-0.fc7)
> > > Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]
>
> > > * * * * Server * * * * * * * Comment
> > > * * * * --------- * * * * * *-------
> > > * * * * MYNETBIOS * * * * * *Samba 3.0.28-0.fc7
>
> > > * * * * Workgroup * * * * * *Master
> > > * * * * --------- * * * * * *-------
> > > * * * * MIDEARTH * * * * * * MYNETBIOS
>
> > > I don't know if it's significant, but bearing in mind I can specify
> > > server in the smbclient command (instead of 192.168.1.100), and I can
> > > ping 192.168.1.100 from my Windows machines, but I can't ping server
> > > from them (ping request could not find server...)
>
> > > If anyone has got any ideas what's wrong, I'd be most grateful!
>
> > > Thanks,
> > > Chris
>
> > Can't ping Samba server from Windows by hostname or IP address? Are
> > firewalls active on your Windows PCs? You shouldn't ned the interface
> > values. What does the rest of the smb.conf look like.
>
> > Try the same smbclient command to attempt a connection from your Samba
> > server to the Windows PCs using either the Windows hostname or IP.
> > * smbclient -L {windows host/IP} -Uroot
>
> > Check your /etc/nsswich.conf file and make sure the host line reads as
> > (it needs wins):
> > *hosts: * * *files dns wins
>
> Thanks for the reply, I've got as far as:
>
> *- I can ping the server from both windows machines by IP (server IP
> is 192.168.1.100), but not by name (server)
> *- I can ping all Windows machines from the server by IP address
> *- smbclient -L 192.168.1.103 -Uroot gives the following result:
>
> Domain=[HW] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
>
> * * * * Sharename * * * Type * * *Comment
> * * * * --------- * * * ---- * * *-------
> * * * * IPC$ * * * * * *IPC * * * Remote IPC
> * * * * print$ * * * * *Disk * * *Printer Drivers
> * * * * SharedDocs * * *Disk
> * * * * C * * * * * * * Disk
> * * * * Printer2 * * * *Printer * EPSON Stylus C48 Series
> * * * * ADMIN$ * * * * *Disk * * *Remote Admin
> * * * * C$ * * * * * * *Disk * * *Default share
> * * * * Printer * * * * Printer * Microsoft Office Document Image
> Writer
> session request to 192.168.1.103 failed (Called name not present)
> session request to 192 failed (Called name not present)
> Domain=[HW] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
>
> * * * * Server * * * * * * * Comment
> * * * * --------- * * * * * *-------
>
> * * * * Workgroup * * * * * *Master
> * * * * --------- * * * * * *-------
>
> *- when I run net view on windows, I get: the following result:
>
> SERVER NAME * * * * * * * * * * * * * * * * * * * *REMARK
> --------------------------------------------------------------
> \\HW
> \\MH
> \\SERVER * * * * * * * * * * * * * * * * * * * * * * * *Samba
> 3.0.28-0.fc7
> The command completed successfully
>
> *- When I run
>
> net view \\HW (or net view \\192.168.1.103)
>
> I get a successful result (it shows the correct shared folder) - all
> the Windows machines give the correct results from all other Windows
> machines, but when I run
>
> net view \\server (or net view 192.168.1.100)
>
> I get a System 53 error (network path not found).
>
> This is the same error I get when I run:
>
> net use N: \\server\share1 (or net use N: \\192.168.1.100\share1)
>
> *- Network Neighbourhood (view workgroup computers) shows the Samba
> computer (as well as the other Windows computers), but when I double
> click on it, I get
>
> \\Server is not accessible, You might not have permission to use this
> network resource. Contact the administrator of the server to find out
> if you have access permission. The network path was not found
>
> I have added wins to the hosts line of my /etc/nsswitch.conf file, and
> the problems still persist
>
> My full smb.conf file is now:
>
> [global]
> * * * * workgroup = MIDEARTH
> ; * * * netbios name = MYNETBIOS
> ; * * * interfaces = lo eth1 eth0
> ; * * * bind interfaces only = yes
> * * * * security = share
>
> [share1]
> * * * * path = /data
> * * * * read only = yes
> * * * * guest ok = yes
>
> I had read somewhere that because I'm using my fedora server as the
> internet gateway (hence why I've got 2 ethernet cards), I needed the
> interfaces line in my smb.conf file - is this true?
> Can anyone also explain the difference between the smb and nmb
> services - I've googled but can't find any explanation (although I
> know I need to be running both)
>
> Sorry for th long post, and thanks in advance for any help.
> Chris- Hide quoted text -
>
> - Show quoted text -


By default Samba will query the kernel for the list of all active
interfaces and use any interfaces except 127.0.0.1 that are broadcast
capable.

The example below configures three network interfaces corresponding to
the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. The
netmasks of the latter two interfaces would be set to 255.255.255.0.

Default: interfaces =

Example: interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0


I don't know what "Fedora server" is. From your original post you
mentioned that your running version "3.0.28-0.fc7" of Samba. Open your
services tool to make sure the "nmb" service is selected and starts
for the run level you use. Levels 3 and 5 should be good enough.


Google smbd and nmbd:
nmbd is a server that understands and can reply to NetBIOS over IP
name service requests, like those produced by SMBD/CIFS clients such
as Windows 95/98, Windows NT and LanManager clients. It also
participates in the browsing protocols which make up the Windows
"Network Neighborhood" view.

smbd is the server daemon that provides filesharing and printing
services to Windows clients. The server provides filespace and printer
services to clients using the SMB (or CIFS) protocol. This is
compatible with the LanManager protocol, and can service LanManager
clients. These include MSCLIENT 3.0 for DOS, Windows for Workgroups,
Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh,
and smbfs for Linux.

On Jan 20, 6:55*pm, tek <kevind...@yahoo.com> wrote:
> On Jan 20, 10:57*am, CCW <c.c.w...@gmail.com> wrote:
>
>
>
>
>
> > On Jan 19, 10:54 pm, tek <kevind...@yahoo.com> wrote:
>
> > > On Jan 19, 12:02 pm, CCW <c.c.w...@gmail.com> wrote:
>
> > > > Hi,
>
> > > > I've got FC7 and Samba installed on my server (192.168.1.100), with a
> > > > very simple smb.conf file; testparm and smbclient both work on the
> > > > server, but when I run net view on Windows, I get an "Error 53" (The
> > > > network path was not found).
>
> > > > Results from testparm:
>
> > > > Load smb config files from smb.conf
> > > > Processing section "[share1]"
> > > > Loaded services file OK.
> > > > Server role: ROLE_STANDALONE
> > > > Press enter to see a dump of your service definitions
>
> > > > [global]
> > > > * * * * workgroup = MIDEARTH
> > > > * * * * netbios name = MYNETBIOS
> > > > * * * * interfaces = lo, eth1, eth0
> > > > * * * * bind interfaces only = Yes
> > > > * * * * security = SHARE
>
> > > > [share1]
> > > > * * * * path = /data
>
> > > > smbclient -L localhost -U% and smbclient -L 192.168.1.100 -Uroot
> > > > %password and smbclient -L server -Uroot%password all give the same
> > > > result:
>
> > > > Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]
>
> > > > * * * * Sharename * * * Type * * *Comment
> > > > * * * * --------- * * * ---- * * *-------
> > > > * * * * share1 * * * * *Disk
> > > > * * * * IPC$ * * * * * *IPC * * * IPC Service (Samba 3.0.28-0.fc7)
> > > > Domain=[MIDEARTH] OS=[Unix] Server=[Samba 3.0.28-0.fc7]
>
> > > > * * * * Server * * * * * * * Comment
> > > > * * * * --------- * * * * * *-------
> > > > * * * * MYNETBIOS * * * * * *Samba 3.0.28-0.fc7
>
> > > > * * * * Workgroup * * * * * *Master
> > > > * * * * --------- * * * * * *-------
> > > > * * * * MIDEARTH * * * * * * MYNETBIOS
>
> > > > I don't know if it's significant, but bearing in mind I can specify
> > > > server in the smbclient command (instead of 192.168.1.100), and I can
> > > > ping 192.168.1.100 from my Windows machines, but I can't ping server
> > > > from them (ping request could not find server...)
>
> > > > If anyone has got any ideas what's wrong, I'd be most grateful!
>
> > > > Thanks,
> > > > Chris
>
> > > Can't ping Samba server from Windows by hostname or IP address? Are
> > > firewalls active on your Windows PCs? You shouldn't ned the interface
> > > values. What does the rest of the smb.conf look like.
>
> > > Try the same smbclient command to attempt a connection from your Samba
> > > server to the Windows PCs using either the Windows hostname or IP.
> > > * smbclient -L {windows host/IP} -Uroot
>
> > > Check your /etc/nsswich.conf file and make sure the host line reads as
> > > (it needs wins):
> > > *hosts: * * *files dns wins
>
> > Thanks for the reply, I've got as far as:
>
> > *- I can ping the server from both windows machines by IP (server IP
> > is 192.168.1.100), but not by name (server)
> > *- I can ping all Windows machines from the server by IP address
> > *- smbclient -L 192.168.1.103 -Uroot gives the following result:
>
> > Domain=[HW] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
>
> > * * * * Sharename * * * Type * * *Comment
> > * * * * --------- * * * ---- * * *-------
> > * * * * IPC$ * * * * * *IPC * * * Remote IPC
> > * * * * print$ * * * * *Disk * * *Printer Drivers
> > * * * * SharedDocs * * *Disk
> > * * * * C * * * * * * * Disk
> > * * * * Printer2 * * * *Printer * EPSON Stylus C48 Series
> > * * * * ADMIN$ * * * * *Disk * * *Remote Admin
> > * * * * C$ * * * * * * *Disk * * *Default share
> > * * * * Printer * * * * Printer * Microsoft Office Document Image
> > Writer
> > session request to 192.168.1.103 failed (Called name not present)
> > session request to 192 failed (Called name not present)
> > Domain=[HW] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
>
> > * * * * Server * * * * * * * Comment
> > * * * * --------- * * * * * *-------
>
> > * * * * Workgroup * * * * * *Master
> > * * * * --------- * * * * * *-------
>
> > *- when I run net view on windows, I get: the following result:
>
> > SERVER NAME * * * * * * * * * * * * * * * * * * * *REMARK
> > --------------------------------------------------------------
> > \\HW
> > \\MH
> > \\SERVER * * * * * * * * * * * * * * * ** * * * * * * *Samba
> > 3.0.28-0.fc7
> > The command completed successfully
>
> > *- When I run
>
> > net view \\HW (or net view \\192.168.1.103)
>
> > I get a successful result (it shows the correct shared folder) - all
> > the Windows machines give the correct results from all other Windows
> > machines, but when I run
>
> > net view \\server (or net view 192.168.1.100)
>
> > I get a System 53 error (network path not found).
>
> > This is the same error I get when I run:
>
> > net use N: \\server\share1 (or net use N: \\192.168.1.100\share1)
>
> > *- Network Neighbourhood (view workgroup computers) shows the Samba
> > computer (as well as the other Windows computers), but when I double
> > click on it, I get
>
> > \\Server is not accessible, You might not have permission to use this
> > network resource. Contact the administrator of the server to find out
> > if you have access permission. The network path was not found
>
> > I have added wins to the hosts line of my /etc/nsswitch.conf file, and
> > the problems still persist
>
> > My full smb.conf file is now:
>
> > [global]
> > * * * * workgroup = MIDEARTH
> > ; * * * netbios name = MYNETBIOS
> > ; * * * interfaces = lo eth1 eth0
> > ; * * * bind interfaces only = yes
> > * * * * security = share
>
> > [share1]
> > * * * * path = /data
> > * * * * read only = yes
> > * * * * guest ok = yes
>
> > I had read somewhere that because I'm using my fedora server as the
> > internet gateway (hence why I've got 2 ethernet cards), I needed the
> > interfaces line in my smb.conf file - is this true?
> > Can anyone also explain the difference between the smb and nmb
> > services - I've googled but can't find any explanation (although I
> > know I need to be running both)
>
> > Sorry for th long post, and thanks in advance for any help.
> > Chris- Hide quoted text -
>
> > - Show quoted text -
>
> By default Samba will query the kernel for the list of all active
> interfaces and use any interfaces except 127.0.0.1 that are broadcast
> capable.
>
> The example below configures three network interfaces corresponding to
> the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. The
> netmasks of the latter two interfaces would be set to 255.255.255.0.
>
> Default: interfaces =
>
> Example: interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0
>
> I don't know what "Fedora server" is. From your original post you
> mentioned that your running version "3.0.28-0.fc7" of Samba. Open your
> services tool to make sure the "nmb" service is selected and starts
> for the run level you use. Levels 3 and 5 should be good enough.
>
> Google smbd and nmbd:
> nmbd is a server that understands and can reply to NetBIOS over IP
> name service requests, like those produced by SMBD/CIFS clients such
> as Windows 95/98, Windows NT and LanManager clients. It also
> participates in the browsing protocols which make up the Windows
> "Network Neighborhood" view.
>
> smbd is the server daemon that provides filesharing and printing
> services to Windows clients. The server provides filespace and printer
> services to clients using the SMB (or CIFS) protocol. This is
> compatible with the LanManager protocol, and can service LanManager
> clients. These include MSCLIENT 3.0 for DOS, Windows for Workgroups,
> Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh,
> and smbfs for Linux.- Hide quoted text -
>
> - Show quoted text -


Try these in your smb.conf

smb ports = 139
name resolve order = wins host bcast
os level = 34
preferred master = Yes
domain master = Yes
hosts allow = 192.168.1., 127.


You never mentioned if you have firewalls blocking NetBIOS ports 445
or 139 from your Windows machines.