Name could not be resolved Hell!

Although I have seen a few questions of this sort out here, none of the answers have helped.  I have a client who dials into an MS Exchange Server which happens to be their all in one server.  They use Outlook as their e-mail application and when I try to "Check Name" of both the user and the Exchange Server, I get the error that "The name could not be resolved.  Network problems are preventing connection to the Microsoft Exchange Server computer.  Contact your system administrator if this condition persists.  Well, it persists and I am the administrator and I have no clue.  

I have uninstalled everything and reinstalled from scratch and nothing.  I can get into the network via the dialup and I can ping the Exchange Server via host name as well as IP address but nothing via Outlook's Check Name function.  I can't even check name with the IP address of the sever.  

Can't think of much else to do, am I missing something small and stupid?  
Who is Participating?
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.

It's a long shot but have you checked the RPC Binding order on the workstations involved?

Take a look at this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider\RPC_Binding_Order

Move the token that represents the protocol that you're using to the front
of the pile. Occasionally I've found that the protocol that gets used isn't
always the one you think, so if it doesn't work right the first time try
reordering the protocols again.
he pingthis,

try putting the ip address of the exchange server in the box. and check you lmhosts file.
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

If the other suggestions haven't helped you then... since I don't know what you've tried I'll just list what usually resolves this for me...

1. Hosts file on the client; make sure there is an entry for your Ex. server.

2. check your dial-up networking properties within Outlook; make sure the proper username, password and domain is specified.

3. Network properties in Control Panel; on the Identification tab make sure the "workgroup" is set to your network's domain name and the "Computer Name" is set to the NT user name

4. On some uncooperative systems I've had luck by installing the Microsoft client for MS Networks, set to log onto your network's domain; (you may need to delete the PWL on the client machine first) have them enter their network username and password when Windows starts up.

If none of these help, just as a test, try to log-in as a user you know is working properly.

Good luck,
pingthisAuthor Commented:
Thanks for all the suggestions.  I am heading out to the client today and will try them out.  But here are some answers to the suggestions which I have left out of the introduction to this issue.

-I have already copied an lmhosts file from a working RAS connecting PC from the same location to the nonworking PC.
-I have also tried to resolve the Exchange Server via IP address in the Check Names screen and still no go.  That is when I tried to ping via the Exchange Server Name and IP address and can somehow do so from the command prompt but not the Outlook Check Name screen.
-Since this is a 95 machine there is no RPC service to start, at least that I can see or know of, but the RPC service is up and going on the Exchange Server.
pingthisAuthor Commented:
Also, have tried to use login of users who work already and still no go.  I can log onto the network with no problem but just can't resolve to Exchange.
I had this problem today.  It turned out to be a faulty RPC setup.  Microsoft advises that you find the following key in the registry of a computer that is working correctly:


1. Select this key in the left hand panel of Regedit.
2. Make the menu selection Registry/Export Registry File.
3. A dialog appears. Select the radio button
Export Range/Selected Branch
4. Enter a filename on a floppy disk, then click the Save button.
5. Stick the floppy in the misbehaving computer and run the reg file you just created.
6. Reboot and pray.

this branch of the registry

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
we had the same problem on a few machines and it turned out to be an older version of SECUR32.DLL that was responsible. Replacing this with version 4.10.1057, which is part of the DCOM package from Microsoft resolved it for us.
Note that re-installing TCP/IP or Microsoft Client and choosing to overwrite a newer version of that file with an older one are 2 ways this problem can be introduced.
Try it, hopefully it will work for you
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

From novice to tech pro — start learning today.