I'm trying to use Samba to transfer some pictures on my local network from one of my Linux machines to my windows XP one. I set up the Samba Server using Yast. The output from 'testparm /etc/samba/smb.conf' is good. My Global parameters are: [global] workgroup = MYHOME netbios name = MYSAMBASERVER map to guest = Bad User username map = /etc/samba/smbusers printcap cache time = 750 printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s When I run smbclient to list my shares I get this: # smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed I get this as root and my normal self on the same machine the server is on. I turned the firewall off. My /etc/samba/smbusers file: # This file allows you to map usernames from the clients to the server. # Unix_name = SMB_name1 SMB_name2 ... # # See section 'username map' in the manual page of smb.conf for more # information. root = administrator ;nobody = guest pcguest smbguest Any ideas why my connection is being refused? Also, anyone know how to access this samba share from the windows side? Thanks, Jerome
On Sunday, June 12, 2005 @ 7:08 PM, Jerome Lyles wrote:
I'm trying to use Samba to transfer some pictures on my local network from one of my Linux machines to my windows XP one. I set up the Samba Server using
Yast. The output from 'testparm /etc/samba/smb.conf' is good. My Global parameters are:
[global] workgroup = MYHOME netbios name = MYSAMBASERVER map to guest = Bad User username map = /etc/samba/smbusers printcap cache time = 750 printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
I get this as root and my normal self on the same machine the server is on. I turned the firewall off.
My /etc/samba/smbusers file:
# This file allows you to map usernames from the clients to the server. # Unix_name = SMB_name1 SMB_name2 ... # # See section 'username map' in the manual page of smb.conf for more # information.
root = administrator ;nobody = guest pcguest smbguest
Any ideas why my connection is being refused? Also, anyone know how to access this samba share from the windows side?
Thanks, Jerome
I share a linux directory with my Windows machine. Try adding -- wins support = yes security = share to your [global] section. Also, I have the following for my "share" (I called it Shareddocs just to have it stick out as a Windows share). I'm forcing the user to the Linux built-in nobody group. [SharedDocs] path = /etc/samba/smbusers guest ok = yes guest account = nobody force group = MYHOME Also, be sure the nobody user is set up as a member of the MYHOME group on your Linux machine. Whatever privileges you give it, that's what you'll be able to do from your Windows machine. Also, your Windows machine has to be using the MYHOME workgroup, which I assume it does. Greg Wallace
On 13/06/05, Greg Wallace <jgregw@acsalaska.net> wrote:
On Sunday, June 12, 2005 @ 7:08 PM, Jerome Lyles wrote:
I'm trying to use Samba to transfer some pictures on my local network from one of my Linux machines to my windows XP one. I set up the Samba Server using
Yast. The output from 'testparm /etc/samba/smb.conf' is good. My Global parameters are:
[global] workgroup = MYHOME netbios name = MYSAMBASERVER map to guest = Bad User username map = /etc/samba/smbusers printcap cache time = 750 printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
I get this as root and my normal self on the same machine the server is on. I turned the firewall off.
My /etc/samba/smbusers file:
# This file allows you to map usernames from the clients to the server. # Unix_name = SMB_name1 SMB_name2 ... # # See section 'username map' in the manual page of smb.conf for more # information.
root = administrator ;nobody = guest pcguest smbguest
Any ideas why my connection is being refused? Also, anyone know how to access this samba share from the windows side?
Thanks, Jerome
I share a linux directory with my Windows machine. Try adding --
wins support = yes security = share
to your [global] section.
Also, I have the following for my "share" (I called it Shareddocs just to have it stick out as a Windows share). I'm forcing the user to the Linux built-in nobody group.
[SharedDocs] path = /etc/samba/smbusers guest ok = yes guest account = nobody force group = MYHOME
Also, be sure the nobody user is set up as a member of the MYHOME group on your Linux machine. Whatever privileges you give it, that's what you'll be able to do from your Windows machine. Also, your Windows machine has to be using the MYHOME workgroup, which I assume it does.
Greg Wallace
Is that IP address a valid internal one? Could that be the cause of the problem? -- Take care. Kevan Farmer 34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
On Monday 13 June 2005 03:23, Kevanf1 wrote:
On 13/06/05, Greg Wallace <jgregw@acsalaska.net> wrote:
On Sunday, June 12, 2005 @ 7:08 PM, Jerome Lyles wrote:
I'm trying to use Samba to transfer some pictures on my local network
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
I get this as root and my normal self on the same machine the server is on. I turned the firewall off.
I share a linux directory with my Windows machine. Try adding --
wins support = yes security = share
to your [global] section.
Also, I have the following for my "share" (I called it Shareddocs just to have it stick out as a Windows share). I'm forcing the user to the Linux built-in nobody group.
[SharedDocs] path = /etc/samba/smbusers guest ok = yes guest account = nobody force group = MYHOME
Also, be sure the nobody user is set up as a member of the MYHOME group on your Linux machine. Whatever privileges you give it, that's what you'll be able to do from your Windows machine. Also, your Windows machine has to be using the MYHOME workgroup, which I assume it does.
Greg Wallace
I will check things out when I get home. Thanks.
Is that IP address a valid internal one? Could that be the cause of the problem?
--
How do I tell if it's a valid one? I know 127.0.0.1 is valid: lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8699 errors:0 dropped:0 overruns:0 frame:0 TX packets:8699 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2750512 (2.6 Mb) TX bytes:2750512 (2.6 Mb) Jerome
Take care. Kevan Farmer
34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
On 13/06/05, Susemail <susemail@hawaii.rr.com> wrote:
On Monday 13 June 2005 03:23, Kevanf1 wrote:
On 13/06/05, Greg Wallace <jgregw@acsalaska.net> wrote:
On Sunday, June 12, 2005 @ 7:08 PM, Jerome Lyles wrote:
I'm trying to use Samba to transfer some pictures on my local network
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
I get this as root and my normal self on the same machine the server is on. I turned the firewall off.
I share a linux directory with my Windows machine. Try adding --
wins support = yes security = share
to your [global] section.
Also, I have the following for my "share" (I called it Shareddocs just to have it stick out as a Windows share). I'm forcing the user to the Linux built-in nobody group.
[SharedDocs] path = /etc/samba/smbusers guest ok = yes guest account = nobody force group = MYHOME
Also, be sure the nobody user is set up as a member of the MYHOME group on your Linux machine. Whatever privileges you give it, that's what you'll be able to do from your Windows machine. Also, your Windows machine has to be using the MYHOME workgroup, which I assume it does.
Greg Wallace
I will check things out when I get home. Thanks.
Is that IP address a valid internal one? Could that be the cause of the problem?
--
How do I tell if it's a valid one? I know 127.0.0.1 is valid:
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8699 errors:0 dropped:0 overruns:0 frame:0 TX packets:8699 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2750512 (2.6 Mb) TX bytes:2750512 (2.6 Mb)
Jerome
There are specific sets of IP addresses that are generally reserved for home networking. Now I'm on shaky ground here so I'm sure others more knowledgeable will prop me up (please :-))) I think that there are three classes of internal (home in this case) network IP addresses. I think you ought to be looking at having 192.168.0.1 as eth0 on your first PC. Then after that 192.168.0.2 for the next one and so on with 0.3 and 0.4 etc I think you can have up to 256 machines connected like this. This is a PC via switch to PC network not via server. I have mine set up this way and it works. The 192 is the internal IP start number if you like. This would use a subnet mask of 255.255.255.0 Feel free to point me in the right direction if I'm wrong. -- Take care. Kevan Farmer 34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
On Mon, 2005-06-13 at 20:56 +0100, Kevanf1 wrote:
On 13/06/05, Susemail <susemail@hawaii.rr.com> wrote:
How do I tell if it's a valid one? I know 127.0.0.1 is valid:
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8699 errors:0 dropped:0 overruns:0 frame:0 TX packets:8699 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2750512 (2.6 Mb) TX bytes:2750512 (2.6 Mb)
Jerome
There are specific sets of IP addresses that are generally reserved for home networking. Now I'm on shaky ground here so I'm sure others more knowledgeable will prop me up (please :-))) I think that there are three classes of internal (home in this case) network IP addresses. I think you ought to be looking at having 192.168.0.1 as eth0 on your first PC. Then after that 192.168.0.2 for the next one and so on with 0.3 and 0.4 etc I think you can have up to 256 machines
With 192.168.0.0/255.255.255.0 you will actually get 254 usable addresses. You cannot use the .255 address as it is the broadcast address. You cannot use the .0 address (I think) as it denotes the network.
connected like this. This is a PC via switch to PC network not via server. I have mine set up this way and it works. The 192 is the internal IP start number if you like. This would use a subnet mask of 255.255.255.0
Feel free to point me in the right direction if I'm wrong.
There are three private address spaces that are -not- routable on the internet and are meant to be used on internal networks only. IP address range, network/mask, number of address 10.0.0.0 - 10.255.255.255, 10.0.0.0/8, 16,777,216 addresses 172.16.0.0 - 172.31.255.255, 172.16.0.0/12, 1,048,576 addresses 192.168.0.0 - 192.168.255.255, 192.168.0.0/16, 65,536 addresses Check http://www.idevelopment.info/data/Networking/Networking_Basics/BASICS_Privat... for further info. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Monday 13 June 2005 12:21, Ken Schneider wrote:
On Mon, 2005-06-13 at 20:56 +0100, Kevanf1 wrote:
On 13/06/05, Susemail <susemail@hawaii.rr.com> wrote:
How do I tell if it's a valid one? I know 127.0.0.1 is valid:
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8699 errors:0 dropped:0 overruns:0 frame:0 TX packets:8699 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2750512 (2.6 Mb) TX bytes:2750512 (2.6 Mb)
Jerome
There are three private address spaces that are -not- routable on the internet and are meant to be used on internal networks only. IP address range, network/mask, number of address 10.0.0.0 - 10.255.255.255, 10.0.0.0/8, 16,777,216 addresses 172.16.0.0 - 172.31.255.255, 172.16.0.0/12, 1,048,576 addresses 192.168.0.0 - 192.168.255.255, 192.168.0.0/16, 65,536 addresses
Check http://www.idevelopment.info/data/Networking/Networking_Basics/BASICS_Priva te_Address_Space.shtml for further info.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
So...is this a valid address?? Jerome
On Tue, 2005-06-14 at 10:53 -1000, Susemail wrote:
There are three private address spaces that are -not- routable on the internet and are meant to be used on internal networks only. IP address range, network/mask, number of address 10.0.0.0 - 10.255.255.255, 10.0.0.0/8, 16,777,216 addresses 172.16.0.0 - 172.31.255.255, 172.16.0.0/12, 1,048,576 addresses 192.168.0.0 - 192.168.255.255, 192.168.0.0/16, 65,536 addresses
Check http://www.idevelopment.info/data/Networking/Networking_Basics/BASICS_Priva te_Address_Space.shtml for further info.
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
So...is this a valid address?? Did you go to the link I included and read any of it. I believe it covers the loopback addresses as well.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Tuesday 14 June 2005 10:57, Ken Schneider wrote:
On Tue, 2005-06-14 at 10:53 -1000, Susemail wrote:
There are three private address spaces that are -not- routable on the internet and are meant to be used on internal networks only. IP address range, network/mask, number of address 10.0.0.0 - 10.255.255.255, 10.0.0.0/8, 16,777,216 addresses 172.16.0.0 - 172.31.255.255, 172.16.0.0/12, 1,048,576 addresses 192.168.0.0 - 192.168.255.255, 192.168.0.0/16, 65,536 addresses
Check http://www.idevelopment.info/data/Networking/Networking_Basics/BASICS_P riva te_Address_Space.shtml for further info.
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
So...is this a valid address??
Did you go to the link I included and read any of it. I believe it covers the loopback addresses as well.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 Hi Ken,
Yes I did but I got the Not Found message from the browser. Jerome ps: But I only went after I read this email. Jerome
On Tue, 2005-06-14 at 16:05 -1000, Susemail wrote:
On Tuesday 14 June 2005 10:57, Ken Schneider wrote:
On Tue, 2005-06-14 at 10:53 -1000, Susemail wrote:
There are three private address spaces that are -not- routable on the internet and are meant to be used on internal networks only. IP address range, network/mask, number of address 10.0.0.0 - 10.255.255.255, 10.0.0.0/8, 16,777,216 addresses 172.16.0.0 - 172.31.255.255, 172.16.0.0/12, 1,048,576 addresses 192.168.0.0 - 192.168.255.255, 192.168.0.0/16, 65,536 addresses
Check http://www.idevelopment.info/data/Networking/Networking_Basics/BASICS_P riva te_Address_Space.shtml for further info.
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
So...is this a valid address??
Did you go to the link I included and read any of it. I believe it covers the loopback addresses as well.
Hi Ken,
Yes I did but I got the Not Found message from the browser. Jerome
ps: But I only went after I read this email.
The link is wrapped on two lines, make sure you put all of the link in the browser. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Monday, June 13, 2005 @ 9:59 AM, Kevan Farmer wrote:
On Monday 13 June 2005 03:23, Kevanf1 wrote:
On 13/06/05, Greg Wallace <jgregw@acsalaska.net> wrote:
On Sunday, June 12, 2005 @ 7:08 PM, Jerome Lyles wrote:
I'm trying to use Samba to transfer some pictures on my local network
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
I get this as root and my normal self on the same machine the server is on. I turned the firewall off.
I share a linux directory with my Windows machine. Try adding --
wins support = yes security = share
to your [global] section.
Also, I have the following for my "share" (I called it Shareddocs just to have it stick out as a Windows share). I'm forcing the user to the Linux built-in nobody group.
[SharedDocs] path = /etc/samba/smbusers guest ok = yes guest account = nobody force group = MYHOME
Also, be sure the nobody user is set up as a member of the MYHOME group on your Linux machine. Whatever privileges you give it, that's what you'll be able to do from your Windows machine. Also, your Windows machine has to be using the MYHOME workgroup, which I assume it does.
Greg Wallace
I will check things out when I get home. Thanks.
Is that IP address a valid internal one? Could that be the cause of the problem?
--
How do I tell if it's a valid one? I know 127.0.0.1 is valid:
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8699 errors:0 dropped:0 overruns:0 frame:0 TX packets:8699 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2750512 (2.6 Mb) TX bytes:2750512 (2.6 Mb)
Jerome
Take care. Kevan Farmer
34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
Take a look at your /etc/samba/lmhosts file. Normally, 127.0.0.2 will be in there with the name of your machine (and 127.0.0.1 will be there with there as "localhost", which I believe is called the "loopback" ip address). For some reason, I commented out 127.0.0.2, but I can't remember why. 127.0.0.1 is still uncommented. Greg Wallace
On Tuesday 14 June 2005 02:29, Greg Wallace wrote:
Is that IP address a valid internal one? Could that be the cause of the problem?
--
How do I tell if it's a valid one? I know 127.0.0.1 is valid:
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8699 errors:0 dropped:0 overruns:0 frame:0 TX packets:8699 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2750512 (2.6 Mb) TX bytes:2750512 (2.6 Mb)
Jerome
Take a look at your /etc/samba/lmhosts file. Normally, 127.0.0.2 will be in there with the name of your machine (and 127.0.0.1 will be there with there as "localhost", which I believe is called the "loopback" ip address). For some reason, I commented out 127.0.0.2, but I can't remember why. 127.0.0.1 is still uncommented.
Greg Wallace
file:/etc/samba/lmhosts # This file provides the same function that the lmhosts file does for # Windows. It's another way to map netbios names to ip addresses. # # See section 'name resolve order' in the manual page of smb.conf for # more information. 127.0.0.1 localhost 127.0.0.2 is not in the file. Jerome
On Mon, 2005-06-13 at 07:59 -1000, Susemail wrote:
How do I tell if it's a valid one? I know 127.0.0.1 is valid:
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8699 errors:0 dropped:0 overruns:0 frame:0 TX packets:8699 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2750512 (2.6 Mb) TX bytes:2750512 (2.6 Mb)
Jerome
If someone already pointed this out, please discard my comment: 1. As you can see, "lo" is Local Loopback interface. Even if your linux machine is not connected network at all, you can always "ping" any IP addresses in this subnet, which are 127.0.0.1 - 127.255.255.254. Those ping packets never go out through your ethernet port. 2. If you have any ethernet interface, you should have "eth0" interface like below, in addition to "lo": suse93-2:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:0B:6A:2C:B0:45 inet addr:192.168.254.2 Bcast:192.168.254.255 Mask:255.255.255.0 inet6 addr: fe80::20b:6aff:fe2c:b045/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5410 errors:0 dropped:0 overruns:0 frame:0 TX packets:5166 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3035562 (2.8 Mb) TX bytes:631546 (616.7 Kb) Interrupt:11 Base address:0xbc00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:938 errors:0 dropped:0 overruns:0 frame:0 TX packets:938 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:74812 (73.0 Kb) TX bytes:74812 (73.0 Kb) "eth0" is the real ethernet interface. Please check this at your PC. Toshi
On Monday 13 June 2005 01:25, Greg Wallace wrote:
I share a linux directory with my Windows machine. Try adding --
wins support = yes security = share
to your [global] section.
Also, I have the following for my "share" (I called it Shareddocs just to have it stick out as a Windows share). I'm forcing the user to the Linux built-in nobody group.
[SharedDocs] path = /etc/samba/smbusers guest ok = yes guest account = nobody force group = MYHOME
Also, be sure the nobody user is set up as a member of the MYHOME group on your Linux machine. Whatever privileges you give it, that's what you'll be able to do from your Windows machine. Also, your Windows machine has to be using the MYHOME workgroup, which I assume it does.
Greg Wallace
Greg, I added 'wins support = yes' and 'security = share' as you suggested and now all the default shares set up by Yast can be seen in 'My Network Places'. The problem is when I enter the User name and password in the login window Windows prepends the name of my Windows machine to my User name like this: MYVIAO/MyUserName and reopens the login window. Windows does give a hint: Example: User Name username@domain DOMAIN\username How do I interpet this? I tried myusername@Linux\myusername and myusername@LinuxLINUX\myusername . Nothing is prepended but hitting enter reopens the login window. I also have a question about adding a share the way you suggested above. Do I create a folder called SharedDoc somewhere to hold the information I want to share? Thanks, Jerome
On Monday 13 June 2005 06:08, Jerome Lyles wrote:
[global] workgroup = MYHOME
netbios name = MYSAMBASERVER
Either put a # in front of the above line
map to guest = Bad User username map = /etc/samba/smbusers printcap cache time = 750 printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s
When I run smbclient to list my shares I get this:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
or use this smbclient -L //MYSAMBASERVER If you comment out "netbios name", then use smbclient -L //linux And do a man smb.conf in the end and search for "netbios name" parameter.
On Tuesday 14 June 2005 04:00, Silviu Marin-Caea wrote:
# smbclient -L Linux Error connecting to 127.0.0.2 (Connection refused) Connection to Linux failed
or use this smbclient -L //MYSAMBASERVER
If you comment out "netbios name", then use smbclient -L //linux
And do a man smb.conf in the end and search for "netbios name" parameter.
Thank you Silviu, I read the "netbios name" parameter and realized I didn't have to change the name at all since the default is the name of my machine. So I used Yast to delete the change and then I ran: smbclient -L //Linux and the command worked as expected. This problem started here: # smbclient -L Linux; no '//'. Now to apply the other suggestions. Thanks again, Jerome
participants (7)
-
Greg Wallace -
Jerome Lyles -
Ken Schneider -
Kevanf1 -
Silviu Marin-Caea -
Susemail
-
Toshi Esumi