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.
if windows cannot ping either address, it means you need to redo the network, verify linux ip, verify networking is up and running, try to ping the winbox from linux, check for firewall settings on either side, check the cables.. and if it doesn't work, post the results of each thing you've tried..
192.168.2.255 in this scenario is more than likely not a valid host IP. If your netmask is 255.255.255.0 then either you are pinging the wrong IP or the IP you set on the Linux box is invalid...
192.168.2.255 in this scenario is more than likely not a valid host IP
the .255 means broadcast, it should ping every address from x.x.x.0 to x.x.x.254
Quote:
marklar
when I type in that command it says unknown host.
when you type the ifconfig command i'm assuming?..
try it without the inet part, and see what happens, if it doesn't error, send the output of
ifconfig
There probably should not be a firewall on your internal interface unless you don't trust someone on the inside. However if it's the interface on the internet you should not be opening those ports to it either.
[david@zeus david]$ cat /etc/services |grep netbios
netbios-ns 137/tcp # NETBIOS Name Service
netbios-ns 137/udp
netbios-dgm 138/tcp # NETBIOS Datagram Service
netbios-dgm 138/udp
netbios-ssn 139/tcp # NETBIOS session service
netbios-ssn 139/udp
[david@zeus david]$ cat /etc/services |grep microsoft
microsoft-ds 445/tcp
microsoft-ds 445/udp
[david@zeus david]$ cat /etc/services |grep printer
printer 515/tcp spooler # line printer spooler
printer 515/udp spooler # line printer spooler
Last edited by DavidPhillips; 12-22-2003 at 10:14 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.