Two Networks IP to server shares work but UNC names don't work

smfmedia
smfmedia used Ask the Experts™
on
I have two networks 192.168.0.x and 192.168.1.x.  I have a Sonicwall Pro 3060 that makes the connection between my lan(192.168.0.x) and the other lan (192.168.1.x)  I have setup routing and I can ping over to the 192.168.1.x network no problem.  I can even get to server shares using \\192.168.1.213 and things work fine.  I setup both DNS servers with secondary zones and all data has replicated between the two servers.  I have done an NSlookup and the names resolve to IP addresses but I can't connect to anything using the UNC name (\\citynas1)

The sonicwall is setup to allow all traffic between the two Lan's.

Why can't I use the UNC Name to connect when they are listed in the DNS server and the NSlookup has no problem resolving them.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
I am going to assume that pinging by DNS name also doesnt work. Although DNS seems to be working at the server level are both DNS servers set as primary and secondary on your client machines? Also, have you checked to see if this is only a one way issue or can you not ping accross using dns name from either subnet?
bluntTonyHead of ICT
Top Expert 2009

Commented:
Have you tried connecting to the share using the FQDN? e.g. \\server.domain.local\share
Are your machines on a WIndows domain?

Author

Commented:
Ping by DNS name does not work.

The same problem exists on both sides of the network.
I have my two DNS servers setup as as primary and secondary on the clients and on the other side there are two more DNS servers that are setup a primary/secondary on those clients.

FQDN does not work either

All machines run on Windows 2003 Domains.
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
I just checked and I can Ping a name using a FQDN but I can't use it in a UNC
bluntTonyHead of ICT
Top Expert 2009

Commented:
So you can access a share via IP address, and you can resolve the FQDN of the same server to that IP address correctly, but you can't access a share using the FQDN? And you can ping by FQDN as well? Providing that the FQDN is resolving to the same IP address that is successful, it doesn't seem like a DNS problem.
What is the error message you get when trying to access with the FQDN?
Are they two seperate domains? Have you tried disabling any firewall on the SonicWall to eliminate this as the cause?

Author

Commented:
There are no Firewall ACLs on the sonicwall for LAN Zones

I just get the windows can't access blah blah blah standard message.

They are two seperate domains.  The trusts have not been setup yet.

When it comes down to it I am looking to not use the FQDN and only use server name to access the shares.  99% of users can not handle using the FQDN.

The other thing is when I browse "entire network" the domain is not present.
Head of ICT
Top Expert 2009
Commented:
For browsing to work you will need to have WINS setup on both domains and have the WINS servers replicate between each other. You need NetBIOS name resolution and registration for network browsing, not just DNS. Network browsing is one of those reasons why NetBIOS is still hanging in there.
WINS replication : http://technet.microsoft.com/en-us/library/cc786754(WS.10).aspx
Just using the NetBIOS name (i.e. 'server' as opposed to 'server.domain.local') to acces a machine in another domain requires either that you add the other domain DNS suffix into the clients' DNS suffix search list, or that you utilise WINS as I have mentioned.
If it's two domains, I would also not replicate secondary zones to the opposite DNS server, but rather set up conditional forwarder on each DNS server for the other domain. So on a DNS server in Domain1 you set up a forwarder for Domain2 and point it to the DNS server in Domain2. (Properties of server in DNS console > Forwarder tab). The remove the secondary zones on each server. Cross domain queries are then just referred to the other DNS server.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial