• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DNS troubles behind router

D

darkmagex

Member
I've been testing a router setup in my office and found a problem I can't seem to fix.

Using a DLink DI-604 (3.38 firmware), everything works except that I cannot access some network shares by name.

\\server does not work, but \\server.domain.edu works fine as does \\ipaddress

I've fiddled with every dns setting in XP i can find and nothing seems to get it to work. Ipconfig shows the correct DNS search suffixes but no dice.

Update: I can nslookup the server and it gets the correct IP from that, and if I add an LMHOSTS entry I can \\server from the command line and it works. Unfortunately LMHOSTS isn't a good solution in this case.

I hardcoded the DNS server ip, as well as search suffixes but it didn't seem to make a difference.
 
I believe you're using the incorrect UNC syntax.

\\server\share is correct

Also, \\share.domain.edu is an incorrect FQDN syntax. I'm going to assume the reason \\share.domain.edu works for you is because you have a computer named the same thing as that share on your network.

The correct FQDN on a network would be \\server.domain.edu OR if you wanted to go directly to the share, \\server.domain.edu\share
 
Originally posted by: darkmagex
I seem to have written my example unclearly. I'm using correct sytanx (\\server\share), and it works when I unplug the router. It's not a case of the share not being correct, but someone the computer not translating it correctly.
Click to expand...

I spent two hours last night troubleshooting a DNS problem on my local network after replacing my wired connection with a wireless one. I have a Linksys router. It was attempting to parse DNS requests from the local clients. What happened was the DNS suffix automatically appended to the new NIC and its properties wouldn't allow it to see the local server or other computers by name. I fixed the problem by hardcoding the DNS number of my local DNS server and changing the DNS properties within the NIC properties so that it automatically appended the correct DNS suffix with every network request.

Give that a shot and see if it helps. I tried everything before the solution hit me in the face, unfortunately. Hope it helps.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top