This is more a windows problem and specific more a WINS/NETBios/name resolution problem. Do you got a dns server? Some kind of domain?
What I understand from your story the following happens: Client queries on netbios level; who is \\computername to the masterbrowser list, can't find on local subnet, hence not found. Broadcasts don't travel beyond own subnet unless otherwise configured. What you should do is either connect via \\ip\share or get yourself some kind of AD DNS or a WINS Server and tell your clients to use WINS/DNS for name resolution. Then it should work. Hope this helps Patrick On Mon, November 13, 2006 22:38, Marwan Sultan wrote: > > Hello Gurus, > > 192.168.0.1 is the internet server dialer (winXP) ---> switch --> > 192.168.0.2 FreeBSD 6.1 NAT 192.168.1.1 > clients are 192.168.1.xxx everything works great, Internet goes to > clients from the fbsd server > all IPs can ping each other.. 192.168.1.5 can ping 192.168.0.1 > To here and its great. > > But when any client 192.168.1.x tries to access the shared files on > 192.168.0.1 > it cannot. it says not a correct path, and it cannot see it, although > it > can PING it. > I asume the diffrences in IPs although its on same LAN makes this > class > cannot access the other. > > Can someone kindly shade a light, on what should I do ? > > > Thank you > Marwan Sultan. > > _________________________________________________________________ > FREE pop-up blocking with the new MSN Toolbar - get it now! > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ > > _______________________________________________ > email@example.com mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"