• Welcome! The TrekBBS is the number one place to chat about Star Trek with like-minded fans.
    If you are not already a member then please register an account and join in the discussion!

Vista and Outlook 2003 problem

I tried telnet'ing in. I'm successful on the XP box, but not on the Vista box. And that's what the head scratcher. Both boxes are hooking into the same router, but the fact that I'm successful on the XP box and not the Vista box is weird. And I swear the Vista box does not have it's firewall on!

I'm looking into one or two other things, but, if I can't get it to go tonight, I'm going to restore back to it's out of the box set up, and see if that works. Thankfully, I've Ghost'ed it, so it's not a big deal.

Okay last roll of the dice.

Go into control panel -> administrator tools -> services and stop the Windows firewall service. That way you make sure the thing is out of the way.
 
I tried telnet'ing in. I'm successful on the XP box, but not on the Vista box. And that's what the head scratcher. Both boxes are hooking into the same router, but the fact that I'm successful on the XP box and not the Vista box is weird. And I swear the Vista box does not have it's firewall on!

I'm looking into one or two other things, but, if I can't get it to go tonight, I'm going to restore back to it's out of the box set up, and see if that works. Thankfully, I've Ghost'ed it, so it's not a big deal.

Okay last roll of the dice.

Go into control panel -> administrator tools -> services and stop the Windows firewall service. That way you make sure the thing is out of the way.

Unfortunately, that was the first thing I did! Firewall is definitely off.

I'm going to try hardcoding the IP addresses, and see if that works.
 
Here's the latest:

I connected the Vista box direct to the modem. I've changed the hosts file to show the IP address for the mail servers. I've turned off all firewalls. I hardcoded the IP address for the mailserver into Outlook.

Still cannot telnet into or successfully connect to the mailservers.

Not sure what to try next. I think I may restore the machine back to it's 'out of the box' status, and see if that works. If not...??
 
Here's the latest:

I connected the Vista box direct to the modem. I've changed the hosts file to show the IP address for the mail servers. I've turned off all firewalls. I hardcoded the IP address for the mailserver into Outlook.

Still cannot telnet into or successfully connect to the mailservers.

Not sure what to try next. I think I may restore the machine back to it's 'out of the box' status, and see if that works. If not...??

I know you can telnet to the SMTP port from the XP system, have you checked to make sure there's nothing in the router's configuration that's blocking it?

Depending on the router you can allow various connections from one computer that you won't allow from another.
 
Here's the latest:

I connected the Vista box direct to the modem. I've changed the hosts file to show the IP address for the mail servers. I've turned off all firewalls. I hardcoded the IP address for the mailserver into Outlook.

Still cannot telnet into or successfully connect to the mailservers.

Not sure what to try next. I think I may restore the machine back to it's 'out of the box' status, and see if that works. If not...??

Can you ping the mail servers? It is not definitive if you can't as some servers do not return pings but is worth a try.

If you CAN ping them then you have a firewall blocking traffic on the Email ports. If Windows Firewall is turned off have you used a firewall like Zone Alarm or Comodo? These often do not uninstall gracefully.

If you can't ping them are you sure you have the server addresses correct?
 
I can ping the from the XP box, but not the Vista box. I actually have four XP boxes in the house right now (two desktops, my work laptop, and my personal laptop), and all can hit the servers. The Vista box can't.

I've verified the server addresses, both online and via tech support.

No other firewalls installed, other than Windows Firewall on the Vista box, and the firewall on the router (which I've disabled when I've been trying this).
 
So, here's the latest. I restored back to the original, out of the box configuration. Immediately went into Windows Mail - no problem connecting to the mail server!

Installed Outlook 2003 - again, no problem connecting to the mail server.

I'm leaning to some issue related to the Symantic AntiVirus and some sort of secret firewall that got installed that, no matter what I couldn't get rid of.
 
So, here's the latest. I restored back to the original, out of the box configuration. Immediately went into Windows Mail - no problem connecting to the mail server!

Installed Outlook 2003 - again, no problem connecting to the mail server.

I'm leaning to some issue related to the Symantic AntiVirus and some sort of secret firewall that got installed that, no matter what I couldn't get rid of.

Symantec has become a bloated piece of crap that causes way to many problems.

I have a simple solution for getting the thing out of the way when trouble shooting - set all the symantec services to either manual start or disabled then reboot.

And here's a thought. to filter mail for viruses etc iirc, the Norton stuff sits on the SMTP and POP3 ports to scan as the messages pass through. if the scanning program is screwed up then the messages can't pass through.

Though that wouldn't come into play when you ran the telnet tests.
 
Final result - fixed computer!

I ended up restoring from the 'out of the box' status, and reinstalling everything. Worked fine. I loaded everything back on without an issue, and have zero problems connecting.

Near as I can tell, though, it was Symantic AntiVirus causing the problem. Since I'm a DoD employee, there's an edition that I can utilize for free. I didn't load it this time, and instead went out and bought Norton 360 (FAR at Fry's today).

Everything is working fine. I don't know for sure that SAV was the problem, but it was the one thing that I didn't load this time, that I loaded last time.

Thanks for the suggestions.
 
^^^^

I had a similar problem once after uninstalling ZoneAlarm via the control panel rather than its own installer - not sure if that is still an issue with ZoneAlarm or not.
 
If you are not already a member then please register an account and join in the discussion!

Sign up / Register


Back
Top