Cannot browse folders in windows 2003 through Netbios names?

I have installed a windows 2003 Server with two NIC Cards.  One NIC is connected to a DSL Router with Static IP address (WAN), the other NIC is running DHCP and has the firewall turned off.  The server is routing IP addresses and is configured for NAT.  Everything seems to works just fine, except I seem to have a Netbios issue or something.   When I share folders on the server, I am unable to browse through the shares from the client computers using start>RUN>\\theservername\sharedfolder.  At first I thought it was NTFS Permission problem, but I am able to browse through Active directory on the client computer using My Network Places, and have access to the shared folders.  Now it gets a little more interesting, if I am at the client computer and type in the run command \\10.0.0.254\sharedfolder, I am now able browse through the shared folders.  Therefore, I must have something configured wrong with the NAT routing, or I need to use WINS to resolve Netbios names.  Anythoughts?    
robertsklAsked:
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.

TheCleanerCommented:
1.  Are the clients internal or external?
2.  If external, does it work ok internally?
3.  Do you have DNS configured properly?

Whether the clients are internal or external will make a big difference where the answer lies.
Walter PadrónCommented:

start>RUN> nslookup theservername   resolves to 10.0.0.254?
start>RUN> \\theservername.your.domain\sharedfolder let's you browse shared folders?


robertsklAuthor Commented:
The client computers are internal.  DNS is setup with a forwarder and client computers are able to reach the internet.  

start>RUN> nslookup theservername   resolves to 10.0.0.254?  NO CANNOT FIND SERVER
start>RUN> \\theservername.your.domain\sharedfolder let's you browse shared folders?  NO CANNOT FIND SERVER

It looks like I have a DNS issue then?  Where did I go wrong?
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

TheCleanerCommented:
if you do a ping -a 10.0.0.254 does it resolve a name at all?

Are the workstations pointing to internal DNS?

Go to the DNS servers and check the forward lookup zone(s) and make sure the domain name is one of the forward zones and that there are A records in there for the servers, etc.

If not, it's a DNS issue.

Also, run a DNSDIAG from a command prompt to test.

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
Walter PadrónCommented:
Also start>RUN> ipconfig /all
and check if your domain is listed under DNS Suffix Search List. . . . . . :
TheCleanerCommented:
Thanks for the points!
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
Windows Server 2003

From novice to tech pro — start learning today.