Software

Ask something
Discussion Locked

cant connect to Exchange server

0 helpful
7 replies

by keeny

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am expereincing a weird problem with a particular PC connecting to our Exchange server.

errror:
'Name could not be resolved'
'Network problems are preventing connection'

PC and networking is configured correctly.

tried with different profiles no difference, tried a removal of office and reinst no diff,

tried a rem & complete removal utility & reg clean &reinstall no diff. pc can see exchange

server in network neighbourhood.

any ideas peeps?

7 replies

by steved

So the server shows up in Network Neighborhood, but can the PC ping it by name? Can it ping it by IP address? If no to former and yes to latter, try an entry in the winnt\system32\drivers\etc\hosts file.

I'm not optimistic this will help, but I have sometimes seen odd variations between PCs on same network apparently configured the same.

Steve Diamond

by mikel~t

If you don't have an internal DNS server, then you will need to use the hosts file, but if you do have an internal DNS server, then you need to make sure the troubled PC is setup to use this DNS server as its default, and then try and attempt to theExchange server.

If you can't ping the Exchange server by name, then you will need to setup the hosts file so the PC can resolve the DNS name localy.

hope this helps.

Mike

by netguymn

You say that network services are configured correctly but I think you should check again. This sounds like a classic network config issue.

Here are a few things to try.
1) From a DOS prompt attempt to ping the mail server by name. I expect it will fail.

2) Try to ping the mail server by IP address. If it succeeds, there are likely name resolution issues on the network or perhaps just with this PC.

3) Try configuring the mail client (resolving the user name) using the mail server'sIP address, rather rather the server name. If it works, again, there is likely a name resolution problem. If not, ...???

4) If available, try pinging the workstation from the mail server to test for network connectivity to the client.

5) As atemporary test, create a hosts or lmhosts file containing the name and IP address of your mail server on the client.

Lastly, make sure that you have a valid WINS address in your network configuration. Ping it to make sure it responds.

Make sure you have a valid DNS entry on your network config. Ping it to make sure it replies.

If you are using DHCP, remember that any entry in the net config settings will override the DHCP settings. If an entry is in there by mistake it can cause problems.

Use winipcfg or ipconfig/all as appropriate for your O/S to see what the system is really using rather than relying on the network control panel.

by keeny

Thanks everyone for your advice.
I still cant get it working though!

I can ping the server by name and IP address. (havnt tried pinging the worksation from the server side though)
I plugged my laptop into the same network port and could connect fine.

Not using DHCP, and the WINS\DNS is configured correctly for our network. Entry in LMHOSTS did nothing either.

This leads me to think it is a software problem, unistalling and reinstalling Outlook didnt help, so the only thing i can do now is rebuild the workstation from scratch. (and keep fingers crossed!)

A cop out i know, but the poor lady has had no e-mail for weeks now.

I've never seen anything like this before, could be paranormal activity in the office or something!
Will leave question open for another day or so.

cheers

This discussion is closed to new replies.