Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't connect to new Exchange server

Status
Not open for further replies.

YokyDoky

IS-IT--Management
Oct 11, 2002
73
US
XP Pro OS, Outlook 2002, local (XP) firewall is NOT enabled. The IS shop installed a new Exchange server and copied my account to it, old one is still online. When I try to switch to the new server in Outlook config, it says it can't find it. Does this on any XP machine - deleting my profile didn't fix it. Can't even ping the new Exchange server from any XP computer by either IP address or netbios name. I can connect to the new server without incident on either NT workstation or W2K Pro running any version of Outlook, doesn't matter, just hooks right up to it and brings me my mail. suggestions?

Y. Doky - "Manager" of Systems

"A .22 caliber intellect in a .357 Magnum world."
 
See Forum member xsrme's notes in this thread: thread858-742206
 
Fascinating, but no solution because NT workstation and 2KPro connect to the new exchange server without incident. Thanks though.

Y. Doky - "Manager" of Systems

"A .22 caliber intellect in a .357 Magnum world."
 
If you cannot ping the server from XP, this is troublesome indeed.

. You likely do not need a nag from me, but be sure ICF is disabled:
It does not prevent the outgoing ping, but it does screw up the possibility of a response to the ping.

. If you are absolutely sure that is an XP client only issue (all previous OS clients work without issue), I offer with faint hopes but fingers crossed the notion that you repair the Winsock service stack on the XP clients: See faq779-4625

. It is my hope that you are pulling valid IP, Gateway and DNS addresses from the XP clients. Does your IPCONFIG /All show reasonable results for these clients?

. XP is very fussy in ways that NT and Win2k as clients are not. See the first and last paragraph of faq779-4017

And keep us advised as to your progress.
 
bcastner - thanks for the tips, I'm following up on them now. I should mention that we use WINS. DNS is configured but not fully implemented so WINS is the chief resolver. I'm starting to suspect this is at the root of the issue, though, since the problems doesn't extend to earlier OSs.

This has the earmarks of a big problem, since the Exchange server is owned/maintained by the state IS agency and we have hundreds of XP machines here.

Y. Doky - "Manager" of Systems

"A .22 caliber intellect in a .357 Magnum world."
 
It is a very interesting issue. It bothers me, as something simple I hope is being missed.

Just to be very clear: If I went to your site and took a Windows 2000 workstation client, and physicly moved it to where you are testing now the XP client; connected up the Win2k workstation, and logged in with the username and password I had tried for the XP client, it would work? And if I then connected physicly the XP client workstation, logged in as the same user and password as the Win2k test workstation, it would not?


 
Does ipconfig/all return a WINS server entry?

Have you tried reinstalling the TCP/IP protocol?

Can it ping localhost/127.0.0.1?
 
bcastner - yep, the w2K machine is connected to the same hub in my office that the XP machine is. I use it for testing, etc. It dual boots with NT workstation. Thats how I tested the connection to the new exchange server with those 2 OSs. I went to a colleague's XP machine, which I had never before logged on to, logged on, and tried configuring Outlook to the new Exchange server. It failed just like it does on my XP, and I can't ping the new exchange server from either.

I VNC'd into an XP machine in a field office across the state, and pinged the new exchange server no problemo. SO that makes it sound like a firewall issue, but the w2K and NT4 machines are behind the same firewall the XP machines are, so...

We can connect to the old exchange server all we want without grief, regardless of OS or physical location.

Y. Doky - "Manager" of Systems

"A .22 caliber intellect in a .357 Magnum world."
 
YokyDoky,

Could you state the major and service pack identification for the version of Exchange you are migrating:

. From...
. To...

Thank you.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top