Recent content by mcymatt

Where there any network changes on Thursday or Friday? Server Changes? Hardware added? Ip address scheme? Service Packs / updates? What Sp for Exchange are you on? Office updates @ the local PCs?

If All users are on the same switch, are the ones that drop off in the same block? EX: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1-4 and 9-12 are the same block and 5-8 and 13-16 are another block of ports. Are you able to add another switch to test those ports?

You may want to use DNS also. Here we use DHCP for the IP addresses, DNS for all of the PCs & WINS for the old PCs. We have had no issues with Exchange dropping connectivity to Outlook users. The answer with the HOSTS file I used for some old 95 & 98 PCs that were taking a long time to connect...

Try using the HOSTS file. Make sure that there is no extention at the end of the file name.

What are you using for name resolution?

1. Is Outlook the only thing effected? 2. What protocols are you running? 3. Are all of the effected users on the same switch?

I had a similar incident. Look at the HOSTS file. You may have to alter the file. You will want to save as hosts.old then alter the file. If can only find the hosts.sam file, try adding the server in the hosts.sam file. copy the file and rename the file to hosts (noextention).

The PCs were not added the exchange / Outlook issue did not surface until we went from DHCP to static IPs. When I am at the PCs I added the IP address of the Exchange Server. The Ip address changes to the name then I cannot connect to the exchange server though Outlook. I only wish it was that...

This one is tough. A network of 9 PCs all except 2 can connect to the Exchange server. The 2 that cannot connect are Windows 98SE w/ Outlook 98 and Windows 95 w/Outlook 2000. Recent changes: 1. DSL services added 2. Firewall added. 3. Network changed from DHCP to static IP. 4. Router Ras turned...

I have had the exact same issue with a Compaq ML370. I am using an AIT drive. I called Compaq and they had me update the firmware on the drive. As of today, I have not had the issue reoccur but I am still waiting to see if I have another failure.