vpc_bits
asked on
Login problems to exchange 2000
Server: WIN2K Server+SP3, Excange2000+SP2, Active Directory Service, latest NAV Virusdefinition with daily scan
Client: Win98/ ME with office 97/2000, latest NAV Virusdefinition with daily scan
Problem: I have one file+internal mail server(exchange 2K). Client PCs can login to the network without any problems. SOME of our Win98/ME clients have problems to login via Outlook97/2000 to exchange2K. After around 10 times entering the password, the small number of Win98/ME client computers are able to login to the exchange2k. As I said only some Win98/ME clients have this problem, most Win98/ME clients are working well. Any idea what the reason for this problem is?
Client: Win98/ ME with office 97/2000, latest NAV Virusdefinition with daily scan
Problem: I have one file+internal mail server(exchange 2K). Client PCs can login to the network without any problems. SOME of our Win98/ME clients have problems to login via Outlook97/2000 to exchange2K. After around 10 times entering the password, the small number of Win98/ME client computers are able to login to the exchange2k. As I said only some Win98/ME clients have this problem, most Win98/ME clients are working well. Any idea what the reason for this problem is?
Have you tried uninstall/eraser97/reinsta
ASKER
That is what we are just trying to uninstall/reinstall. Problem is not only with 97. Repair on the O2K clients, we already tried it, but it was not helpful. Thanks
Using Eraserxx between the uninstall/reinstall will remove files that uninstall misses - http://support.microsoft.com/default.aspx?scid=kb;en-us;239938
Just a possibility.
I had a similar issue to this once, and it turned out to be a DNS issue.
Exchange 2000 requires a properly configured DNS and Active directory. Failer to have these will cause clients to fail to auth properly.
I had a similar issue to this once, and it turned out to be a DNS issue.
Exchange 2000 requires a properly configured DNS and Active directory. Failer to have these will cause clients to fail to auth properly.
ASKER
Thanks,
we will try.
we will try.
ASKER
We tried it, but we still have the same problem.
Thanks
Thanks
ASKER
Hello Tordan,
it seems, that we have the problem which you descriped.
How have you fixed it?
In our case:
Exchange server name: vpchn (IP 197.0.0.3)
Client IP: 197.0.0.66
ping from client: ping vpchn -> 197.0.0.66 instead 197.0.0.3
All Win98 PCs who have this problem has the same result, ping resolution is to client IP address, what is wrong. All other 98 PCs are working well and are able to make a name resolution from vpchn to 197.0.0.3.
We also reinstalled (format c:) the PC, but same problem.
Thanks
it seems, that we have the problem which you descriped.
How have you fixed it?
In our case:
Exchange server name: vpchn (IP 197.0.0.3)
Client IP: 197.0.0.66
ping from client: ping vpchn -> 197.0.0.66 instead 197.0.0.3
All Win98 PCs who have this problem has the same result, ping resolution is to client IP address, what is wrong. All other 98 PCs are working well and are able to make a name resolution from vpchn to 197.0.0.3.
We also reinstalled (format c:) the PC, but same problem.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hello Tordan,
first thank you very much for your detail information. We checked all our installation & configuration again. It is like you already wrote. We have 1 DHCP & DNS Server, ...
We fixed the problem by disabling DNS on all 10 "problem PCs (Win98 & ME)". It is working now, but we still don't understand why.
We will investigate and try to understand what the reason is.
We close the problem request.
Thank you very much
first thank you very much for your detail information. We checked all our installation & configuration again. It is like you already wrote. We have 1 DHCP & DNS Server, ...
We fixed the problem by disabling DNS on all 10 "problem PCs (Win98 & ME)". It is working now, but we still don't understand why.
We will investigate and try to understand what the reason is.
We close the problem request.
Thank you very much
weird,
what exactly do you mean by 'disabling DNS'? that might give me a clue as to where you problem lies.
also if you accept one of my answers i will get my 50 points. /grin
Thanks,
Tordan
what exactly do you mean by 'disabling DNS'? that might give me a clue as to where you problem lies.
also if you accept one of my answers i will get my 50 points. /grin
Thanks,
Tordan
ASKER
We disabled DNS at the problem PCs under the TCP/IP configuration of each problem PC (TCP/IP, properties).
Thanks
Thanks
ASKER
I am closing this question
Thanks
Thanks
A request for a refund has been made. Experts, you have 72 hours to object.
SpideyMod
Community Support Moderator @Experts Exchange
SpideyMod
Community Support Moderator @Experts Exchange
I certainly do object. I pointed out the problem quite nicely i think.
from the thread i think that it is evident that the old win9x boxes had a hard coded and incorrect DNS setting and by turning that off he was then receiving the correct setting from dhcp.
from the thread i think that it is evident that the old win9x boxes had a hard coded and incorrect DNS setting and by turning that off he was then receiving the correct setting from dhcp.
Here's what I am doing in this case. I am awarding the answer to Tordan because technically the information provided should have solved the problem, but other factors on the machines may have blocked the resolution. I have also given vpc_bits the 50 question points back as the resolution used was to turn off DHCP and was posted here. Hopefully this satisfies everybody.
SpideyMod
Community Support Moderator @Experts Exchange
SpideyMod
Community Support Moderator @Experts Exchange
Works for me.
/grin
/grin
ASKER
Thanks