Linux - NetworkingThis 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After reading all these posts I'm not sure you are going to solve your problem. You need to change your Ip off of 192.168.2.255/24. its broadcast address for that /24 and you CANNOT asign it to an interface. You will cause that host to drop off the network. IT CAN"T HAVE THE BROADCAST ADDRESS!!!.
First fix the ip address then see if it will work. if its a firewall you may have to access from another interface as you will not get an answer back by trying to contact the broadcast address.
post the output of ifconfig at the time you are trying to ping it..
then run ipconfig on windows and verify that the win network is running
also please read some manpages, as you will feel less lost when you know what's in them..
once you have verified the windows ip, try to ping the windows box from linux..
your ping test, you should be doing is two steps
1.) ping 192.168.x.x
ping whatever the boxes ip is set to it makes sure you can see yourself, verifying that your network and ip are correctly setup.
2) ping the ip of the win/lin box (the other box)
you should do both from the win machine, and the lin machine, so four steps, this tells us what is configured right..
when we need the output of a command, we need to see the output. without it we don't know what's going on with your machine, if it errors, we need to know what the error says if it gives data we need to see that data..
so you can succefully ping the win box from lin
and the lin box from win...
that means that we move on to samba..
since in the begining you were trying to acces the lin data from win thru //ip
did you do the following
read manpage on sama, samba.conf, and on samba's user and password feature?
did you sset up shares within samba?
did you set your network in samba so you can use win's workgroup browser to try and see it?
did you use the win search for computers to search for your computers ip address?
I didn't read the manpage...I followed a tutorial...which obviously failed
I don't know what shares are...and I don't think I set my network in sambaso I can use win's workgroup broweser to try and see it...I think I got samba's user and password feature thoug...
find a manual page viewer and view the samba, samba.conf man pages, or check for other threads on setting up samba, as there is a lot of them...
you need to
be sure you have a username and password in samba's password database
2. be sure that account exists on the windows box, so you can get into the served files
3. have samba.conf configured with your windows workgroup name
4. have samba.conf configured for your shared folders.
5. have samba running.
if i;'m wrong or missed anything, someone please correct me.....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.