I also had problems connecting to NT network and never found anything on the internet or Suse about how to do this. (Suse Support will not help with network unless you pay them) Here is what I did. Go to control panel, network, windows share. Enter the information there. Go to Lan Browsing, enter the domain name, then apply. Install LinNeighborhood from the Suse 7.3 CD. Open LinNeighborhood (Internet, Tools), then do the setup on it under Options, Preferences. You can enter your logon and password. Then you go to Options, Browse entire network. You should be able to see all of the windows shares. You can then select the folder or drive and mount it. This should put it in your home directory. You can close LinNeighborhood, and then browse the share with Konqueror or other file manager. When you shutdown and start up again, all you have to do is to open LinNeighborhood again, let it mount the drives automatically, then close it again. You could also have LinNeighborhood start automatically. You can also use Komba2, but I have not tried that yet. Art -----Original Message----- From: Hugh Foster [mailto:HughFoster@Servisair.com] Sent: Wednesday, March 20, 2002 7:39 AM To: suse-linux-e@suse.com Subject: [SLE] Baffled newbie trying to reach NT LAN Hello list. I am getting to grips with SUSE 7.2, slowly, but I cannot manage to get the network set up properly. I have started SAMBA (I think) and set up my network card. I can PING things, so far so good. But everytime I click Local Network in the KDE file manager, it says I'm not set up properly and should go to the LISa setup screen and configure the settings there. But I don't understand what those settings mean! Moreover, I have scoured the manuals and help systems and cannot find any instructions for it anywhere. Argh. Help? Best regards, Hugh Foster System Support Analyst Servisair (UK) Ltd. hughfoster@servisair.com www.servisair.com "Reboot the PC and try it again" This e-mail may contain material of a private and highly confidential nature. No authority either express or implied is given to any person other than the intended recipient(s) to read, disclose or act upon its contents or attachments. If you are not the intended recipient please destroy this e-mail together with any embedded, associated or attached documents or files. [This express obligation of confidence may be used as evidence should any legal action arise concerning the misuse of this message or its attachments etc as any unauthorised use or disclosure of them is strictly prohibited]. Any comments or statements made are not necessarily those of the Company, its holding company, subsidiaries, or affiliates. The copyright holder shall not be liable for any loss of profit, interruption of business, damage to equipment or data or any other damage, including but not limited to direct, special, incidental or consequential damages. Any other remedy that would otherwise be available in law or equity is hereby excluded except to the extent that such exclusion would be void or is prohibited by law.
On Thursday 21 March 2002 01:27, Art wrote:
Go to control panel, network, windows share. Enter the information there. Go to Lan Browsing, enter the domain name, then apply. Install LinNeighborhood from the Suse 7.3 CD. Open LinNeighborhood (Internet, Tools), then do the setup on it under Options, Preferences. You can enter your logon and password.
This is very clear and concise. This should have been in the manual! One thing I don't understand is the relationship between DNZ and DHCP in SuSE. In my case, I am using SuSE 7.3 on a dual boot (with Win 2k) and am connected to a LinkSys router and a cable modem. In otherwords, I have both a WAN and a LAN. The LAN is made up of 3 Win 98 SE computers. Before I could access my Internet connection, I needed to fill out a hostname and a domain name. This is based on DNS configuration as far as I can tell. As I don't need this for Internet access (using DHCP), I filled these out like I would in Windows: Hostname (computer name): thor, Domain (workgroup): asgaard. While I realize that hostname-computer name and domain-workgroup are not really equivalent, I have not been able to ascertain how the two are related despite extensive reading of late. I believe that I may have setup my network configuration incorrectly, but hey, it has worked until now. The problem for me is also with using the smbclient and LinNeighbothood to access the Win machines on my LAN. When I open a shell, the prompt is <user>@thor According to "Broadband Internet Connections: A User's Guide to DSL and Cable." by Roderick W. Smith, it is possible to setup a DNS like thor.asgaard.invalid but I am unsure what use this is in my situation. The crux of the problem seems to be the mix between DHCP and DNS that is forced on me by the configuration parameters for getting an Internet connection, but what to correct, I am unsure. Any ideas? Cheers, Brian BTW, all of the above is in reference to using the smbclient. I am not serving SMB.
Brian Durant wrote:
This is very clear and concise. This should have been in the manual! One thing I don't understand is the relationship between DNZ and DHCP in SuSE.
DHCP is a way to dynamically assign all the variables needed to connect to a network, such as IP, netmask, gateway, etc. DNS is the service that translates names that makes sense to people, to IP numbers that make sense to computers. The protocol and service doesn't vary between SuSE and anyone else on the internet. ;-) Maybe the programs used do, but that is the freedom of Linux, standards compliant software that works everywhere.
In my case, I am using SuSE 7.3 on a dual boot (with Win 2k) and am connected to a LinkSys router and a cable modem. In otherwords, I have both a WAN and a LAN. The LAN is made up of 3 Win 98 SE computers. <snip> The crux of the problem seems to be the mix between DHCP and DNS that is forced on me by the configuration parameters for getting an Internet connection, but what to correct, I am unsure. Any ideas?
First, that is not your problem. I have DHCP supplied parameters for my cable modem. That affects my eth0, not eth1 which goes to my home network (Win98). If your problem is name resolution, add the IPs of your LAN to /etc/hosts AND /etc/lmhosts (this is for samba). HTH, but I am not exactly sure what your problem or question is. Also, as good list netiquette, you need not add several list members to your emails. This only gives them two messages, as they will get the one via the list. With all the scanning that I have seen going on lately, we need to conserve the bandwidth. :-) -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871
On Thursday 21 March 2002 17:26, you wrote:
DHCP is a way to dynamically assign all the variables needed to connect to a network, such as IP, netmask, gateway, etc. DNS is the service that translates names that makes sense to people, to IP numbers that make sense to computers. The protocol and service doesn't vary between SuSE and anyone else on the internet. ;-) Maybe the programs used do, but that is the freedom of Linux, standards compliant software that works everywhere.
OK, but if DHCP is administered dynamically, then there is nothing to fill in, but you need to fill in something to get an Internet connection with SuSE. In the Win or Mac world, if your access to the Internet is administered dynamically, then there is nothing to fill in or see, unless you want to enforce a static IP. In this case (and only this case), I find the DNS confusing for the following reasons: 1) The dynamic administration of DHCP that I mentioned above, which usually includes not needing to include a domain, unless the individual is serving their own domain directly to the Internet. Albeit, there are some ISP's that require filling out this info such as cb.net.id. 2) The issue of hostname-computer name and domain-workgroup Linux-Win. Isn't there a clean cut way of applying this in SuSE? There are two options that I have spotted. One in KDE control center, which is called "user" and "workgroup". The other in YAST2, where "hostname" and "domain name" can be filled out. "User" is not necessarily "computer name". These are concepts that are hard to wrap my head around compared to past experience in other OS's 3) Where does my LAN start and my WAN end? If I want to have a computer called "x" and a workgroup that I want to call "y", but log onto an ISP domain called cbn.net.id and have a "username" on that ISP of "z", where do the different blanks need to be filled in in SuSE to complete this?
First, that is not your problem. I have DHCP supplied parameters for my cable modem. That affects my eth0, not eth1 which goes to my home network (Win98). If your problem is name resolution, add the IPs of your LAN to /etc/hosts AND /etc/lmhosts (this is for samba). HTH, but I am not exactly sure what your problem or question is.
OK, I have an eth0 that connects to my router. I do have an eth1 that I haven't configured yet, but I haven't done that yet as it is not connected to anything at this time. The diference between your configuration and mine seems to be that my LAN is connected to a hardware router that is connected to the cable modem (i.e. WAN). Why would I add IPs of my LAN to "/etc/hosts AND /etc/lmhosts"? I am not hosting anything. I just want to be able to log on to the other computers. The other computers on my LAN do not have static IP addresses anyway. Everything is assigned automagically.
Also, as good list netiquette, you need not add several list members to your emails. This only gives them two messages, as they will get the one via the list. With all the scanning that I have seen going on lately, we need to conserve the bandwidth. :-)
Noted. I only included them as I have discussed parts of this issue with the "cc'd" before. Cheers, Brian
Brian Durant wrote:
On Thursday 21 March 2002 17:26, you wrote:
DHCP is a way to dynamically assign all the variables needed to connect to a network, such as IP, netmask, gateway, etc. DNS is the service that translates names that makes sense to people, to IP numbers that make sense to computers. The protocol and service doesn't vary between SuSE and anyone else on the internet. ;-) Maybe the programs used do, but that is the freedom of Linux, standards compliant software that works everywhere.
OK, but if DHCP is administered dynamically, then there is nothing to fill in, but you need to fill in something to get an Internet connection with SuSE.
You only need to install the Nic, assign it a number, enable it, and set it to dhclient. You can either go with the default config or you CAN modify it.
In the Win or Mac world, if your access to the Internet is administered dynamically, then there is nothing to fill in or see, unless you want to enforce a static IP.
That is not entirely true, though dhcp client is the default config in Windows, and their defaults, which a lot of DHCP servers are configured for, will usually work (but not always).
In this case (and only this case), I find the DNS confusing for the following reasons:
I thought we were talking about DHCP. DNS is a seperate service. It is usually configured on your computer by DHCP in that environment for name resolution (otherwise you would need to know all IP numbers for everything).
1) The dynamic administration of DHCP that I mentioned above, which usually includes not needing to include a domain, unless the individual is serving their own domain directly to the Internet. Albeit, there are some ISP's that require filling out this info such as cb.net.id.
The fact that some do and some don't is EXACTLY why things are configurable in Linux. It will work (maybe some configuring) everywhere. Microsoft tries to create a proprietary everything that they can control, so it is not surprising theirs usually works by default since most ISPs have to assume the majority of clients that connect to them will run M$.
2) The issue of hostname-computer name and domain-workgroup Linux-Win. Isn't there a clean cut way of applying this in SuSE? There are two options that I have spotted. One in KDE control center, which is called "user" and "workgroup". The other in YAST2, where "hostname" and "domain name" can be filled out. "User" is not necessarily "computer name". These are concepts that are hard to wrap my head around compared to past experience in other OS's
That is probably because you used a non networking OS. User is not the same as the computer name, even in Windows. The confusion in the terms is a result of M$ attempt to proprietize the computer software industry. User = user, the one using the computer at any given moment. Hostname=computer name, domain name is almost the same as workgroup.
3) Where does my LAN start and my WAN end? If I want to have a computer called "x" and a workgroup that I want to call "y", but log onto an ISP domain called cbn.net.id and have a "username" on that ISP of "z", where do the different blanks need to be filled in in SuSE to complete this?
This sounds like a dialup, so whatever program is used to interface with your ISP would take 'z' with the appropriate password. Remember, each server you connect to (not pass through) will authenticate you to make sure you are a valid user, so you may have many usernames/passwords, one each for each server. This is different than your computer name/domain name. This your ISP may be using to make an entry in their DNS server (maybe you are confusing the dynamic updating of DNS with DHCP), though I doubt it unless you are web hosting or something.
OK, I have an eth0 that connects to my router. I do have an eth1 that I haven't configured yet, but I haven't done that yet as it is not connected to anything at this time. The diference between your configuration and mine seems to be that my LAN is connected to a hardware router that is connected to the cable modem (i.e. WAN). Why would I add IPs of my LAN to "/etc/hosts AND /etc/lmhosts"? I am not hosting anything. I just want to be able to log on to the other computers. The other computers on my LAN do not have static IP addresses anyway. Everything is assigned automagically.
I can only assume your ISP does dynamic DNS updating through DHCP, which makes an entry in their DNS server that would be able to translate your hostnames to IP addresses. If that assumption is correct, you should be able to connect to them through their name assuming nothing is being blocked by a firewall. If your other machines are Win98 (if I remember), are you sharing your drives to the internet? What do you mean by 'log on to the other computers'. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871
On Thursday 21 March 2002 20:37, you wrote:
Brian Durant wrote:
DHCP is a way to dynamically assign all the variables needed to connect to a network, such as IP, netmask, gateway, etc. DNS is the service that translates names that makes sense to people, to IP numbers that make sense to computers. The protocol and service doesn't vary between SuSE and anyone else on the internet. ;-) Maybe the programs used do, but that is the freedom of Linux, standards compliant software that works everywhere.
OK, but if DHCP is administered dynamically, then there is nothing to fill in, but you need to fill in something to get an Internet connection with SuSE.
You only need to install the Nic, assign it a number, enable it, and set it to dhclient. You can either go with the default config or you CAN modify it.
This is what I have done. This is also how I got my Internet connection to work.
In the Win or Mac world, if your access to the Internet is administered dynamically, then there is nothing to fill in or see, unless you want to enforce a static IP.
That is not entirely true, though dhcp client is the default config in Windows, and their defaults, which a lot of DHCP servers are configured for, will usually work (but not always).
In this case (and only this case), I find the DNS confusing for the following reasons:
I thought we were talking about DHCP. DNS is a separate service. It is usually configured on your computer by DHCP in that environment for name resolution (otherwise you would need to know all IP numbers for everything).
We were talking about DHCP, but I believe that the explanation I originally received for the necessity of filling out the host and domain names in YAST2 is that this is for DNS. Perhaps I am wrong. Maybe it was in connection with that some ISPs require a host name and domain name. In my case, it wasn't necessary. All I know is that I couldn't get a connection before I put something in those fields, regardless of what was put in those fields. I chose to interpret the host name as more or less = with the "computer name" in Win and domain with "workgroup". It may not be used by me for accessing the Internet, but I need to fill out those fields before I can get a connection. Why this is necessary, I have nary a clue, but that is the explanation that I received.
1) The dynamic administration of DHCP that I mentioned above, which usually includes not needing to include a domain, unless the individual is serving their own domain directly to the Internet. Albeit, there are some ISP's that require filling out this info such as cb.net.id.
The fact that some do and some don't is EXACTLY why things are configurable in Linux. It will work (maybe some configuring) everywhere. Microsoft tries to create a proprietary everything that they can control, so it is not surprising theirs usually works by default since most ISPs have to assume the majority of clients that connect to them will run M$.
This I understand and do to a large extent agree with your point of view. but does it bring me closer to understanding my configuration problem and how to solve?
2) The issue of hostname-computer name and domain-workgroup Linux-Win. Isn't there a clean cut way of applying this in SuSE? There are two options that I have spotted. One in KDE control center, which is called "user" and "workgroup". The other in YAST2, where "hostname" and "domain name" can be filled out. "User" is not necessarily "computer name". These are concepts that are hard to wrap my head around compared to past experience in other OS's
That is probably because you used a non networking OS. User is not the same as the computer name, even in Windows. The confusion in the terms is a result of M$ attempt to proprietize the computer software industry. User = user, the one using the computer at any given moment. Hostname=computer name, domain name is almost the same as workgroup.
Noted. Is Win or Mac a non networking OS in your definition?
3) Where does my LAN start and my WAN end? If I want to have a computer called "x" and a workgroup that I want to call "y", but log onto an ISP domain called cbn.net.id and have a "username" on that ISP of "z", where do the different blanks need to be filled in in SuSE to complete this?
This sounds like a dialup, so whatever program is used to interface with your ISP would take 'z' with the appropriate password. Remember, each server you connect to (not pass through) will authenticate you to make sure you are a valid user, so you may have many usernames/passwords, one each for each server. This is different than your computer name/domain name. This your ISP may be using to make an entry in their DNS server (maybe you are confusing the dynamic updating of DNS with DHCP), though I doubt it unless you are web hosting or something.
No, no. I did say cable modem and router. You still need to log on to the POP3 server for example. As far as I know, ISPs still use the same user name for POP3 as for a dial up connection, even if you don't have that dial up connection ;-) That is the way my ISP functions, anyway.
OK, I have an eth0 that connects to my router. I do have an eth1 that I haven't configured yet, but I haven't done that yet as it is not connected to anything at this time. The difference between your configuration and mine seems to be that my LAN is connected to a hardware router that is connected to the cable modem (i.e. WAN). Why would I add IPs of my LAN to "/etc/hosts AND /etc/lmhosts"? I am not hosting anything. I just want to be able to log on to the other computers. The other computers on my LAN do not have static IP addresses anyway. Everything is assigned automagically.
I can only assume your ISP does dynamic DNS updating through DHCP, which makes an entry in their DNS server that would be able to translate your hostnames to IP addresses. If that assumption is correct, you should be able to connect to them through their name assuming nothing is being blocked by a firewall. If your other machines are Win98 (if I remember), are you sharing your drives to the internet? What do you mean by 'log on to the other computers'.
OK, how do I connect through the computer name? All I see in the KDE control center (when logged on as "root") are IP addresses listed as examples. Can I just add names in LISa? Should they be in capital letters or small? Nothing is being shared to the Internet. By "logging on", I mean connecting to the other computers so that I can mount their hard drives. Cheers, Brian
Brian Durant wrote:
We were talking about DHCP, but I believe that the explanation I originally received for the necessity of filling out the host and domain names in YAST2 is that this is for DNS. Perhaps I am wrong.
This may be true, but this you also have to do in Windows when it is installed, just before you agree to their license.
This I understand and do to a large extent agree with your point of view. but does it bring me closer to understanding my configuration problem and how to solve?
Noted. Is Win or Mac a non networking OS in your definition?
What I mean is you don't 'have' to login (and at least with Windows can easily bypass any pseudo login). It really doesn't have a true concept of a user, such as NT, W2000, Linux, etc. I consider them more of a desktop OS.
OK, how do I connect through the computer name? All I see in the KDE control center (when logged on as "root") are IP addresses listed as examples. Can I just add names in LISa? Should they be in capital letters or small? Nothing is being shared to the Internet. By "logging on", I mean connecting to the other computers so that I can mount their hard drives.
From what I have seen, LISa is to be used to browse network shares, not samba shares. Have you tried in Konquerer smb://"computername"/"share name", i.e smb://jmorris/C. To mount the drives, you need to be root. Try mount -t smbfs -o rw,user,username=(yourusername for the share), password=(passwd for that share) //"computername"/"sharename" mountpoint, or. i.e. mount -t smbfs -o rw,user,username=joe,password=xxxxx //jmorris/C /mnt/samba. If all you are going to do it read/write, I can do it with my Windows machine downstairs through Konq with smb:// as above. HTH -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871
On Thursday 21 March 2002 22:02, you wrote:
From what I have seen, LISa is to be used to browse network shares, not samba shares. Have you tried in Konquerer smb://"computername"/"share name", i.e smb://jmorris/C. To mount the drives, you need to be root. Try mount -t smbfs -o rw,user,username=(yourusername for the share), password=(passwd for that share) //"computername"/"sharename" mountpoint, or. i.e. mount -t smbfs -o rw,user,username=joe,password=xxxxx //jmorris/C /mnt/samba. If all you are going to do it read/write, I can do it with my Windows machine downstairs through Konq with smb:// as above.
Logging in as root is impracticable as I transfer files from my machine to the Win boxes, but also need to share a printer over the LAN. I don't have a printer connected to my computer yet and am forced to share a printer. Logging on as root every time I want to print a document is not really something I would feel comfortable with. AFAIK, printer sharing is not one of the things that Konq can do. To get back on track with trying to solve my problem, I will include the text from the original message from Art and will add comments:
Go to control panel, network, windows share. Enter the information there.
"Default user name" is this the "computer name" that I am working from or is it literally "user name"? I ask, because as I see it, on a home LAN, it is more important to know which computer is connected than which user. Our family members sometimes switch computer if there are performance or technical problems with one or more of the computers.
Go to LAN Browsing, enter the domain name, then apply.
What domain name? I am not using DNS, why do I need to enter a domain name? Is this the same "domain name" that I had to fill in to get my Internet connection working with YAST2 ?
Install LinNeighborhood from the Suse 7.3 CD. Open LinNeighborhood (Internet, Tools), then do the setup on it under Options, Preferences. You can enter your logon and password.
"logon" is that "user name", "computer name" or doesn't it matter?
Then you go to Options, Browse entire network. You should be able to see all of the windows shares. You can then select the folder or drive and mount it. This should put it in your home directory. You can close LinNeighborhood, and then browse the share with Konqueror or other file manager.
What procedure do I need to go through to access a printer on the LAN with LinNeighborhood? Cheers, Brian
Brian Durant wrote:
Logging in as root is impracticable as I transfer files from my machine to the Win boxes, but also need to share a printer over the LAN.
I don't know how you got from transfering files to printers, but my networked Win98 also serves up my (win only?) printer.
I don't have a printer connected to my computer yet and am forced to share a printer. Logging on as root every time I want to print a document is not really something I would feel comfortable with.
Why do you need to log in as root to print?
AFAIK, printer sharing is not one of the things that Konq can do.
Konq is a web/file browser. It neither shares printers nor files.
Go to control panel, network, windows share. Enter the information there.
"Default user name" is this the "computer name" that I am working from or is it literally "user name"?
Where is this exactly. If you mean the Identification tab, it is the computer name.
I ask, because as I see it, on a home LAN, it is more important to know which computer is connected than which user. Our family members sometimes switch computer if there are performance or technical problems with one or more of the computers.
If you are talking about a resource of a computer, such as a HD or printer, it is always refered to its source as the computer, not the user.
Go to LAN Browsing, enter the domain name, then apply.
What domain name? I am not using DNS, why do I need to enter a domain name? Is this the same "domain name" that I had to fill in to get my Internet connection working with YAST2 ?
I believe he is refering to the workgroup, the 'name' of the network group. If you are going to browse networked resources, it follows this scheme- Workgroup>Computer>Share. If you are a part of the workgroup, you only need Computer>Share. If your ISP requires you to set your domain name to match their domain, you would just need to navigate to your shares via Workgroup>Computer>Share, IIRC.
Install LinNeighborhood from the Suse 7.3 CD. Open LinNeighborhood (Internet, Tools), then do the setup on it under Options, Preferences. You can enter your logon and password.
"logon" is that "user name", "computer name" or doesn't it matter?
It would depend on HOW you shared your HD in Windows. If you gave Full access without password, you don't need this.
Then you go to Options, Browse entire network. You should be able to see all of the windows shares. You can then select the folder or drive and mount it. This should put it in your home directory. You can close LinNeighborhood, and then browse the share with Konqueror or other file manager.
What procedure do I need to go through to access a printer on the LAN with LinNeighborhood?
You don't. Use CUPS, configure with K>System>Tools>Cups administration tool. I am a bit confused, are you trying to browse your Windows shared Hard Drives, or are you trying to print to a Windows shared printer, or both, or what exactly? If you just want to see your Windows shares (HD or printer), type in the location field in Konq smb://(computer name of your windows machine). If that doesn't work, what does it give you? -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871
On Saturday 23 March 2002 15:05, you wrote:
Logging in as root is impracticable as I transfer files from my machine to the Win boxes, but also need to share a printer over the LAN.
I don't know how you got from transfering files to printers, but my networked Win98 also serves up my (win only?) printer.
I am trying to connect to the Win boxes on my LAN. That is why I am trying to get the smb client working, preferably with LinNeighborhood as per the instructions in Art's e-mail Printing has become a topic because you stated as follows in a previous mail:
From what I have seen, LISa is to be used to browse network shares, not samba shares. Have you tried in Konquerer smb://"computername"/"share Try mount -t smbfs -o rw,user,username=(yourusername for the share), password=(passwd for that share) //"computername"/"sharename" mountpoint, or. i.e. mount -t smbfs -o rw,user,username=joe,password=xxxxx //jmorris/C /mnt/samba. If all you are going to do it read/write, I can do it with my Windows machine downstairs through Konq with smb:// as above.
This obviously does not help me much if I also need to print. Nor does it follow the instructions that were provided in Art's mail, which I am trying to follow as stringently as possible, so that I can get this issue solved as quickly as possible.
I don't have a printer connected to my computer yet and am forced to share a printer. Logging on as root every time I want to print a document is not really something I would feel comfortable with.
Why do you need to log in as root to print?
AFAIK, printer sharing is not one of the things that Konq can do.
This is another attempt to direct the issue at hand back to Art's original e-mail. I am simply pointing out (again) that your suggestion of using Konq will not help me, but is simply muddying the waters in relationship to Art's original e-mail instructions.
Konq is a web/file browser. It neither shares printers nor files.
Go to control panel, network, windows share. Enter the information there.
"Default user name" is this the "computer name" that I am working from or is it literally "user name"?
Where is this exactly. If you mean the Identification tab, it is the computer name.
Look above, it states KDE control center "panel", network, windows share. That is where it is necessary to fill out the "default user name". Now, does this literally mean "user name" or "computer name"?
I ask, because as I see it, on a home LAN, it is more important to know which computer is connected than which user. Our family members sometimes switch computer if there are performance or technical problems with one or more of the computers.
If you are talking about a resource of a computer, such as a HD or printer, it is always referred to its source as the computer, not the user.
Exactly, which is why the requirement of filling out "user name" in KDE -> Control Center-> Network -> Windows Share is confusing for me. My conclusion is that "user name" means "user name" in this field, but as you rightly stated in one of your earlier e-mails:
What I mean is you don't 'have' to login (and at least with Windows can easily bypass any pseudo login). It really doesn't have a true concept of a user, such as NT, W2000, Linux, etc.
Therefore, I don't see the purpose except to hold the hand of former Win users.
Go to LAN Browsing, enter the domain name, then apply.
What domain name? I am not using DNS, why do I need to enter a domain name? Is this the same "domain name" that I had to fill in to get my Internet connection working with YAST2 ?
I believe he is referring to the workgroup, the 'name' of the network group. If you are going to browse networked resources, it follows this scheme- Workgroup>Computer>Share. If you are a part of the workgroup, you only need Computer>Share.
I am part of the work group in the sense of that I created it, but the others on my LAN are only desktop users and do not use the work group for anything. It is there for my convenience. How do I "become" a member of the "work group" in SuSE?
If your ISP requires you to set your domain name to match their domain, you would just need to navigate to your shares via Workgroup>Computer>Share, IIRC.
We have been through this discussion before. My ISP does not require me to set a domain name, but YAST2 did, before I could get my Internet connection working. Therefore I made the assumption that the "host name" field in YAST2 was mor or less equivalent to "computer name" in the Win world and that "domain name" was more or less equivalent to "work group" in the Win world.
Install LinNeighborhood from the Suse 7.3 CD. Open LinNeighborhood (Internet, Tools), then do the setup on it under Options, Preferences. You can enter your logon and password.
"logon" is that "user name", "computer name" or doesn't it matter?
It would depend on HOW you shared your HD in Windows. If you gave Full access without password, you don't need this.
Noted.
Then you go to Options, Browse entire network. You should be able to see all of the windows shares. You can then select the folder or drive and mount it. This should put it in your home directory. You can close LinNeighborhood, and then browse the share with Konqueror or other file manager.
What procedure do I need to go through to access a printer on the LAN with LinNeighborhood?
You don't. Use CUPS, configure with K>System>Tools>Cups administration tool.
Do you mean "print job administrator"? I haven't been able to set up a printer in YAST2. So I don't believe the KDE tool "print job administrator" will help.
I am a bit confused, are you trying to browse your Windows shared Hard Drives, or are you trying to print to a Windows shared printer, or both, or what exactly?
Both.
If you just want to see your Windows shares (HD or printer), type in the location field in Konq smb://(computer name of your windows machine). If that doesn't work, what does it give you?
smb://"computer name" gave me: "Could not connect to host "computer name" smb://"computer name"/"share" gave me: "Unknown error. Hmm..." I am also unable to get any Win shares in LinNeighborhood, when logged on as "usr". I am sure that the LAN is working, because I can easily access the Win computers when I boot up with Win 2k on my computer. This tells me that something must not be configured correctly on my SuSE boot and my gut feeling tells me it has to do with the "host and domain" name fields in YAST2, but I don't seem to get any closer to a resolution to this issue. Cheers, Brian
Brian Durant wrote:
I am trying to connect to the Win boxes on my LAN. That is why I am trying to get the smb client working, preferably with LinNeighborhood as per the instructions in Art's e-mail Printing has become a topic because you stated as follows in a previous mail:
I am sorry, but the following has nothing to do with printing. It is to be able to browse or mount your Window's shared hard drive.
From what I have seen, LISa is to be used to browse network shares, not samba shares. Have you tried in Konquerer smb://"computername"/"share Try mount -t smbfs -o rw,user,username=(yourusername for the share), password=(passwd for that share) //"computername"/"sharename" mountpoint, or. i.e. mount -t smbfs -o rw,user,username=joe,password=xxxxx //jmorris/C /mnt/samba. If all you are going to do it read/write, I can do it with my Windows machine downstairs through Konq with smb:// as above.
This obviously does not help me much if I also need to print. Nor does it follow the instructions that were provided in Art's mail, which I am trying to follow as stringently as possible, so that I can get this issue solved as quickly as possible.
I'm sorry, I have long since deleted the original emails. I can't help you follow Art's instructions. But, you are not going to use smbclient to print, nor LinNeighborhood. They are programs to browse the shares on a network. If you want to see a Windows share from your Linux machine (see above subject :-) ), you can type on a command line (i.e. xterm) smbclient -L (computer name) -You fill in the name. If you want to print, you will use lprold, lprng, or cups. I would recommend CUPS to print to your Windows served printer, and your printing program will use samba_print to actually print through the network to your Windows printer. If this is different than Art's instructions, and that is what you are comfortable with, then just delete this email.
AFAIK, printer sharing is not one of the things that Konq can do.
This is another attempt to direct the issue at hand back to Art's original e-mail. I am simply pointing out (again) that your suggestion of using Konq will not help me, but is simply muddying the waters in relationship to Art's original e-mail instructions.
Sorry, can't help there.
Go to control panel, network, windows share. Enter the information there.
"Default user name" is this the "computer name" that I am working from or is it literally "user name"?
Where is this exactly. If you mean the Identification tab, it is the computer name.
Look above, it states KDE control center "panel", network, windows share. That is where it is necessary to fill out the "default user name". Now, does this literally mean "user name" or "computer name"?
Again, miscommunication. As you noted above, it is control center in KDE. I thought you were talking about the Windows machine, which does have control panel>network. The default user name is exactly that. If you set up your Windows (in Windows) to share based on password, then this setting would give it that username and password. If you set up your Windows HD for full access (meaning no password is needed), this is not even needed. BTW, user name is user name, not computer name. This is to authenticate your Linux machine (using Samba) to your password protected Windows shares. I hope that is now clear. ;-)
I ask, because as I see it, on a home LAN, it is more important to know which computer is connected than which user. Our family members sometimes switch computer if there are performance or technical problems with one or more of the computers.
If you are talking about a resource of a computer, such as a HD or printer, it is always referred to its source as the computer, not the user.
Exactly, which is why the requirement of filling out "user name" in KDE -> Control Center-> Network -> Windows Share is confusing for me. My conclusion is that "user name" means "user name" in this field, but as you rightly stated in one of your earlier e-mails:
What I mean is you don't 'have' to login (and at least with Windows can easily bypass any pseudo login). It really doesn't have a true concept of a user, such as NT, W2000, Linux, etc.
Therefore, I don't see the purpose except to hold the hand of former Win users.
See above.
I am part of the work group in the sense of that I created it, but the others on my LAN are only desktop users and do not use the work group for anything. It is there for my convenience. How do I "become" a member of the "work group" in SuSE?
If you are not sharing resources with Windows via Samba (which you would put it in smb.conf), then putting it in Control center for Windows shares will basically allow you to skip the workgroup level (since this would be done by the setting for workgroup) in (I believe) Konquerer (the KDE default file browser).
Then you go to Options, Browse entire network. You should be able to see all of the windows shares. You can then select the folder or drive and mount it. This should put it in your home directory. You can close LinNeighborhood, and then browse the share with Konqueror or other file manager.
What procedure do I need to go through to access a printer on the LAN with LinNeighborhood?
You don't. Use CUPS, configure with K>System>Tools>Cups administration tool.
Do you mean "print job administrator"? I haven't been able to set up a printer in YAST2. So I don't believe the KDE tool "print job administrator" will help.
No. Do you have Cups installed (it is several different rpms)? Kups is the program I was refering to, because on my network (Windows shared Canon Multipass c-5500), Yast2 could not set it up. Kups did it quite impressively, IMHO.
If you just want to see your Windows shares (HD or printer), type in the location field in Konq smb://(computer name of your windows machine). If that doesn't work, what does it give you?
smb://"computer name" gave me:
I'm sorry, I was not clear enough. You need to supply the names of your Windows computers, not use computername. Also, if your Windows machines are not in your /etc/hosts file or /etc/lmhosts, and you are not running DNS (which I believe you said), it still wouldn't work (you could enter them though :-) ). As a quick work around, just supply the IP address of your windows machine with the shared drive/printer, i.e. smb://192.168.1.2 {replace with the IP of one of YOUR machines). That should work.
-- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871
On Saturday 23 March 2002 22:01, you wrote:
If you want to see a Windows share from your Linux machine (see above subject :-) ), you can type on a command line (i.e. xterm) smbclient -L (computer name) -You fill in the name.
I have had no luck with this. I suspect, for the same reason that LinNeighborhood hasn't worked.
If you want to print, you will use lprold, lprng, or cups. I would recommend CUPS to print to your Windows served printer, and your printing program will use samba_print to actually print through the network to your Windows printer.
OK, I see now that printing and smb shares are two very different kettle of fish in Linux. Let's stick to trying to get the smb shares to appear for now, if you are up to it ;-) If we can get it to work without LinNeighborhood, then I will accept this, but it has been about 15 yrs. since I used DOS. I feel totally blind in the command line after having used Macintosh for so long 8-) That is why I have been trying to stick to Art's instructions.
Again, miscommunication. As you noted above, it is control center in KDE. I thought you were talking about the Windows machine, which does have control panel>network.
Not my error, I was quoting from the original e-mail instructions.
The default user name is exactly that. If you set up your Windows (in Windows) to share based on password, then this setting would give it that username and password. If you set up your Windows HD for full access (meaning no password is needed), this is not even needed. BTW, user name is user name, not computer name. This is to authenticate your Linux machine (using Samba) to your password protected Windows shares. I hope that is now clear. ;-)
I believe so. However, if you are using a Win machine and browse your "network neighborhood", you are doing this using the computer name to identify the other computers. As the DHCP/DNS issue has had me so confused, I would just like to verify that my SuSE computer name is what I think it is.
If you are not sharing resources with Windows via Samba (which you would put it in smb.conf), then putting it in Control center for Windows shares will basically allow you to skip the workgroup level (since this would be done by the setting for workgroup) in (I believe) Konquerer (the KDE default file browser).
And "user name" only needs to be filled out in the KDE control center for Win shares if the Win HD is set up for limited access, correct?
No. Do you have Cups installed (it is several different rpms)? Kups is the program I was refering to, because on my network (Windows shared Canon Multipass c-5500), Yast2 could not set it up. Kups did it quite impressively, IMHO.
OK, let's just leave this issue with printing until I am able to see the smb shares with the smb client. Cheers, Brian
Hi, I'm reluctant to jump into this for obvious reasons (that I'm still in the baffled newbie class myself re: Linux) but maybe here are a few of things that could help you because I've had some experience with Microsoft and Novell networks: 1. workgroup name is very important in MS networking. very important that each machine be given *the same* workgroup name. Example: my home LAN is named HOME. So on the Toshiba laptop running Win98, I have workgroup HOME. On the Athlon machine running xp, I have workgroup HOME. On the Linux machines, I have workgroup HOME. I'm behind a Linksys router and each machine is assigned a number in the 192.168.1.x range where x is 1 to 253. 2. The machine name is different for each machine on the MS network (same goes for the Linux boxes as well). For example the Toshiba laptop is named TOSH. The SuSE linux box is named Athena, the xp machine is Venus. You can use uname -a to show you the box name in Linux. On the MS machines, net name should show the machine name 3. If you have your LAN set up as above, then you should be able to see the other MS machine(s) in the Network Neighborhood (regardless of whether smb stuff is working or not on the Linux box.) If not, try pinging from one MS machine to another in an MSDOS box (command window) and just use the numeric IP addresses. Example: ping 192.168.1.5 where .5 would represent the address assigned to one of the MS machines. No answer back means could mean networking not configured correctly, cable problems (physical wire) or hub/switch/router problems. 4. Verify that you have all machines on the LAN using the same network numbers. By that I mean they should all start with 192.168.1.x for example. There can't be one that's 192.168.2.4 and another that's 192.168.1.5. They'll be seen as being on different networks (and that's what routing's all about) and won't see each other the way you want them to. 5. For test purposes, you might abandon DHCP till things are sorted out and just assign each machine an IP in the 192.168.1.x range if that's feasible. It could make pinging and identification easier while testing. Tom
On Saturday 23 March 2002 22:01, you wrote:
If you want to see a Windows share from your Linux machine (see above subject :-) ), you can type on a command line (i.e. xterm) smbclient -L (computer name) -You fill in the name.
I have had no luck with this. I suspect, for the same reason that LinNeighborhood hasn't worked.
If you want to print, you will use lprold, lprng, or cups. I would recommend CUPS to print to your Windows served printer, and your printing program will use samba_print to actually print through the network to your Windows printer.
OK, I see now that printing and smb shares are two very different kettle of fish in Linux. Let's stick to trying to get the smb shares to appear for now, if you are up to it ;-) If we can get it to work without LinNeighborhood, then I will accept this, but it has been about 15 yrs. since I used DOS. I feel totally blind in the command line after having used Macintosh for so long 8-) That is why I have been trying to stick to Art's instructions.
Again, miscommunication. As you noted above, it is control center in KDE. I thought you were talking about the Windows machine, which does have control panel>network.
Not my error, I was quoting from the original e-mail instructions.
The default user name is exactly that. If you set up your Windows (in Windows) to share based on password, then this setting would give it that username and password. If you set up your Windows HD for full access (meaning no password is needed), this is not even needed. BTW, user name is user name, not computer name. This is to authenticate your Linux machine (using Samba) to your password protected Windows shares. I hope that is now clear. ;-)
I believe so. However, if you are using a Win machine and browse your "network neighborhood", you are doing this using the computer name to identify the other computers. As the DHCP/DNS issue has had me so confused, I would just like to verify that my SuSE computer name is what I think it is.
If you are not sharing resources with Windows via Samba (which you would put it in smb.conf), then putting it in Control center for Windows shares will basically allow you to skip the workgroup level (since this would be done by the setting for workgroup) in (I believe) Konquerer (the KDE default file browser).
And "user name" only needs to be filled out in the KDE control center for Win shares if the Win HD is set up for limited access, correct?
No. Do you have Cups installed (it is several different rpms)? Kups is the program I was refering to, because on my network (Windows shared Canon Multipass c-5500), Yast2 could not set it up. Kups did it quite impressively, IMHO.
OK, let's just leave this issue with printing until I am able to see the smb shares with the smb client.
Cheers,
Brian
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Monday 25 March 2002 15:17, you wrote:
1. workgroup name is very important in MS networking. very important that each machine be given *the same* workgroup name. Example: my home LAN is named HOME. So on the Toshiba laptop running Win98, I have workgroup HOME. On the Athlon machine running xp, I have workgroup HOME. On the Linux machines, I have workgroup HOME. I'm behind a Linksys router and each machine is assigned a number in the 192.168.1.x range where x is 1 to 253.
I am also using a LinkSys router. You say that your Linux machines are also assigned workgroup "home". Where and how did you do this?
2. The machine name is different for each machine on the MS network (same goes for the Linux boxes as well). For example the Toshiba laptop is named TOSH. The SuSE linux box is named Athena, the xp machine is Venus. You can use uname -a to show you the box name in Linux. On the MS machines, net name should show the machine name
OK, I tried uname -a and got "Linux thor" thor should be the name of the computer. I don't know what the Linux is doing in there. I already know the Win boxes names, but get nothing with smbclient -L <computer name>.
3. If you have your LAN set up as above, then you should be able to see the other MS machine(s) in the Network Neighborhood (regardless of whether smb stuff is working or not on the Linux box.) If not, try pinging from one MS machine to another in an MSDOS box (command window) and just use the numeric IP addresses. Example: ping 192.168.1.5 where .5 would represent the address assigned to one of the MS machines. No answer back means could mean networking not configured correctly, cable problems (physical wire) or hub/switch/router problems.
I can see the Win machines when I boot into Win 2k and use network neighborhood. My only problem is when I boot into SuSE, smbclient can't seem to locate anything with "smbclient -L" <computer name>.
4. Verify that you have all machines on the LAN using the same network numbers. By that I mean they should all start with 192.168.1.x for example. There can't be one that's 192.168.2.4 and another that's 192.168.1.5. They'll be seen as being on different networks (and that's what routing's all about) and won't see each other the way you want them to.
I assume that they all are as I can see them all in Win 2000, but just to be on the safe side, how do I check the IP addresses when they are assigned dynamically?
5. For test purposes, you might abandon DHCP till things are sorted out and just assign each machine an IP in the 192.168.1.x range if that's feasible. It could make pinging and identification easier while testing.
This would be a last resort Tom, as accessing the smb shares is mainly for my benefit. My other family members will not appreciate me mucking around with the machines and they suddenly have no Internet access (as an example). Cheers, Brian
workgroup HOME. On the Linux machines, I have workgroup HOME. I'm behind a Linksys router and each machine is assigned a number in the 192.168.1.x range where x is 1 to 253.
I am also using a LinkSys router. You say that your Linux machines are also assigned workgroup "home". Where and how did you do this?
Like many things in Linux there are lots of ways to do any one thing. For example, you asked about how to specify group name/workgroup. You can specify workgroup on the command line with the -W option. Example: smbclient -L VENUSXP -W HOME There's also a place to set it in your smb.conf file in /etc which is what is normally done. You'll have an smb.conf file because I believe SuSE makes one for you at install. After install, mine had the default workgroup set to TUX-NET. So look for yours and change it if necessary. smb.conf is a big subject but fortunately there's lots of help on the web available to you for that subject. I suggest you start with a look at info smbclient man smbclient I know that being referred to man pages sounds like a brush off, but you *really* will find a lot of info you *need* to know if you're going to use SambaSuite. My peeve with man pages is lack of examples. How many times have I groaned and thought, Oh just 1 example PLEASE. But usually none. It depends on who wrote the 'man' page I suppose. "Info" page, if there is one, is more likely to have an example, I've discovered. I suspect all these authors are following some style sheet and it doesn't require them to give examples.
networks (and that's what routing's all about) and won't see each other the way you want them to.
I assume that they all are as I can see them all in Win 2000, but just to be on the safe side, how do I check the IP addresses when they are assigned dynamically?
If you can "see" them in Win2000 then it's probably not a problem with the MS machines. Did you mention this before? So forget about the dynamically assigned IP confusion (DHCP). Select some folder or drive and mark it shared and try to connect with it from Linux. Example: smbclient //venusxp/gnostic smb: \> dir Substitute your own MS machine's name instead of venusxp and substitute your MS machine's shared folder instead of gnostic. If it asks for a password, give it, but better that you not set a password on the MS share just for this test. So you'd hit <enter> at the password prompt. Then it should come back with that peculiar smb prompt in line 2 of my example. Since you asked-- On the Windows machine(s), the command ipconfig will give you that machine's IP address, network mask, and default gateway. (use a command prompt box) On Linux the hosts file in /etc will contain your IP address, machine name, and other machines' info on your network. Example: cat /etc/hosts Tom
participants (4)
-
Art Fore -
Brian Durant -
Joe & Sesil Morris (NTM) -
Tom Nicholson