FN-GM Posted December 17, 2007 Posted December 17, 2007 Hi Recently when we configure outlook manually to connect to our Exchange server we type in the details to our server correctly and we have tried using the IP address but when we click check name it resolves another Exchange server in another school another domain in the same forest. Any thoughts please? Thanks Z
Ric_ Posted December 17, 2007 Posted December 17, 2007 Is there a GPO coming into play or is the setup maybe from a custom install disk? You could run GPOResult from the GPMC to see if any Office templates are in effect.
FN-GM Posted December 17, 2007 Author Posted December 17, 2007 We are using the Administrator account and there are no policies what so ever. It was fine last week we haven't changed anything but today it was playing up. I will check tomorrow though, that’s for your comments. Z
FN-GM Posted December 18, 2007 Author Posted December 18, 2007 No there isn't any policies effecting it Thank you Z
ricki Posted December 18, 2007 Posted December 18, 2007 HI It might be your dns. Try pinging the name of the exchange server and see what ip it has for it. Then check that the ip is the same. Also check the mx records you have for the exchange server. You might have a record missing or a preference value set wrong. Just a thought. Richard
FN-GM Posted December 18, 2007 Author Posted December 18, 2007 The IP is correct and the MX records are. I have just found out it doesn't do it on all computers but just some of them. Z
HodgeHi Posted December 18, 2007 Posted December 18, 2007 Maybe dns is manually configured wrongly on the clients.
localzuk Posted December 18, 2007 Posted December 18, 2007 Also, check the hosts file. Our network used to have things set via hosts, and some of the older machines still had things set in there.
FN-GM Posted December 18, 2007 Author Posted December 18, 2007 Maybe dns is manually configured wrongly on the clients. Its done via DHCP and some clients are fine on DHCP. Also, check the hosts file. Our network used to have things set via hosts, and some of the older machines still had things set in there. What do mean please?
HodgeHi Posted December 18, 2007 Posted December 18, 2007 I would check them anyway. May have a rogue dhcp service giving out different information. I found this happened with a censornet proxy that was meant to have the dhcp service disabled but still started the service during boot.
ricki Posted December 19, 2007 Posted December 19, 2007 Hi I have had it when a child was bringing a laptop into school and was plugging it into the network and they had set up dhcp server on it to bugger the network, I have also had it where a teacher had shared there internet connection and every time they plugged into the network it gave out addresses Lastly if you have a nt 4 server chack that first. Good luck with the search. Richard
FN-GM Posted December 19, 2007 Author Posted December 19, 2007 All our servers are 2003 the IP settings are coreect. Z
localzuk Posted December 19, 2007 Posted December 19, 2007 Also, check the hosts file. Our network used to have things set via hosts, and some of the older machines still had things set in there. What do mean please? Take a look in the file c:\windows\system32\drivers\etc\hosts It should be pretty empty, as in a dozen commented lines and then 127.0.0.1 localhost ::1 localhost Is there anything else in there?
FN-GM Posted December 19, 2007 Author Posted December 19, 2007 This is what i get # Copyright © 1993-1999 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost
E_S_P Posted December 20, 2007 Posted December 20, 2007 If you ping using the fqdn does it resolve to the correct IP(s) from these PC's for the correct exchange server? I dont know your topography but have you tried tracert if you are crossing routers/routing tables to make sure if you are ending up in the right place from these PC's. Do they have any gateway addresses set - possibly from another network segment they may have been on ? Are you splitting the DHCP scope over multiple servers - if so any routers etc set in there. Tried a flushdns/release/renew ? Do you have any DNS errors on your servers, and are they replicating changes ok - are the problem machines all connecting to the same server? Good Luck & Merry Xmas !
thegrassisgreener Posted December 20, 2007 Posted December 20, 2007 Why don't you speak to Riz at the CLC, he will tell you the problem streight away
FN-GM Posted December 20, 2007 Author Posted December 20, 2007 @ E_S_P I have checked all that and its fine @ thegrassisgreener I was surprised that Riz doesn't know I had him on the case right away he does think it could be a problem with AD. So how do you know Riz then? Z
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now