iPass is not a corporate VPN. Its just a client application that identifies available connection methods and uses iPass account credentials to provide internet access via a third party provider (Telstra in this case) while providing cerntalised billing.Evan said:Possibly an iPass client ?
iPass can look like a normal login but is actually a VPN connection to your corp network, you can still use iPass now if you want to.
E
In fact that is exactly how I am using it right now from my home WiFi network. I use it to select between the 3 different SSIDs I run here.Evan said:iPass is also used to connect even at non iPass free internet access hostspots. Just the way i have seen it configured before on my travels.
wallacej said:I have no problem with receiving email, but sending is another story.
The message will appear to be sent, then I will get an email back saying that the message I just sent has not been sent, along with some other tech details. So I take my messages in, respond, then send when I have hooked up my telstra wireless card, or back onto my own network??
AnonymousCoward said:What protocols are you guys using to send email using Outlook?
If connecting back to an Exchange 2003/2007 server, then RPC over HTTPS (now called "Outlook Anywhere") works just fine. That tunnels everything over HTTPS. As mentioned earlier in the thread, ensure that you have "logged" in to the Telstra network first.
If you are using SMTP or IMAP, then perhaps the ports are being blocked? You may need to route the mail through a Telstra SMTP server
You are not alone...wallacej said:Unfortunately I don't understand most of what is written here, although I am sure it is all useful stuff.....
AFF Supporters can remove this and all advertisements
wallacej said:My account is with bigpond.net.au - I can receive mail, but the send still bounces back as
550 relaying mail to xx_xx_xx_xx.com.au is not allowed - the x's being the @ part of the email address.
I sometime use iiNet dialup, but still get the same problem...