[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 that is?

well, port 137, 138, 139 are labeled. 445 is for directory services. You should not need that one unless you do.

printer is in case your sharing your printer.

Open the ports you decide that you need using your firewall tool or iptables script.

However it makes no sense to have an internal interface firewalled and then open all the vunerable ports on it.

wow you completely lost me....you gotta keep some of this in stupid people Linux terms

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.

the Ip address is 198.162.2.100

something like that..

hmmm//

move to simplistic...

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

ooooook

both of them ping to each other fine

Linux ----> Windows and Windows ---> Linux

I don't know what results you want me to post....

ok...

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

Can you see the samba server on the network?

no

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

If you cannot see it at all I would say firewall, or nmbd is not running, or it's WORKGROUP is not the same.


on the server try this

smbclient -L localhost

sorry guys I was outta town...back to fixing the problem....



when I do that command it said session failed