Re: Desiring to set up Windows Vista and Linux Fedora Core 4

[Barry L. Bond]

Greetings!

     Tonight is unfortunately the first small bit of time I've had to even
try to get Samba configured between my Vista and my Linux FC4.  (My mother
as well as my extremely limited home time dealing with important things
are my main delays.)

     It's not going well.  :-)

     I have added hosts allow with 192.168.1 and 192.168.2.  I have
experimented with a few things.  I have looked at
http://forums.fedoraforum.org/showthread.php?t=2556 and even read
something about making the network communication in Vista be LM as well as
NTLM...

     Okay, let me ask one basic question at a time.

     I "was thinking" that I didn't have to actually mount samba
(smbmount) in the past, back years ago when I used it with VMWare and
Windows 98.  (I was thinking that the smdb/nmdb daemons just did what was
needed.)

     I will be fine if I just am able to submit a print job from the
Windows/Vista to the Linux HP9110 printer.  I will be fine if I just
transfer any files, either direction, by accessing my host filesystem via
Explorer in Windows.  (This is how I did it, years ago, with Windows 98 in
VMWare.)

     I am thinking that I do NOT need to add to /etc/fstab, or smbmount
anything from the Linux side.  Do you agree?

     Barry

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Michael Wood-8]

Hi

2009/10/3 Barry L. Bond <bbond@...>:
[...]
>     I have added hosts allow with 192.168.1 and 192.168.2.  I have
> experimented with a few things.  I have looked at
> http://forums.fedoraforum.org/showthread.php?t=2556 and even read

This fedoraforums thread is about connecting to Windows from the Linux
machine.  Based on what you say below it looks like you want the
opposite, i.e. connect from the Windows machine to the Linux machine
in order to print.

> something about making the network communication in Vista be LM as well as
> NTLM...

You might want to add a bit more context for people who did not see or
do not remember the rest of this thread.

From what you say above, I assume that the Windows machine is on
either 192.168.1.x or 192.168.2.x networks?  Don't forget to use a
full stop after them like:

hosts allow 192.168.1. 192.168.2.

or you could write it like:

hosts allow 192.168.1.0/24 192.168.2.0/24

>     Okay, let me ask one basic question at a time.
>
>     I "was thinking" that I didn't have to actually mount samba
> (smbmount) in the past, back years ago when I used it with VMWare and
> Windows 98.  (I was thinking that the smdb/nmdb daemons just did what was
> needed.)

I'm not entirely sure what you mean by this, but smbmount is for
letting the Linux box mount (connect to) a Windows (or Samba) share on
another machine.  It seems that what you want is the other way around.
 i.e. to connect to Samba on the Linux machine from the Windows
machine.

>     I will be fine if I just am able to submit a print job from the
> Windows/Vista to the Linux HP9110 printer.  I will be fine if I just
> transfer any files, either direction, by accessing my host filesystem via
> Explorer in Windows.  (This is how I did it, years ago, with Windows 98 in
> VMWare.)
>
>     I am thinking that I do NOT need to add to /etc/fstab, or smbmount
> anything from the Linux side.  Do you agree?

Yes, if you want to connect to Samba from the Windows machine then you
do not have to do anything with /etc/fstab or smbmount.

What does your smb.conf look like?  And what happens when you try to
connect/print from the Windows machine?  What errors to you get?

--
Michael Wood <esiotrot@...>
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Gary Dale-2]

Barry L. Bond wrote:

> Greetings!
>
>      Tonight is unfortunately the first small bit of time I've had to even
> try to get Samba configured between my Vista and my Linux FC4.  (My mother
> as well as my extremely limited home time dealing with important things
> are my main delays.)
>
>      It's not going well.  :-)
>
>      I have added hosts allow with 192.168.1 and 192.168.2.  I have
> experimented with a few things.  I have looked at
> http://forums.fedoraforum.org/showthread.php?t=2556 and even read
> something about making the network communication in Vista be LM as well as
> NTLM...
>
>      Okay, let me ask one basic question at a time.
>
>      I "was thinking" that I didn't have to actually mount samba
> (smbmount) in the past, back years ago when I used it with VMWare and
> Windows 98.  (I was thinking that the smdb/nmdb daemons just did what was
> needed.)
>
>      I will be fine if I just am able to submit a print job from the
> Windows/Vista to the Linux HP9110 printer.  I will be fine if I just
> transfer any files, either direction, by accessing my host filesystem via
> Explorer in Windows.  (This is how I did it, years ago, with Windows 98 in
> VMWare.)
>
>      I am thinking that I do NOT need to add to /etc/fstab, or smbmount
> anything from the Linux side.  Do you agree?
>
>      Barry
>
>  

I'd begin by upgrading to something more recent than Fedora Core 4. I
believe there are some issues that Vista introduced that required some
changes in Samba (I may be wrong on this, but I suspect upgrading to
something more recent is still a good idea). At the very least, see if
there is a backport for a more recent version of Samba to FC4.

It sounds like you are using FC4 as a file & print server. All you need
to do on it is share the resources (folders and printers) and set up the
permissions and accounts (if required).

You don't mention which version of Vista you are using, and I don't know
if they crippled certain versions like they did with XP to prevent them
from joining domains. However, if you can join Vista to a domain,
install and use SWAT to set up Samba as a domain controller and use it
to log in from Vista.


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Barry L. Bond]

Hi Michael!

     Thank you for your fast reply!

On Sat, Oct 03, 2009 at 04:35:50PM +0200, Michael Wood wrote:

> From what you say above, I assume that the Windows machine is on
> either 192.168.1.x or 192.168.2.x networks?  Don't forget to use a
> full stop after them like:
>
> hosts allow 192.168.1. 192.168.2.
>
> or you could write it like:
>
> hosts allow 192.168.1.0/24 192.168.2.0/24

     Hmmmm... I have "hosts allow = 192.168.1., 192.168.2., 127."

     I have a space between the IP address excerpts (I presume that's what
you mean by the full stop), though I also have a comma.  I'll remove the
commas...

> What does your smb.conf look like?  And what happens when you try to
> connect/print from the Windows machine?  What errors to you get?

     Here is my current smb.conf file:

<<>>
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2009/10/03 00:37:16

# Global parameters
[global]
        server string = Windows in Linux - VMware
        interfaces = eth0, vmnet1, vmnet8
        guest account = barry
        username map = /etc/samba/smbusers
        log file = /var/log/samba/%m.log
        max log size = 50
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        printcap name = /etc/printcap
        preferred master = Yes
        dns proxy = No
        idmap uid = 16777216-33554431
        idmap gid = 16777216-33554431
        guest ok = Yes
        hosts allow = 192.168.1. 192.168.2. 127.
        cups options = raw

[homes]
        comment = Home Directories
        read only = No

[printers]
        comment = All Printers
        path = /var/spool/samba
        printable = Yes
        browseable = No

[HostFS]
        comment = VMware host filesystem
        path = /
        read only = No

[barry]
        path = /home/barry
        valid users = barry
        read only = No

[HP9110]
        comment = Hewlett-Packard OfficeJet 9110
        path = /var/spool/samba
        read only = No
        printable = Yes
        printer name = HP9110
        oplocks = No
        share modes = No
<<>>

     There are a LOT of comments in my original smb.conf file, but since I
tried to modify a couple of things using SWAT, I see it removed the
comments.

     Much of what is in this file is what I had, years ago, when I had
Windows 98 which I could access through VMware, which was running on my
Linux system.  (I want to do exactly what I did with that, be able to
submit a print job or transfer a file either direction.)

     After I removed the comments in my "hosts allow" line, I typed
"service smb restart" in my root window:

<<>>
[root@barrycon samba]# service smb restart
Shutting down SMB services:                                [  OK  ]
Shutting down NMB services:                                [  OK  ]
Starting SMB services:                                     [  OK  ]
Starting NMB services:                                     [  OK  ]
<<>>

     On the Windows computer, I clicked Start and then Network.

     I double-clicked OFFICE-WINDOWS.

     I double-clicked "Add a Printer".

     Then an "Add a printer" came up near the top of my explorer, after
Organize and Views.

     Clicking "Add a printer", I choose "Add a network, wireless or
Bluetooth printer" in the dialog box that comes up. ("Add a local printer"
is the only other choice here.)

     It says "Searching for available printers..."

     After a delay, it says "No printers were found."

     I click "The printer that I want isn't listed" and out of the three
choices ("Browse for a printer", "Select a shared printer by name" and
"Add a printer using a TCP/IP address or hostname"), I choose the second
one, as the printer is connected to my Linux system with a parallel port,
and it does not have an IP address.

     I click in the "text box" and type "\\barrycon\hp9110"

     The hostname is barrycon (and that is exactly what worked in the
Windows 98/VMware I did years ago), and if I type "lpstat -v" the first
line says "device for HP9110:".

     Another dialog box says "Connecting to hp9110 on barrycon" and after
a short delay it says "Windows cannot connect to the printer.  The server
print spooler service is not running.  Please restart the spooler on the
server or restart the server machine."

     Michael, in the extremely limited time I've given this, I don't
appear to be communicating at all.  I thank you that you and others are
trying to help me, so I believe I will just see if you or anyone else
replies before I mess something up worse!  :-)

     Thank you again!

     Barry

--
Barry L. Bond                      | http://home.roadrunner.com/~os9barry
Software Engineer, ITT Corporation | (My personal home web page, last
                                   | updated February 17, 2005)
                                   |
bbond @ cfl.rr.com <- personal     |  Re-Vita Products:
Barry.Bond @ ITT.com <- Work ONLY  |  http://www.re-vita.net/barrybond
                                   |  Re-Vita Distributor Information
Home office:  407-382-2815         |  http://www.re-vita.net/barrybond-2
Work:         321-494-5627 (Work)  |  Toll free order:  1-888-820-5531
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Barry L. Bond]

Hi Gary!

     Thank you for your reply and help!

>I'd begin by upgrading to something more recent than Fedora Core 4. I
>believe there are some issues that Vista introduced that required some
>changes in Samba (I may be wrong on this, but I suspect upgrading to
>something more recent is still a good idea). At the very least, see if
>there is a backport for a more recent version of Samba to FC4.

     I just now read a previous post from you that also indicated concerns
with my running FC4, that I missed before.

     I am afraid that right now I just don't have any time for the
computer stuff at home I used to have so well set up and caught up.  :-(

     Right now, given that there are very important things I need to get
to each week that I don't get to (you can see the one time a week that I
may have a half hour or so to revisit my strong desire to be able to print
from Windows, even though I don't need to often!), I'm afraid I'm in an
"if it works, don't fix it" mode...

     By "backport" do you mean a more recent version of Samba that will
work in FC4?

>It sounds like you are using FC4 as a file & print server. All you need
>to do on it is share the resources (folders and printers) and set up the
>permissions and accounts (if required).

     On the Windows, I did do some things along this line (setting up
sharing) last week...

>You don't mention which version of Vista you are using, and I don't know
>if they crippled certain versions like they did with XP to prevent them
>from joining domains. However, if you can join Vista to a domain,
>install and use SWAT to set up Samba as a domain controller and use it
>to log in from Vista.

     If I go to Control Panel and double click System, it says this:

<<>>
Windows edition..........

      Windows Vista Ultimate
      Copyright 2007 Microsoft Corporation.  All rights reserved.
      Service Pack 2
<<>>

     Does that tell you what you were desiring?  (I don't know Windows
very well.)  :-)

     Last week, I did read something that was along the lines of Vista
communicating with Samba.  I have already forgotten what they called it,
but I did find (with very explicit instructions posted by someone where I
was reading about that, in a Microsoft forum) and I checked a different
thing, to see whether that would work...

     Gary, I really appreciate your help.  On terminology, how do I join
Vista to a domain?

     Thank you!
     Barry
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Bruno MACADRE]

Barry L. Bond a écrit :

> Hi Michael!
>
>      Thank you for your fast reply!
>
> On Sat, Oct 03, 2009 at 04:35:50PM +0200, Michael Wood wrote:
>
>  
>> From what you say above, I assume that the Windows machine is on
>> either 192.168.1.x or 192.168.2.x networks?  Don't forget to use a
>> full stop after them like:
>>
>> hosts allow 192.168.1. 192.168.2.
>>
>> or you could write it like:
>>
>> hosts allow 192.168.1.0/24 192.168.2.0/24
>>    
>
>      Hmmmm... I have "hosts allow = 192.168.1., 192.168.2., 127."
>
>      I have a space between the IP address excerpts (I presume that's what
> you mean by the full stop), though I also have a comma.  I'll remove the
> commas...
>
>  
>> What does your smb.conf look like?  And what happens when you try to
>> connect/print from the Windows machine?  What errors to you get?
>>    
>
>      Here is my current smb.conf file:
>
> <<>>
> # Samba config file created using SWAT
> # from 127.0.0.1 (127.0.0.1)
> # Date: 2009/10/03 00:37:16
>
> # Global parameters
> [global]
> server string = Windows in Linux - VMware
> interfaces = eth0, vmnet1, vmnet8
> guest account = barry
> username map = /etc/samba/smbusers
> log file = /var/log/samba/%m.log
> max log size = 50
> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> printcap name = /etc/printcap
> preferred master = Yes
> dns proxy = No
> idmap uid = 16777216-33554431
> idmap gid = 16777216-33554431
> guest ok = Yes
> hosts allow = 192.168.1. 192.168.2. 127.
> cups options = raw
>
> [homes]
> comment = Home Directories
> read only = No
>
> [printers]
> comment = All Printers
> path = /var/spool/samba
> printable = Yes
> browseable = No
>
> [HostFS]
> comment = VMware host filesystem
> path = /
> read only = No
>
> [barry]
> path = /home/barry
> valid users = barry
> read only = No
>
> [HP9110]
> comment = Hewlett-Packard OfficeJet 9110
> path = /var/spool/samba
> read only = No
> printable = Yes
> printer name = HP9110
> oplocks = No
> share modes = No
> <<>>
>
>      There are a LOT of comments in my original smb.conf file, but since I
> tried to modify a couple of things using SWAT, I see it removed the
> comments.
>
>      Much of what is in this file is what I had, years ago, when I had
> Windows 98 which I could access through VMware, which was running on my
> Linux system.  (I want to do exactly what I did with that, be able to
> submit a print job or transfer a file either direction.)
>
>      After I removed the comments in my "hosts allow" line, I typed
> "service smb restart" in my root window:
>
> <<>>
> [root@barrycon samba]# service smb restart
> Shutting down SMB services:                                [  OK  ]
> Shutting down NMB services:                                [  OK  ]
> Starting SMB services:                                     [  OK  ]
> Starting NMB services:                                     [  OK  ]
> <<>>
>
>      On the Windows computer, I clicked Start and then Network.
>
>      I double-clicked OFFICE-WINDOWS.
>
>      I double-clicked "Add a Printer".
>
>      Then an "Add a printer" came up near the top of my explorer, after
> Organize and Views.
>
>      Clicking "Add a printer", I choose "Add a network, wireless or
> Bluetooth printer" in the dialog box that comes up. ("Add a local printer"
> is the only other choice here.)
>
>      It says "Searching for available printers..."
>
>      After a delay, it says "No printers were found."
>
>      I click "The printer that I want isn't listed" and out of the three
> choices ("Browse for a printer", "Select a shared printer by name" and
> "Add a printer using a TCP/IP address or hostname"), I choose the second
> one, as the printer is connected to my Linux system with a parallel port,
> and it does not have an IP address.
>
>      I click in the "text box" and type "\\barrycon\hp9110"
>
>      The hostname is barrycon (and that is exactly what worked in the
> Windows 98/VMware I did years ago), and if I type "lpstat -v" the first
> line says "device for HP9110:".
>
>      Another dialog box says "Connecting to hp9110 on barrycon" and after
> a short delay it says "Windows cannot connect to the printer.  The server
> print spooler service is not running.  Please restart the spooler on the
> server or restart the server machine."
>
>      Michael, in the extremely limited time I've given this, I don't
> appear to be communicating at all.  I thank you that you and others are
> trying to help me, so I believe I will just see if you or anyone else
> replies before I mess something up worse!  :-)
>
>      Thank you again!
>
>      Barry
>
>  

Hi,

    Is your samba server a wins server (i don't see it in your smb.conf)
? Or have you a wins server on your network ?
    Have you try to put barrycon's IP address instead of its name ?
(something like \\Barrycon_IP\HP9110) ?

Bruno
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Michael Wood-8]

Hi Barry

2009/10/10 Barry L. Bond <bbond@...>:

> Hi Michael!
>
>     Thank you for your fast reply!
>
> On Sat, Oct 03, 2009 at 04:35:50PM +0200, Michael Wood wrote:
>
>> From what you say above, I assume that the Windows machine is on
>> either 192.168.1.x or 192.168.2.x networks?  Don't forget to use a
>> full stop after them like:
>>
>> hosts allow 192.168.1. 192.168.2.
>>
>> or you could write it like:
>>
>> hosts allow 192.168.1.0/24 192.168.2.0/24
>
>     Hmmmm... I have "hosts allow = 192.168.1., 192.168.2., 127."

That looks fine as long as the Windows machine is on 192.168.1.x or
192.168.2.x.  According to the documentation you can use either commas
or spaces (or both) to separate them.

>     I have a space between the IP address excerpts (I presume that's what
> you mean by the full stop), though I also have a comma.  I'll remove the
> commas...

By "full stop" I mean what Americans like to call a "period" :)  i.e.
a dot.  In other words I just wanted to make sure you had something
like:

hosts allow 192.168.1., 192.168.2., 127.

and NOT:

hosts allow 192.168.1, 192.168.2, 127

although to be honest I don't know if Samba would accept the latter.

>> What does your smb.conf look like?  And what happens when you try to
>> connect/print from the Windows machine?  What errors to you get?
>
>     Here is my current smb.conf file:
>
> <<>>
> # Samba config file created using SWAT
> # from 127.0.0.1 (127.0.0.1)
> # Date: 2009/10/03 00:37:16
>
> # Global parameters
> [global]
>        server string = Windows in Linux - VMware
>        interfaces = eth0, vmnet1, vmnet8

I see you are restricting Samba to the above interfaces.  Which
interface is your Windows machine plugged into?  Your hosts allow line
leads me to suspect you might have another ethernet interface in the
machine (unless the other 192.168.x.y network is allocated to VMware.)

>        guest account = barry
>        username map = /etc/samba/smbusers
>        log file = /var/log/samba/%m.log
>        max log size = 50
>        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
>        printcap name = /etc/printcap
>        preferred master = Yes
>        dns proxy = No
>        idmap uid = 16777216-33554431
>        idmap gid = 16777216-33554431
>        guest ok = Yes
>        hosts allow = 192.168.1. 192.168.2. 127.
>        cups options = raw

Are you using cups?  The "printcap name" above leads me to believe you
are not using cups.

> [homes]
>        comment = Home Directories
>        read only = No
>
> [printers]
>        comment = All Printers
>        path = /var/spool/samba
>        printable = Yes
>        browseable = No
>
> [HostFS]
>        comment = VMware host filesystem
>        path = /
>        read only = No
>
> [barry]
>        path = /home/barry
>        valid users = barry
>        read only = No

This should not really be necessary because of the [homes] section
above, but should not cause any trouble either.

> [HP9110]
>        comment = Hewlett-Packard OfficeJet 9110
>        path = /var/spool/samba
>        read only = No
>        printable = Yes
>        printer name = HP9110
>        oplocks = No
>        share modes = No

Your [printers] section should automatically set up a share for any
printers defined in your /etc/printcap file.  So this should also not
be necessary.

> <<>>
>
>     There are a LOT of comments in my original smb.conf file, but since I
> tried to modify a couple of things using SWAT, I see it removed the
> comments.

Yes, unfortunately SWAT does not preserve the comments, but they just
get in the way when you post your config to the list anyway.

>     Much of what is in this file is what I had, years ago, when I had
> Windows 98 which I could access through VMware, which was running on my
> Linux system.  (I want to do exactly what I did with that, be able to
> submit a print job or transfer a file either direction.)
>
>     After I removed the comments in my "hosts allow" line, I typed
> "service smb restart" in my root window:
[...]

>     On the Windows computer, I clicked Start and then Network.
>
>     I double-clicked OFFICE-WINDOWS.
>
>     I double-clicked "Add a Printer".
>
>     Then an "Add a printer" came up near the top of my explorer, after
> Organize and Views.
>
>     Clicking "Add a printer", I choose "Add a network, wireless or
> Bluetooth printer" in the dialog box that comes up. ("Add a local printer"
> is the only other choice here.)

Yes, Network printer is the correct option.

>     It says "Searching for available printers..."
>
>     After a delay, it says "No printers were found."
>
>     I click "The printer that I want isn't listed" and out of the three
> choices ("Browse for a printer", "Select a shared printer by name" and
> "Add a printer using a TCP/IP address or hostname"), I choose the second
> one, as the printer is connected to my Linux system with a parallel port,
> and it does not have an IP address.

Well, actually the IP address in this case would have been the IP
address of the Linux box.  If the printer was plugged directly into
the network then of course this would be the IP address of the printer
itself.  But the option you chose should work if the name resolution
(WINS) etc. are working properly.  You might try the third option to
see what it does.  I can't test that myself right now.

>     I click in the "text box" and type "\\barrycon\hp9110"

Try using HP9110 as the share name instead of hp9110.  Not sure if it
makes a difference.  Also try Bruno's suggestion of using the Linux
machine's IP address instead of the name.

>     The hostname is barrycon (and that is exactly what worked in the
> Windows 98/VMware I did years ago), and if I type "lpstat -v" the first
> line says "device for HP9110:".

What does the following give you:
rpm -qf /usr/bin/lpstat

or maybe:
rpm -qf /usr/sbin/lpstat

(I haven't run an rpm-based distribution in a while...)

>     Another dialog box says "Connecting to hp9110 on barrycon" and after
> a short delay it says "Windows cannot connect to the printer.  The server
> print spooler service is not running.  Please restart the spooler on the
> server or restart the server machine."

See if the Windows box can resolve the name of the Linux box:

C:\>nbtstat -a barrycon

It should show the IP address and then a "NetBIOS Remote Machine Name Table".

Also try:

C:\>nbtstat -A 192.168.x.y

(with the IP address of the Linux machine.)

Also see if this works from the Windows box:

C:>ping barrycon

>     Michael, in the extremely limited time I've given this, I don't
> appear to be communicating at all.  I thank you that you and others are
> trying to help me, so I believe I will just see if you or anyone else
> replies before I mess something up worse!  :-)
>
>     Thank you again!

Something else you might like to try is backing up your smb.conf file
and starting very simply based on this:

http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/FastStart.html#id2554870

See also the other examples on that page, but do not bother with the
domain member and domain server sections.  They are most likely much
more complicated than is necessary for what you want to know.

Of course that does assume you're using CUPS, so you might have to
modify it a bit if you're not using CUPS.

--
Michael Wood <esiotrot@...>
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Michael Wood-8]

2009/10/10 Barry L. Bond <bbond@...>:
> Hi Gary!
[...]
>     I just now read a previous post from you that also indicated concerns
> with my running FC4, that I missed before.
> [...] I'm afraid I'm in an "if it works, don't fix it" mode...

Just bear in mind that sometimes the problems you have when trying to
set something new up could in part be caused by the old versions you
are restricted to because you are running an old distribution.  Of
course upgrading is not guaranteed to fix your Samba problems and
could cause other stuff to break :)

>     By "backport" do you mean a more recent version of Samba that will
> work in FC4?

Yes, that's exactly what he means.  I do not know off hand where you'd
find it, though.

>>It sounds like you are using FC4 as a file & print server. All you need
>>to do on it is share the resources (folders and printers) and set up the
>>permissions and accounts (if required).
>
>     On the Windows, I did do some things along this line (setting up
> sharing) last week...

He did not mean that you should create shares on the Windows machine,
but that you just need to share your printer and e.g. your home
directory on the Linux machine, as you have done.

>>You don't mention which version of Vista you are using, and I don't know
>>if they crippled certain versions like they did with XP to prevent them
>>from joining domains. However, if you can join Vista to a domain,
>>install and use SWAT to set up Samba as a domain controller and use it
>>to log in from Vista.
>
>     If I go to Control Panel and double click System, it says this:
>
> <<>>
> Windows edition..........
>
>      Windows Vista Ultimate

[...]

I believe that's the version with the most features, so you should not
run into any problems like not being able to join domains or whatever
if that's what you wanted to do.

>     Gary, I really appreciate your help.  On terminology, how do I join
> Vista to a domain?

I think you should probably try to keep things as simple as possible
to start with.  Setting up Samba as a domain controller is much more
trouble than is necessary for your simple requirements.

--
Michael Wood <esiotrot@...>
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Barry L. Bond]

Hi Michael!

     Thank you again for your very fast reply!  I just tonight had a
chance to look over Samba again, and consider the wonderful help you
have in this email.

On Sat, Oct 10, 2009 at 03:45:17PM +0200, Michael Wood wrote:

> >     Here is my current smb.conf file:
> >
> > <<>>
> > # Samba config file created using SWAT
> > # from 127.0.0.1 (127.0.0.1)
> > # Date: 2009/10/03 00:37:16
> >
> > # Global parameters
> > [global]
> >        server string = Windows in Linux - VMware
> >        interfaces = eth0, vmnet1, vmnet8
>
> I see you are restricting Samba to the above interfaces.  Which
> interface is your Windows machine plugged into?  Your hosts allow line
> leads me to suspect you might have another ethernet interface in the
> machine (unless the other 192.168.x.y network is allocated to VMware.)

     The Windows box is plugged into my D-Link router, as it has one
network interface connection and I also access the Internet with it.

     The D-Link EBR-2310 router is IP 192.168.1.1.

     The Linux eth0 port is IP 192.168.2.1.

     It is actually plugged into the second port of another D-Link device, a
Gigabit switch (a DGS-2205).

     Also plugged into the switch is port qfe1 (of a 4-port Ethernet card
I have in a Sun Ultra 30), with the address of 192.168.2.2.

     Port qfe0 of the Sun 4-port Ethernet card is 192.168.1.201, and it is
attached to the EBR-2310 router.

     (The switch is used to be able to allow the Linux as well as the Sun
to control my ESP-16 MI [serial port hub, 16 serial connections].  A few
of the serial connections are terminals, so they can actually be
controlled by the Sun as well as the Linux.  Actually, at the moment,
everything else that is attached to serial connections [weather station,
mailing label printer, speech synthesizer, UPS, X10 power controller,
etc.] I really only have the programming at the moment to control these
things on the Linux system.)

     The Sun is the router.  It also takes the Linux 192.168.2 connection
and routes it to/from the 192.168.1, the cable modem and Internet.  (And,
the Sun is my mail host.)

     Again, the Windows computer is on the router, and that is how it is
connected to the Linux.  (And, I have a 4-camera DVR attached to the
router, and DDNS set up to allow a URL to be used to look at the cameras
when I'm at work.  Helps me check on things on an occasional day when I
know my mother is going to be out.)

     Actually, I'm not really using the VMWare right now at all.  The two
vmnet interfaces allowed the connection to that, though.  (I added eth0
for the Windows Vista computer.)

> >        guest account = barry
> >        username map = /etc/samba/smbusers
> >        log file = /var/log/samba/%m.log
> >        max log size = 50
> >        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> >        printcap name = /etc/printcap
> >        preferred master = Yes
> >        dns proxy = No
> >        idmap uid = 16777216-33554431
> >        idmap gid = 16777216-33554431
> >        guest ok = Yes
> >        hosts allow = 192.168.1. 192.168.2. 127.
> >        cups options = raw
>
> Are you using cups?  The "printcap name" above leads me to believe you
> are not using cups.

     Yes.  :-)  Who knows... when I first set up my FC4 Linux system, I
wasn't using cups, but I installed it soon afterward.  That may have been
leftover from then, but it was working!  :-)

> > [homes]
> >        comment = Home Directories
> >        read only = No
> >
> > [printers]
> >        comment = All Printers
> >        path = /var/spool/samba
> >        printable = Yes
> >        browseable = No
> >
> > [HostFS]
> >        comment = VMware host filesystem
> >        path = /
> >        read only = No
> >
> > [barry]
> >        path = /home/barry
> >        valid users = barry
> >        read only = No
>
> This should not really be necessary because of the [homes] section
> above, but should not cause any trouble either.

     Okay...

> > [HP9110]
> >        comment = Hewlett-Packard OfficeJet 9110
> >        path = /var/spool/samba
> >        read only = No
> >        printable = Yes
> >        printer name = HP9110
> >        oplocks = No
> >        share modes = No
>
> Your [printers] section should automatically set up a share for any
> printers defined in your /etc/printcap file.  So this should also not
> be necessary.

     Okay...  if I seem to get some sort of Samba "connection" between the
Windows and Linux boxes, but have other trouble, I'll keep this in mind.

> > <<>>

> > "service smb restart" in my root window:
> [...]
> >     On the Windows computer, I clicked Start and then Network.
> >
> >     I double-clicked OFFICE-WINDOWS.
> >
> >     I double-clicked "Add a Printer".
> >
> >     Then an "Add a printer" came up near the top of my explorer, after
> > Organize and Views.
> >
> >     Clicking "Add a printer", I choose "Add a network, wireless or
> > Bluetooth printer" in the dialog box that comes up. ("Add a local printer"
> > is the only other choice here.)
>
> Yes, Network printer is the correct option.
>
> >     It says "Searching for available printers..."
> >
> >     After a delay, it says "No printers were found."
> >
> >     I click "The printer that I want isn't listed" and out of the three
> > choices ("Browse for a printer", "Select a shared printer by name" and
> > "Add a printer using a TCP/IP address or hostname"), I choose the second
> > one, as the printer is connected to my Linux system with a parallel port,
> > and it does not have an IP address.
>
> Well, actually the IP address in this case would have been the IP
> address of the Linux box.  If the printer was plugged directly into
> the network then of course this would be the IP address of the printer
> itself.  But the option you chose should work if the name resolution
> (WINS) etc. are working properly.  You might try the third option to
> see what it does.  I can't test that myself right now.
>
> >     I click in the "text box" and type "\\barrycon\hp9110"
>
> Try using HP9110 as the share name instead of hp9110.  Not sure if it
> makes a difference.  Also try Bruno's suggestion of using the Linux
> machine's IP address instead of the name.

     Okay.  Thank you!  :-)

     I just typed "\\192.168.2.1\HP9110" in the text box and I clicked the
[Next] button.

     The dialog box says "Connecting to HP9110 on 192.168.2.1"...

     After a delay, it eventually brings up another dialog box that says
"Windows cannot connect to the printer.  Make sure that you have typed the
name correctly, and that the printer is connected to network."

     Trying the third option, "Add a printer using a TCP/IP address or
hostname", I click the [Next] button.

     For "Device type" I have left it at "Autodetect".

     For Hostname or IP address, I'm using the IP of the Linux system:
192.168.2.1

     The third line is "Portname".  (I have never done it this way
before.)  At the moment, it has "192.168.2.1" which it put there as I
typed in the IP address in the second line, and it adds a "_1".  (So the
entire item is:  192.168.2.1_1

     I click the [Next] button.

     It says "Contacting printer..."

     After a delay, it brings up a window that says "Detecting TCP/IP
Port".  It says "Windows will automatically move to the next page when the
detection is done."

     After a delay, it says "The device is not found on the network."
followed by a "Be sure that" with standard things (the device is turned
on, the network is connected, the address on the previous page is correct,
etc.).

> What does the following give you:
> rpm -qf /usr/bin/lpstat
>
> or maybe:
> rpm -qf /usr/sbin/lpstat
>
> (I haven't run an rpm-based distribution in a while...)

     The first rpm gave me "cups-1.1.23-15".  The second one (with /sbin)
said "No such file or directory".

     Actually, most of my Fedora Core system was installed by yum, and not
rpm.  (But, though it does an automatic update sometimes that I see in the
LogWatch that runs at 4:00 every morning, I'm having difficulty running it
myself right now.)

> >     Another dialog box says "Connecting to hp9110 on barrycon" and after
> > a short delay it says "Windows cannot connect to the printer.  The server
> > print spooler service is not running.  Please restart the spooler on the
> > server or restart the server machine."
>
> See if the Windows box can resolve the name of the Linux box:
>
> C:\>nbtstat -a barrycon

     Wow, I had no clue about that command!  :-D

     I clicked Start->All Programs->Accessories->Command prompt

     In the command prompt, I'm typing "C:\>nbtstat -a barrycon"

     Ah... I don't need the C:\> part... I'm typing "nbtstat -a barrycon"

     It says:  "Local Area Connection:
                Node IpAddress:  [192.168.1.102] Scope Id:  []

                      Host not found."

> It should show the IP address and then a "NetBIOS Remote Machine Name Table".
>
> Also try:
>
> C:\>nbtstat -A 192.168.x.y
>
> (with the IP address of the Linux machine.)

     I'm typing "nbtstat -a 192.168.2.1"...

     ...and it says EXACTLY the same thing, after a slight delay.

> Also see if this works from the Windows box:
>
> C:>ping barrycon

     Typing "ping barrycon" displays (after a slight delay) "Ping request
could not find host barrycon.  Please check the name and try again."

     I'm typing "ping 192.168.2.1"...

     It says "Pinging 192.168.2.1 with 32 bytes of data:
     Request timed out.
     Request timed out.
     Request timed out.
     Request timed out.

     Ping statistics for 192.168.2.1:
        Packets: Sent = 4, Received = 0, Lost = 4 <100% loss>,"

     I don't appear to be connecting!  I see that now, where I didn't
before!  :-)

> Something else you might like to try is backing up your smb.conf file
> and starting very simply based on this:
>
> http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/FastStart.html#id2554870
>
> See also the other examples on that page, but do not bother with the
> domain member and domain server sections.  They are most likely much
> more complicated than is necessary for what you want to know.
>
> Of course that does assume you're using CUPS, so you might have to
> modify it a bit if you're not using CUPS.

     Thank you!  I see the link, and I can't work much longer this morning (it's after
1:00 Saturday morning), but I'll keep it and try it soon, also depending on what you and
others offer as additional suggestions from this post.  :-)

     I am using CUPS.  It works great.

     Thank you Michael and Bruno.  I'll CC this to the Samba mailing list.

     Barry

--
Barry L. Bond                      | http://home.roadrunner.com/~os9barry
Software Engineer, ITT Corporation | (My personal home web page, last
                                   | updated February 17, 2005)
                                   |
bbond @ cfl.rr.com <- personal     |  Re-Vita Products:
Barry.Bond @ ITT.com <- Work ONLY  |  http://www.re-vita.net/barrybond
                                   |  Re-Vita Distributor Information
Home office:  407-382-2815         |  http://www.re-vita.net/barrybond-2
Work:         321-494-5627 (Work)  |  Toll free order:  1-888-820-5531
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Barry L. Bond]

Hi Michael and everyone else!

> Something else you might like to try is backing up your smb.conf file
> and starting very simply based on this:
>
> http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/FastStart.html#id2554870

     Here is my latest attempt at an smb.conf file, set up almost exactly as in
this web page, and I have since added just a couple of things:

<<>>
# Global parameters
[global]
   workgroup = WORKGROUP
   netbios name = BARRYCON
   interfaces = eth0
        hosts allow = 192.168.1. 192.168.2. 127.
   security = share
        printcap name = cups
   disable spoolss = Yes
   show add printer wizard = No
   printing = cups

[printers]
        comment = All Printers
        path = /var/spool/samba
   guest ok = Yes
        printable = Yes
   use client driver = Yes
        browseable = No
<<>>

     I don't think I'm communicating at all between the Windows Vista system
and the Linux system.

     I think I need to set up something in my Advanced portion of my D-Link
router.

     For example, I have a GadSpot DVR set up, with the two ports mapped.  For
example, one port is 8080, so I have:

<<>>
192.168.1.101 Public/private 8080 Schedule Always.
<<>>

     (I have the other port on another line with an address of 192.168.1.101,
which is the address of the DVR.)

     I have the following typed in later lines of my Advanced Virtual Servers
List:

<<>>
Office-Windows, 192.168.1.102
Barrycon, 192.168.2.1
<<>>

     What port(s) should I allow for Samba?

     The D-Link router allows "mapping" of two port numbers between the Windows
computer and the DVR.  I think I need something similar here.

     The Windows Vista has a hard-coded IP of 192.168.1.102 and the Linux
system has a hard-coded IP of 192.168.2.1.

     If anyone can offer any suggestions, I would appreciate it.  Thank you!
     Barry

--
Barry L. Bond                      | http://home.roadrunner.com/~os9barry
Software Engineer, ITT Corporation | (My personal home web page, last
                                   | updated February 17, 2005)
                                   |
bbond @ cfl.rr.com <- personal     |  Re-Vita Products:
Barry.Bond @ ITT.com <- Work ONLY  |  http://www.re-vita.net/barrybond
                                   |  Re-Vita Distributor Information
Home office:  407-382-2815         |  http://www.re-vita.net/barrybond-2
Work:         321-494-5627 (Work)  |  Toll free order:  1-888-820-5531
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Eero Volotinen-2]

>      I don't think I'm communicating at all between the Windows Vista system
> and the Linux system.
>
>      I think I need to set up something in my Advanced portion of my D-Link
> router.
>
>      For example, I have a GadSpot DVR set up, with the two ports mapped.  For
> example, one port is 8080, so I have:
>
> <<>>
> 192.168.1.101 Public/private 8080 Schedule Always.
> <<>>
>
>      (I have the other port on another line with an address of 192.168.1.101,
> which is the address of the DVR.)

Port 135/TCP - used by smbd
Port 137/UDP - used by nmbd
Port 138/UDP - used by nmbd
Port 139/TCP - used by smbd
Port 445/TCP - used by smbd

Do you really need to put samba and windows machine on different ip range?

--
Eero
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Eero Volotinen-2]

Eero Volotinen wrote:

> Do you really need to put samba and windows machine on different ip range?

Remember also open ports on Linux internal firewall.

--
Eero
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Michael Wood-8]

2009/10/24 Barry L. Bond <bbond@...>:
[...]

> On Sat, Oct 10, 2009 at 03:45:17PM +0200, Michael Wood wrote:
>
>> >     Here is my current smb.conf file:
>> >
>> > <<>>
>> > # Samba config file created using SWAT
>> > # from 127.0.0.1 (127.0.0.1)
>> > # Date: 2009/10/03 00:37:16
>> >
>> > # Global parameters
>> > [global]
>> >        server string = Windows in Linux - VMware
>> >        interfaces = eth0, vmnet1, vmnet8
>>
>> I see you are restricting Samba to the above interfaces.  Which
>> interface is your Windows machine plugged into?  Your hosts allow line
>> leads me to suspect you might have another ethernet interface in the
>> machine (unless the other 192.168.x.y network is allocated to VMware.)
>
>     The Windows box is plugged into my D-Link router, as it has one
> network interface connection and I also access the Internet with it.

It would be a lot easier for people to follow if you provided an ASCII
art diagram of all the machine and routers involved, but I have drawn
your network on a piece of paper based on your description.

It seems your Linux box only has one network card, right?  And are you
trying to print from the Windows machine connected to your D-Link
router?  Or from a Virtual machine running under VMware on the Linux
box?

Your interfaces line appears to specify all possible interfaces other
than lo anyway, so you may as well leave it out.

[...]
>> >        printcap name = /etc/printcap
[...]
>> >        cups options = raw
>>
>> Are you using cups?  The "printcap name" above leads me to believe you
>> are not using cups.
>
>     Yes.  :-)  Who knows... when I first set up my FC4 Linux system, I
> wasn't using cups, but I installed it soon afterward.  That may have been
> leftover from then, but it was working!  :-)

Well, if you are using CUPS, you could set up an IPP printer on the
Windows box and bypass Samba completely.  In the "Add Printer Wizard"
you tell it to add a network printer and on the next screen choose the
"Connect to a printer on the Internet..." option (XP.  Not sure if
it's the same for Vista).  The URL should be something like:

http://192.168.2.1:631/printers/HP9110

(depending on what name the printer has been given in CUPS.)

Try browsing to http://127.0.0.1:631 on the Linux box to see if CUPS is running.

[...]
>     I just typed "\\192.168.2.1\HP9110" in the text box and I clicked the
> [Next] button.
>
>     The dialog box says "Connecting to HP9110 on 192.168.2.1"...
>
>     After a delay, it eventually brings up another dialog box that says
> "Windows cannot connect to the printer.  Make sure that you have typed the
> name correctly, and that the printer is connected to network."

Perhaps you should see if you can telnet to the TCP ports mentioned by
Eero from the Ultra 30.  It would be better to test from Vista, but
I've been told Vista does not have a telnet client built in.
Otherwise you could download something like PuTTY and see if you can
connect to those ports from the Vista machine.

>     Trying the third option, "Add a printer using a TCP/IP address or
> hostname", I click the [Next] button.
>
>     For "Device type" I have left it at "Autodetect".
>
>     For Hostname or IP address, I'm using the IP of the Linux system:
> 192.168.2.1
>
>     The third line is "Portname".  (I have never done it this way
> before.)  At the moment, it has "192.168.2.1" which it put there as I
> typed in the IP address in the second line, and it adds a "_1".  (So the
> entire item is:  192.168.2.1_1

Perhaps this is the Vista equivalent of the XP "Connect to a printer
on the Internet or on a home or office network" option.  If so, you'll
want to try port 631 (assuming you are running CUPS on the Linux box.)
 I'm not sure if this is what is meant by the above, though, and there
should be somewhere to put in /printers/HP9110 or something like that
too if it is.

>> What does the following give you:
>> rpm -qf /usr/bin/lpstat
>>
>> or maybe:
>> rpm -qf /usr/sbin/lpstat
>>
>> (I haven't run an rpm-based distribution in a while...)
>
>     The first rpm gave me "cups-1.1.23-15".  The second one (with /sbin)
> said "No such file or directory".

OK, so it seems that CUPS is installed.  Or at least part of it.

What does "rpm -qa | grep cups" give you?

>     Actually, most of my Fedora Core system was installed by yum, and not
> rpm.  (But, though it does an automatic update sometimes that I see in the
> LogWatch that runs at 4:00 every morning, I'm having difficulty running it
> myself right now.)

yum is just a front end to rpm.

>> See if the Windows box can resolve the name of the Linux box:
>>
>> C:\>nbtstat -a barrycon
[...]
>     It says:  "Local Area Connection:
>                Node IpAddress:  [192.168.1.102] Scope Id:  []
>
>                      Host not found."

OK, so name resolution is not working.  This is likely because you
have the Windows box and the Linux box on different subnets.  You
could try configuring the Windows box to use the Linux box as a WINS
server.  Samba would have to be running as a WINS server.

>> It should show the IP address and then a "NetBIOS Remote Machine Name Table".
>>
>> Also try:
>>
>> C:\>nbtstat -A 192.168.x.y
>>
>> (with the IP address of the Linux machine.)
>
>     I'm typing "nbtstat -a 192.168.2.1"...
>
>     ...and it says EXACTLY the same thing, after a slight delay.

Note the capital A in my command.  When you query an IP address using
nbtstat you need -A instead of -a.

>> Also see if this works from the Windows box:
>>
>> C:>ping barrycon
>
>     Typing "ping barrycon" displays (after a slight delay) "Ping request
> could not find host barrycon.  Please check the name and try again."

I would not expect this to work if "nbtstat -a barrycon" did not work.

>     I'm typing "ping 192.168.2.1"...
>
>     It says "Pinging 192.168.2.1 with 32 bytes of data:
>     Request timed out.
[...]

OK, so either you have a firewall blocking this (e.g. on the Ultra 30
or on Linux) or the Window box does not know how to get to the
192.168.2.0/24 network.  If it's the latter, add a route for
192.168.2.0 netmask 255.255.255.0 to the Windows machine's network
settings with a gateway of 192.168.1.201 (the IP of the Ultra 30 on
the 192.168.1.x subnet).

Also check that you can ping 192.168.1.201 from the Window box.

>> Something else you might like to try is backing up your smb.conf file
>> and starting very simply based on this:
>>
>> http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/FastStart.html#id2554870
>>
>> See also the other examples on that page, but do not bother with the
>> domain member and domain server sections.  They are most likely much
>> more complicated than is necessary for what you want to know.
>>
>> Of course that does assume you're using CUPS, so you might have to
>> modify it a bit if you're not using CUPS.
>
>     Thank you!  I see the link, and I can't work much longer this morning (it's after
> 1:00 Saturday morning), but I'll keep it and try it soon, also depending on what you and
> others offer as additional suggestions from this post.  :-)

I still think it would be worth trying to start with the simple config
mentioned above, but your routing and firewalling should be correct
first.

>     I am using CUPS.  It works great.

Well then you might be able to ignore Samba for the printing and just
directly use CUPS, but again your routing (and firewalling, if any)
will need to be correct first.

--
Michael Wood <esiotrot@...>
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Michael Wood-8]

2009/11/7 Barry L. Bond <bbond@...>:

> Hi Michael and everyone else!
>
>> Something else you might like to try is backing up your smb.conf file
>> and starting very simply based on this:
>>
>> http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/FastStart.html#id2554870
>
>     Here is my latest attempt at an smb.conf file, set up almost exactly as in
> this web page, and I have since added just a couple of things:
>
> <<>>
> # Global parameters
> [global]
>   workgroup = WORKGROUP
>   netbios name = BARRYCON
>   interfaces = eth0
>        hosts allow = 192.168.1. 192.168.2. 127.
>   security = share
>        printcap name = cups
>   disable spoolss = Yes
>   show add printer wizard = No
>   printing = cups
>
> [printers]
>        comment = All Printers
>        path = /var/spool/samba
>   guest ok = Yes
>        printable = Yes
>   use client driver = Yes
>        browseable = No
> <<>>
>
>     I don't think I'm communicating at all between the Windows Vista system
> and the Linux system.
>
>     I think I need to set up something in my Advanced portion of my D-Link
> router.

Most likely your D-Link router has a built in 4 port switch and does
not control access between these 4 ports, so I doubt you need to do
anything on the D-Link router.

>     For example, I have a GadSpot DVR set up, with the two ports mapped.  For
> example, one port is 8080, so I have:
[...]

My understanding is that this is to allow you to connect to your DVR
from the Internet.  So unless you want to connect to Samba from the
Internet, I very much doubt you need to configure anything on the
D-Link router.

>     What port(s) should I allow for Samba?
[...]

See Eero's message.  However, I think this could be leading you down
the wrong path.

First make sure you can ping the Ultra 30 from the Windows box and
vice versa.  Then make sure you can ping the Linux box from the Ultra
30 and vice versa.  Then make sure you can ping the Linux box from the
Window box and vice versa.

For the above to work, you may have to disable firewalls on the
Windows box, the Linux box and the Ultra 30.  Of course you could also
allow the necessary things in the firewalls instead of disabling them.

Also, the Ultra 30 must be configured to route traffic between its
interfaces.  If you can connect to the Internet from the Linux box
then this should be OK.

I think you should configure the Windows box to use the Linux box as a
WINS server after making sure that your smb.conf file has "wins
support = yes" in the global section.

I hope this gets you a bit further.

--
Michael Wood <esiotrot@...>
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Barry L. Bond]

Hi Michael!

     Thank you for your extra efforts to try to follow this, and with my
only having time to try something else once every couple of weeks!  :-O

On Sun, Nov 08, 2009 at 04:02:50PM +0200, Michael Wood wrote:

> It would be a lot easier for people to follow if you provided an ASCII
> art diagram of all the machine and routers involved, but I have drawn
> your network on a piece of paper based on your description.

     Okay...  :-)  I actually do need to "draw up" a better diagram than I
drew up when I had some network changes last year after a direct lightning
strike to my house!  :-)  (Until that lightning strike, I had a Cyclades
16-port PCI bus card in the Linux computer.  That was fried, and I went to
the IP Network hub, allowing the Solaris as well as the Linux to control
the ports.  I added the D-Link DGS-2205 switch then, too...)  I will plan
it...

> It seems your Linux box only has one network card, right?  And are you
> trying to print from the Windows machine connected to your D-Link
> router?  Or from a Virtual machine running under VMware on the Linux
> box?

     Correct.  The Linux box has only one network card, and it is attached
to the DGS-2205 (switch).  One network port on the Sun is attached to the
D-Link router and the cable modem is on the other side of that, and
another Sun network port is attached to the DGS-2205 switch.

     The only network port of the Windows is attached to the D-Link
router.

     I'm trying to print from the Windows machine connected to the D-Link
router.

     Well, forget the virtual machine, really, for now.  (In the past, I
have run Windows 98 through VMware running on the Linux, and I was able to
do on it exactly what I WANT to do with this truly separate Windows
machine:  print and transfer files.  Back then, I had TIME, and I likely
just "trial-ed and error-ed" until I got it working well enough!)

> Your interfaces line appears to specify all possible interfaces other
> than lo anyway, so you may as well leave it out.

     Really, the vmnet interfaces could go now... I just had left them,
for they were needed and used in the past (and there is a slight chance
they MAY be used in the future), and I didn't think they hurt anything.
Is that okay?

> [...]
> >> >        printcap name = /etc/printcap
> [...]
> >> >        cups options = raw
> >>
> >> Are you using cups?  The "printcap name" above leads me to believe you
> >> are not using cups.
> >
> >     Yes.  :-)  Who knows... when I first set up my FC4 Linux system, I
> > wasn't using cups, but I installed it soon afterward.  That may have been
> > leftover from then, but it was working!  :-)
>
> Well, if you are using CUPS, you could set up an IPP printer on the
> Windows box and bypass Samba completely.  In the "Add Printer Wizard"
> you tell it to add a network printer and on the next screen choose the
> "Connect to a printer on the Internet..." option (XP.  Not sure if
> it's the same for Vista).  The URL should be something like:
>
> http://192.168.2.1:631/printers/HP9110

     Er... no I can't.  This printer has only a parallel port, and it is
attached to a parallel port on my Linux computer.  :-)

> (depending on what name the printer has been given in CUPS.)
>
> Try browsing to http://127.0.0.1:631 on the Linux box to see if CUPS is running.

     It most certainly is.  I don't use "this type of interface" very
often, but I have accessed it this way some.  (I usually just "lp" and
"lpstat"...)

     I print quite a bit from the Linux system, via my CUPS-enabled HP
9110 printer.

> [...]
> >     I just typed "\\192.168.2.1\HP9110" in the text box and I clicked the
> > [Next] button.
> >
> >     The dialog box says "Connecting to HP9110 on 192.168.2.1"...
> >
> >     After a delay, it eventually brings up another dialog box that says
> > "Windows cannot connect to the printer.  Make sure that you have typed the
> > name correctly, and that the printer is connected to network."
>
> Perhaps you should see if you can telnet to the TCP ports mentioned by
> Eero from the Ultra 30.  It would be better to test from Vista, but
> I've been told Vista does not have a telnet client built in.
> Otherwise you could download something like PuTTY and see if you can
> connect to those ports from the Vista machine.

     Hmmm.... so, on the Sun, type "telnet 192.168.2.1" and whatever port?
I'm using that IP because that's the Linux system, where the Samba is
running.

     If that's what you mean, then here is what I get:

<<>>
bash-2.03# telnet 192.168.2.1 135
Trying 192.168.2.1...
telnet: Unable to connect to remote host: Connection refused
bash-2.03# telnet 192.168.2.1 137
Trying 192.168.2.1...
telnet: Unable to connect to remote host: Connection refused
bash-2.03# telnet 192.168.2.1 138
Trying 192.168.2.1...
telnet: Unable to connect to remote host: Connection refused
bash-2.03# telnet 192.168.2.1 139
Trying 192.168.2.1...
Connected to 192.168.2.1.
Escape character is '^]'.

<<>>

     I never enabled "ftp" on my Linux system, so I guess that's why I'm
getting "Connection refused" on most of the attempts.

     When I tried with port 139, it displayed what you see, and there was
a delay for a couple of minutes, and then I see:

<<>>
Connection closed by foreign host
bash-2.03# telnet 192.168.2.1 445
Trying 192.168.2.1...
Connected to 192.168.2.1.
Escape character is '^]'.
Connection closed by foreign host
<<>>

     There is also a delay after the port 445 and then I saw the
"Connection closed by foreign host" message.

     Is this what you had in mind?

> >     The first rpm gave me "cups-1.1.23-15".  The second one (with /sbin)
> > said "No such file or directory".
>
> OK, so it seems that CUPS is installed.  Or at least part of it.
>
> What does "rpm -qa | grep cups" give you?

     That command gives me:

<<>>
[root@barrycon xinetd.d]# rpm -qa | grep cups
hal-cups-utils-0.5.3-3
gimp-print-cups-4.2.7-7
cups-libs-1.1.23-15
cups-lpd-1.1.23-15
libgnomecups-devel-0.2.0-2
libgnomecups-0.2.0-2
cups-1.1.23-15
bluez-utils-cups-2.15-7
cups-devel-1.1.23-15
<<>>

> >> See if the Windows box can resolve the name of the Linux box:
> >>
> >> C:\>nbtstat -a barrycon
> [...]
> >     It says:  "Local Area Connection:
> >                Node IpAddress:  [192.168.1.102] Scope Id:  []
> >
> >                      Host not found."
>
> OK, so name resolution is not working.  This is likely because you
> have the Windows box and the Linux box on different subnets.  You
> could try configuring the Windows box to use the Linux box as a WINS
> server.  Samba would have to be running as a WINS server.

     Ah... well, I also asked Eero if that was a problem...  I would be
happy using IP addresses, but we can keep this in mind...

> >> It should show the IP address and then a "NetBIOS Remote Machine Name Table".
> >>
> >> Also try:
> >>
> >> C:\>nbtstat -A 192.168.x.y
> >>
> >> (with the IP address of the Linux machine.)
> >
> >     I'm typing "nbtstat -a 192.168.2.1"...
> >
> >     ...and it says EXACTLY the same thing, after a slight delay.
>
> Note the capital A in my command.  When you query an IP address using
> nbtstat you need -A instead of -a.

     Ah!  I apologize about that!  Let me try it again!

     Typed carefully... since I am typing instead of copying/pasting it!
     :-D

<<>>
C:\Users\Barry L. Bond>nbtstat -A 192.168.2.1

Local Area Connection:
Node IpAddress: [192.168.1.102] Scope Id: []

    Host not found.
<<>>

     (I may have typed the capital A in Windows before and typed it as a
lowercase a in email, but I'm sure not going by memory!)  :-D

> OK, so either you have a firewall blocking this (e.g. on the Ultra 30
> or on Linux) or the Window box does not know how to get to the
> 192.168.2.0/24 network.  If it's the latter, add a route for
> 192.168.2.0 netmask 255.255.255.0 to the Windows machine's network
> settings with a gateway of 192.168.1.201 (the IP of the Ultra 30 on
> the 192.168.1.x subnet).

     I don't have a firewall running on the Ultra 30 or the Linux.  The
D-Link router is also a firewall, for the Internet side.

     Okay.  I'm noting this.  I have absolutely no idea how to do this!
:-)  But, I shall add it to my "do list"...

> Also check that you can ping 192.168.1.201 from the Window box.

     This worked:

<<>>
C:\Users\Barry L. Bond>ping 192.168.1.201

Pinging 192.168.1.201 with 32 bytes of data:
Reply from 192.168.1.201: bytes=32 time<1ms TTL=255
Reply from 192.168.1.201: bytes=32 time<1ms TTL=255
Reply from 192.168.1.201: bytes=32 time<1ms TTL=255
Reply from 192.168.1.201: bytes=32 time<1ms TTL=255

Ping statistics for 192.168.1.201:
    Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>,
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
<<>>

     Thank you, Michael!  I appreciate and need your help!

     Barry

--
Barry L. Bond                      | http://home.roadrunner.com/~os9barry
Software Engineer, ITT Corporation | (My personal home web page, last
                                   | updated February 17, 2005)
                                   |
bbond @ cfl.rr.com <- personal     |  Re-Vita Products:
Barry.Bond @ ITT.com <- Work ONLY  |  http://www.re-vita.net/barrybond
                                   |  Re-Vita Distributor Information
Home office:  407-382-2815         |  http://www.re-vita.net/barrybond-2
Work:         321-494-5627 (Work)  |  Toll free order:  1-888-820-5531
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba