OL 2001 for MAC = wireless ??
RiDeRT
Using VPN client and wireless all works well except for OL 2001.
I suspect it's tied to OS X working fine VPN but somehow OS 9 running for OL
does not recognise the network..
Any ideas ?
Best regards,
Denis S.
Durham College
---
Outgoing mail is certified Virus Free.
Certifié ne contenir aucun virus.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/03
William M. Smith
> PowerBook G4 OS X - when connecting wired mode - all is fine.
>
> Using VPN client and wireless all works well except for OL 2001.
>
> I suspect it's tied to OS X working fine VPN but somehow OS 9 running for OL
> does not recognise the network..
Hi Denis!
Since you're comparing connectivity between a wired (non-VPN?) network and a
wireless VPN network, I'm assuming you're trying to access your Exchange
server from two very different networks.
Classic mode gets it IP information from Mac OS X and uses it as its own, so
I wouldn't believe that the difference between wired vs. wireless makes the
difference, but rather accessing from the LAN vs. accessing from outside the
LAN makes the difference.
The best way to test this is to use your Terminal or Network Utility (both
found in Applications --> Utilities) to ping your Exchange server. Try
pinging by IP address and then by name if your network uses DNS.
This should at least get you started in troubleshooting.
Hope this helps! bill
--
William M. Smith
(Microsoft Interop MVP)
Matt
We are having a similar issue and it has to do with wireless
connections. I have a client using a powerbook G4. When he is wired to
the network, outlook 2001 functions fine from classic. When we move
him to a wireless connection, we suddenly get connection delays and
eventually the application freezes. The wireless signals are strong
throughout the office so i'm hesitant to say that the connection is
the cause. I've tried increasing the memory allocation but with no
luck. Any help would be greatly appreciated.
thanks,
matt
William M. Smith
> We are having a similar issue and it has to do with wireless
> connections. I have a client using a powerbook G4. When he is wired to
> the network, outlook 2001 functions fine from classic. When we move
> him to a wireless connection, we suddenly get connection delays and
> eventually the application freezes. The wireless signals are strong
> throughout the office so i'm hesitant to say that the connection is
> the cause. I've tried increasing the memory allocation but with no
> luck. Any help would be greatly appreciated.
Hi Matt!
Wireless connections with good signals should cause no noticeable delays or
problems. But with wireless you may be suddenly on a different subnet or the
wireless device is not bridging the network properly.
The problem you're experiencing is probably due to the setup of the routing
from one subnet to the other or DNS.
If you have any DNS server entires made in your TCP/IP set, clear them or
make sure they are correct and accessible.
If you don't have any DNS server entries, maybe you need to enter a DNS
address or the address of your wireless device. Some wireless devices, when
routing, act as a DNS server for the wireless network.
RiDeRT
client, as our VPN is a Contivity device from Nortel.
Our security folks added these rings of fires to protect us from intruders
on the wireless side.
In wireless mode, I get an IP address and can connect to any internet
service and can even do email using Outlook Web access, but our users would
like the 'richness' of the full client in wireless mode, as they do using
the wired connection.
I cannot ping the name using wireless but can ping the IP address, I can
ping the IP address. Could I modify the HOSTS file in any way ? It looks
like our DNS on the wireless LAN is not setup properly...
Many thanks William - you're an incredible resource indeed.
Denis
"William M. Smith" <meck...@REMOVETHIS.mn.rr.com> wrote in message
news:BB43E3EC.10464%meck...@REMOVETHIS.mn.rr.com...
> Hi Denis!
>
> Since you're comparing connectivity between a wired (non-VPN?) network and
a
> wireless VPN network, I'm assuming you're trying to access your Exchange
> server from two very different networks.
>
> Classic mode gets it IP information from Mac OS X and uses it as its own,
so
> I wouldn't believe that the difference between wired vs. wireless makes
the
> difference, but rather accessing from the LAN vs. accessing from outside
the
> LAN makes the difference.
>
> The best way to test this is to use your Terminal or Network Utility (both
> found in Applications --> Utilities) to ping your Exchange server. Try
> pinging by IP address and then by name if your network uses DNS.
>
> This should at least get you started in troubleshooting.
>
> Hope this helps! bill
> --
> William M. Smith
> (Microsoft Interop MVP)
>
William M. Smith
> Right you are - only our wireless network uses VPN. We use the NetLock
> client, as our VPN is a Contivity device from Nortel.
>
> Our security folks added these rings of fires to protect us from intruders
> on the wireless side.
>
> In wireless mode, I get an IP address and can connect to any internet
> service and can even do email using Outlook Web access, but our users would
> like the 'richness' of the full client in wireless mode, as they do using
> the wired connection.
>
> I cannot ping the name using wireless but can ping the IP address, I can
> ping the IP address. Could I modify the HOSTS file in any way ? It looks
> like our DNS on the wireless LAN is not setup properly...
>
> Many thanks William - you're an incredible resource indeed.
Hi Denis!
First, thank you for the kudos. They're muchly appreciated! d:-)
Can you find out from your security folks if they are configuring firewalls
to specifically block ports used by Outlook? In particular, ask about port
135. If you can connect to the web and use OWA, you're using port 80.
If you don't use a Hosts file when connected via wire, you'll definitely
need one when you're connected via VPN and DNS doesn't work. Does this sound
like your case?
Let me know what you find out.
Thanx! bill
RiDeRT
what would the syntax look like ? which one would come first, or does it
even matter ?
Does port 135 need to be open ?
Denis
"William M. Smith" <meck...@REMOVETHIS.mn.rr.com> wrote in message
news:BB4B4825.111A5%meck...@REMOVETHIS.mn.rr.com...
> Hi Denis!
>
> First, thank you for the kudos. They're muchly appreciated! d:-)
>
> Can you find out from your security folks if they are configuring
firewalls
> to specifically block ports used by Outlook? In particular, ask about port
> 135. If you can connect to the web and use OWA, you're using port 80.
>
> If you don't use a Hosts file when connected via wire, you'll definitely
> need one when you're connected via VPN and DNS doesn't work. Does this
sound
> like your case?
>
> Let me know what you find out.
>
> Thanx! bill
> --
> William M. Smith
> (Microsoft Interop MVP)
>
William M. Smith
> I do use a HOSTS file when wired - can I have a few entries in there then ?
>
> what would the syntax look like ? which one would come first, or does it
> even matter ?
>
> Does port 135 need to be open ?
Hi Denis!
VPN should be putting you on your company's network, so the Hosts file you
have should work both when wired and through VPN. FYI, if you did have to
change it, the order of entries does not make a difference.
I know UDP port 135 is used for Exchange server communication and probably
should be open, but I'm not expert enough to know if this is everything. I
did find this article on the web. Maybe it will shed some light.
http://www.zdnet.com.au/itmanager/technology/story/0,2000029587,20276509,00.
htm
Hope this helps! bill
GadgetFreak
Im still at a loss on this one. I have a cable modem that hooks up to
the Airport. When I use the Airport and the Cisco OSX VPN it works
fine except for connecting to Exchange. I can mount drives etc., but
no Exchange connection. If I unplug the Airport and plug that line
directly into the Mac it works fine with the VPN, including Exchange.
On another, older MAC that can be booted in OS9, I can start the OS9
VPN and Exchange works wirelessly. If I boot that Mac in OSX VPN
works wirelessly for everything except Exchange. I have seen the same
thing when travelling as well. I can never get an OSX connection to
Exchange using the OSX VPN. Even tried putting an OS9 VPN on and
running in Classic mode, no dice. By the way the OSX Exchange works
fine if I dont need to run the VPN (in my office for instance). Im at
the end of my rope on this one. Worked for weeks with our IT guys and
couldnt get it going. We decided to wait for OSX Outlook figuring
that would solve it. Since that apparently isnt coming I really need
to get this to work or ditch the Mac. Thanks for any help.
"William M. Smith" <meck...@REMOVETHIS.mn.rr.com> wrote in message news:<BB4BCD16.112F0%meck...@REMOVETHIS.mn.rr.com>...