Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
My friends and I have a cable modem which we run into a 4port linksys router and to our 3 pcs. Mine is a linux box and the others are win. I set up samba and everything works perfectly on their end-they can share my files and eachothers. On my end when I run smbclient -L localhost I get their info. But when I try to connect with smbclient //winname/dir I get an error that the connection failed.
Is there something special I have to do because we are going through this router?
Here is the error message:
root@dingo:/etc# smbclient //terry/music
added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0
added interface ip=127.0.0.1 bcast=127.0.0.255 nmask=255.255.255.0
timeout connecting to 192.168.0.3:139
Connection to terry failed
(I set up terry to be 192.168.0.3 in
I'm doing the same thing, with the 4 port LinkSys connecting a Win98 machine and Linux box.
Since the timeout message is giving you an IP, it is getting the IP from Hosts properly. I could not connect until I set up static IPs for the computers and turned off DHCP service on the router.
It looks to me like the problem is with the Winbox setup - recognize that the winboxes could see each other using NetBEUI and don't necessarily need TCP except to see beyond the router. I'd double check the TCP settings on the winboxes - don't use DHCP.