Outlook 2000 clients unable to open mailbox

[scoobydoo26]

Ok, here goes a brief summary of the problem...we've recently moved offices where i've setup the network with a couple of hubs (for now), NT 4.0 SP5 PDC and Member server with Exchange 5.5 SP3 on NT 4.0 SP5 machine. After setting everybody backup on the network there a couple of machines that cannot access their mailboxes. Everything else is fine.

In my troubleshooting...i've able to see exchange in net neighborhood, am able to browse and access shared folders and also able to ping it with no problem. When i open outlook it timesout and says there is no exchange server available. It's been a long couple of days and i think my brain is fried so if i've missed anything, any help would be VERY WELCOME

The only thing that has changed is right now i'm waiting for the SDSL line at the new location and i don't have the router setup. The NT server is acting as my DHCP server for the moment


THANKS IN ADVANCE!!!!

 

[Zelandakh]

What about control panel mail and fax, can you put in the server and username and check name?

You need BOTH netbios and ip name resolution working for outlook to work.

Why using NT SP 5 and Exchange SP3? They are both 1 SP behind.

 

[KeyTech]

Try this to get more info on whats happening....
Go to the exchange server and launch the Exchange Server Administrator, then go to the Connections, and the Internet Mail Connection. Then go to the Diag Logging tab, and in here set all catagories to Maximum. This will cause any faults or errors or reports to be logged in the Event Viewer Application log. Check in here every few mins to see whats happening and if the users are being refused or if the licence's are exceeded etc....
hope this helps.... Jay~

"I have to think of a funny footer to
put in here!!!???"

~KeyTech

 

[scoobydoo26]

thanks...will try this as i haven't checked the logging in admin. I do have wins and dns up and running.

 

[Maruis]

Outlook uses name resulotions to get to the Exchange server. Not our IP address. If the WS can resolve the Exchange server name you wil be ok.
I.E.

"ping exchange" instead of "ping 192.168.0.50"

a DNS entry will help or a WINS server to help resolve IP's to NetBios names