Another one - Strange.

[pikk67]

Hi All

So...I got my Exchange server up and running nicely now except for remote access while vpn'd into the office. With my old 5.5 Exchange box, I could easily connect to my office via VPN and run Outlook and send/rec'v email. I simply used a LMHOSTS file with my Exchange server entry...among others. Now, with my new 2003 Exchange box on my Windows 2003 domain...I am doing the same, exact thing only now I keep getting "Disconnected" when I open Outlook. It sees the Exchange server just fine (shows up properly in the Mail Properties) and I have none of the usual "Exchange is offline" type errors but it stays disconnected!!

Any ideas???

P

 

[lebisol]

hey pikk67,
Here are few things that come to mind:
-What has changed in VPN? is there some form of QoS?
-Is lmhost file updated?(I am sure u aware of the pesky specs. on spacing/naming conversion)
-Can you ping the server?
-Can you get any name resolution accross the vpn pipe? can u see any shares on the same server?
-Is it the vpn subnet perhaps filtered out on your gateway server?
-Is the server set on static IP? and or was there perhaps 2 nic cards used and one of them was disconnected?
-Is this a new domain or the same domain where 5.5 used to sit?
-Any authentication errors in the log files?
-Any change when services are restarted?

So these are some of things that I would investigate...sorry if you find some obvious Qs in here...but u never know..


All the best!

:--------------------------------------:

[URL unfurl="true"]http://mostarnet.com[/url]

All around in my home town,
They tryin' to track me down...

 

[pikk67]

Lebisol,

Thanks for the tips and checklist. However, I did manage to resolve it earlier. It was a DNS issue...or at least so it seems. For whatever reason, it would not authenticate unless I added my DNS server IP manually in my NW Properties. Go figure. )

Thnx again!

Pikk

 

[lebisol]

glad u got it going...sometimes checklist is good...u can find what you don't see written
I hope this was DNS issue on client side not the server side...

if on client side:
I ran into some infected clients a that had tcp/ip really twisted....all looked good except the fact that I had to manually assing net properties it would hate the DHCP and even static IP was being reported as a duplicate after some time...all kinds of strange layer3 crap.To make the game that much more interesting it happend right after I edited LMHOST files....then it all added up .
so perhaps worth looking into that machine for infection...WinsockXPFix & LSPFix could be your friends along with other removal tools...
then again...it may be a hickup
All the best!


:--------------------------------------:

[URL unfurl="true"]http://mostarnet.com[/url]

All around in my home town,
They tryin' to track me down...

 

[pikk67]

Lebisol

Great stuff! Thanks again for your help.

Have a great day.

P'