SpencerSteel
asked on
ISA and XP
Hello all,
Just got a couple of lovely laptops which run XP Pro. I'm used to 2000, but i'm getting to find out where everything is...just about.
However, my Firewall Client does not seem to 'work' - I've insalled the client and it connects OK - but both MSN and POP3 mail is not happening. The only network difference between my old machine and this new machine it's IP address, they are both in the same 'Admin' type client groups for access etc...
The logs report that although my machine is being logged using the Web, there are no FW logs at all ...
I'm a newbie with ISA Server - but I really can't see what could be up ... any ideas ?
Baffled in London
Spencer
Just got a couple of lovely laptops which run XP Pro. I'm used to 2000, but i'm getting to find out where everything is...just about.
However, my Firewall Client does not seem to 'work' - I've insalled the client and it connects OK - but both MSN and POP3 mail is not happening. The only network difference between my old machine and this new machine it's IP address, they are both in the same 'Admin' type client groups for access etc...
The logs report that although my machine is being logged using the Web, there are no FW logs at all ...
I'm a newbie with ISA Server - but I really can't see what could be up ... any ideas ?
Baffled in London
Spencer
ASKER
Thanks - but that is a bit of red herring - it's not that i'm not getting email, sorry - it's just ISA wont let it use any anything ...
MSN Messager is a good example - I have my 'old 2000' machine here and my new XP machine. Both have firewall client. The 2000 machine connects using HTTP Proxy 1.1.1.4 and port 1863 - I do exactly the same on an XP machine and hit the 'unable to sign in' messages. The POP Outlook Express account cannot connect to get the initial IMAP folders ... so it would appear a rather generic problem with the ISA Server not allowing my XP machines through.
It was a long shot but I wondered if this was a known issue - or there was something 'special' to do with an XP box - because normally this is a breeze
*humph*
Spencer
MSN Messager is a good example - I have my 'old 2000' machine here and my new XP machine. Both have firewall client. The 2000 machine connects using HTTP Proxy 1.1.1.4 and port 1863 - I do exactly the same on an XP machine and hit the 'unable to sign in' messages. The POP Outlook Express account cannot connect to get the initial IMAP folders ... so it would appear a rather generic problem with the ISA Server not allowing my XP machines through.
It was a long shot but I wondered if this was a known issue - or there was something 'special' to do with an XP box - because normally this is a breeze
*humph*
Spencer
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I don't believe this - on the firewall client - i just unchecked 'Automatically detect ISA Server' (then Update), and everything started to work ! The ISA Server name was always in the box provided.
I noted that it kept 'dropping' the Firewall session (hover over it and it would say Not Connected or something) - but I could reconnect ... but it would behave strangly
But as I've just said, the unchecking of 'automatically discover' worked
How odd.
Have some points just for being awake and listening to me rattle
S.S.
I noted that it kept 'dropping' the Firewall session (hover over it and it would say Not Connected or something) - but I could reconnect ... but it would behave strangly
But as I've just said, the unchecking of 'automatically discover' worked
How odd.
Have some points just for being awake and listening to me rattle
S.S.
Hi Spencer,
Say to yourself over and over, "it's Microsoft.... it's Microsoft.... it's Microsoft....."
Glad you solved it,
Kent
Say to yourself over and over, "it's Microsoft.... it's Microsoft.... it's Microsoft....."
Glad you solved it,
Kent
Are both of these machines on the same subnet?
It could be that your e-mail server doesn't know that the new address is a local address and is trying to be a good citizen by not forwarding what could be spam. Check your e-mail server settings to make sure that it know that the new address is a "good guy". :)
Good Luck,
Kent