LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Samba question (https://www.linuxquestions.org/questions/linux-networking-3/samba-question-127720/)

Marklar 12-20-2003 11:16 PM

Samba question
 
I do \\192.168.2.255 and I get the error

"Windows cannot find 192.168.2.255. Make sure you typed the name correctly, and then try again.

I try \\192.168.2.100 but Windows cannot find anything....

can anyone help me?

miaviator278 12-21-2003 12:36 AM

that's not really a linux question.

ping 192.168.2.255

and see if the winbox can see it.

also try 192.168.2.100

check windows help command reference for ping functionality as far as pinging broadcast addresses.

Marklar 12-21-2003 12:57 AM

hey it's linux related...that's linux problem enough for me

Marklar 12-21-2003 12:58 AM

The pings time out

Marklar 12-21-2003 10:36 AM

uh anyone else able to help?

miaviator278 12-21-2003 04:04 PM

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..

jcookeman 12-21-2003 09:04 PM

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...

Marklar 12-21-2003 09:10 PM

alright then..you're most likely right..so how do I fix it?

jcookeman 12-21-2003 10:06 PM

ifconfig eth0 inet 192.168.2.10

and then try to ping it from the windows box...just make sure that 192.168.1.10 is not already taken

DavidPhillips 12-21-2003 10:12 PM

Did you setup a firewall on that interface?

Maybe it's blocking all traffic.

Marklar 12-22-2003 08:41 AM

yeah I think it might be a firewall..how do I fix that too?

Marklar 12-22-2003 12:31 PM

Quote:

Originally posted by jcookeman
ifconfig eth0 inet 192.168.2.10

and then try to ping it from the windows box...just make sure that 192.168.1.10 is not already taken

when I type in that command it says unknown host.

miaviator278 12-22-2003 06:33 PM

man ifconfig

ifconfig eth0 (ip)
Quote:


jcookeman

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

Marklar 12-22-2003 07:37 PM

when it doesn't error I get a list of ips

DavidPhillips 12-22-2003 10:12 PM

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




All times are GMT -5. The time now is 09:13 PM.