Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
12-16-2005, 03:55 AM
|
#1
|
|
LQ Newbie
Registered: Dec 2005
Posts: 1
Rep:
|
Unable to connect SUSE 10 machine to windows network
I have a new Linux (SUSE 10.0) machine that I am trying to connect peer to peer to two XP machines, via ethernet. The XP machines can see each other but the Linux is isolated.
They are 192.168.0.1, 2, 3 (linux). YAST indicates everything is working but no go. EVERY bit of documentation I can find is oriented towards setting up the Linux as a server, which I do NOT want to do. Any ideas are welcome. Thanks.
|
|
|
|
12-16-2005, 12:47 PM
|
#2
|
|
Senior Member
Registered: Jan 2002
Location: St Louis, MO
Distribution: Ubuntu
Posts: 1,284
Rep:
|
What are you connecting your machines through - a hub/switch? Also, are you sure that the network settings are configured correctly, including the card itself? Can you physically ping the other machines on the network? If so, then what resources are you trying to access on the Windowsm machines - printers/network shares? If so, you will need to install the Samba client packages on the SuSE machine so that it understands the communication methods and filesystems being used on the Windows computers.
|
|
|
|
12-17-2005, 12:33 AM
|
#3
|
|
LQ Newbie
Registered: Nov 2005
Location: Basel Suisse
Posts: 18
Rep:
|
Samba v3 does not like peer to peer. You need a nameserver, even with only two computers. But it can be solved without, with the help of Lisa. But she seems forgotten. there are some problems installing her (If you have a spare emailadress that you can throw away, I could send the instructions for Suse on.)
But first try to open Konqueror (this only works with konqueror)
In the URL-adress write smb://192.168.0.1 (and click enter),and you should get the login for that computer.
If this works you can rightclick in the workspace, klick make new -- link to adress URL for both your XP-machines, Drag and drop the icons to a suitable folder, and you have simple networkbrowser (you can give it the beutiful samba-icon), and Lisa is not needed.
For a simple server on the linuxmachine:
In Yast: make a new user, call him e.g. share_a
As root
( copy /etc/samba/smb.conf to /etc/samba/smb.conf-original )
open /etc/samba/smb.conf with e.g. kwrite, and make the following configuration
[global]
workgroup = (whatever you use)
netbiosname = (whatever you use)
security = share
# (with security=user, it's difficult to make it simple)
auth methods = guest
#smb ports = 139 may be needed, but its better without
#wins support = yes may be needed for networkprinting
[share_a]
comment = the user share_a
path = /home/share_a
#or any path, e.g. "path = /home"
read only = no
guest OK = yes
hosts allow = 192.168.0.1/255.255.255.252
#only möderate security, but could do if you have control over LAN-cables.
BEWARE: yast or swat might make unsolicited changes e.g "security = user".
you need "security=user" if you want all sambas possibilities
but you also need plenty of time to find out howto
P.S. Standard-Pinging in Linux is ,in the terminal-window, e.g.
ping -c4 192.168.0.1 # (without -c4 it will ping forever.)
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:07 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|