I need access to shares on a Unix server on a separate sub-net from my PC.


I have a Unix file server on IP 192.168.19.102 and (several) Windows XP computers with static IP addresses ranging from subnets 192.168.16.###.  through 192.168.18.###.   None of these PC's can access the folder shares on the Unix server.  However, all the computers with on our sub-net 192.168.19.###, can access the Unix shares without any problem.   Also, I can ping the Unix server from any of our PC's from any sub-net.

Our gateway router is on 192.168.16.254 and our DNS server is 192.168.19.250.

I have added routes on the Unix server to all our sub-net addresses using the command...

      route add 192.168.17.0  192.168.16.254
      route add 192.168.18.0  192.168.16.254
and so on...

What configuration(s) am I missing that will allow computers on subnets other than the one the Unix server is on?
NetTokenAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

omarfaridCommented:
it could be a firewall that is denying your access
NetTokenAuthor Commented:

A good call, but not the case in my situation.   The connection is going from my PC, 192.168.16.56 through a DELL Powerconnect managed switch 192.168.19.138 then to the Unix server at 192.168.19.102.  There are no firewalls setup on this (internal) LAN connection.
gheistCommented:
Set up WINS server. Samba will do.
Otherwise NetBIOS naming does not cross broadcast domains.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
NetTokenAuthor Commented:
Thanks gheist, it turned out that Samba was running on this server but was configured to work with a specific workgroup name.  The machines in question had been taken off that workgroup and joined to a windows domain.  I just have to reconfigure Samba to work with these domain machines.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.