Changed network to a fixed IP, now apple devices like iPads, Macbooks, iphones cannot connect. I see them on thw wireless tables, but they cannot resolve DNS so internet is inaccessible. Fix type ideas??
Are you connecting through a third party router, such as an Apple AirPort Extreme, or are you using the Shaw wifi modem?
If you're using a Shaw wifi modem, it's best to just set the devices to pick up an IP from the modem automatically. If you're using a third party router, it might require a setting inside the router to match the fixed IP to the devices' MAC address.
Hi, well it is a bit complex. The Shaw Cisco modem is set to "Bridge" so it is only a modem feeding into an Airlink (kinda generic) router and there are a couple of wireless access points as well. I changed the setup to a fixed IP address a few weeks ago, seemed to go okay, resolving the dreaded "Suspected Junk Mail" tag issue with Shaw emails. So far, so good. All the PC's and android devices connect well, either by Lan wire or wirelessly. However, people coming by with their iPhones and iPads and newer iPods cannot connect wirelessly. They connect to the wireless access points, I can see them and ping them, but no internet connectivity. Talked to a techie, tried putting a numeric IP address into the browser - worked! Just not particularly helpful.
Lotsa digging in google and Apple websites, again not particularly helpful. Apple had a pathetic response of "update the iOS".
So, appears to be a DNS issue, but I can't find a way to resolve it in the Shaw faq's, so I figured I would give you guys a whirl ... 'cause generally your efforts have been helpful before .. (thanx, BTW).
The router has room for 3 DNS servers and I added google.ca's besides the 2 Shaw ones, but to no avail...
Seems like Apple people are getting impatient, so I would really appreciate any ideas,
I have to admit I'm stumped on this one too. If PCs can connect to DNS servers but the Mac devices can't, there must be a specific setting that the Mac devices need.
On a side note, I'm confused on how changing to a fixed IP resolves the "suspected junk mail" tag issue with Shaw emails. Is an email program adding this to emails from @shaw.ca addresses? Or is this on emails received at your own @shaw.ca address?
Do we have any closet Apple Geniuses on the community?
You said you are using fixed IP on all your LAN devices, so the DHCP server is turned off?
Did you setup DNS servers on the Apple devices? Which DNS servers did you enter? This is what I suspect is wrong, is the DNS entries on the Apple devices, based on what you said above
Actually, it isn't fixed IP on all the devices. It is fixed IP on the router connected to the modem so the outside world sees a fixed address. I still use the DHCP on the internal network. The Apple devices worked before quite happily. Thing is, they are transient machines coming with friends and guests. There is lots of talk on the Apple forums of reinstalling the OS'es and/or deleting the mDNSResponder files and letting it rebuild it on bootup - certainly not something I want to have as a "guest routine".
The Apple machines 'should' get their DNS lookup stuff done by the Shaw DNS servers in the setup of the router, or as a failover with the Google DNS server I added to the third slot. But they seem to be stubborn about not playing nice. They get their DHCP internal IP address just fine, but cannot access the outside world.
I was hoping there was some experience out there on a different DNS setting in the routers on Shaw systems, or a magic setting in the Cisco modem, or a magic ....
What do you mean by fixed on the outside?
You setup a static IP that you didn't get from Shaw? - If so, do not do this, I can show you a trick that you can use with DNS that will allways be your DHCP assigned IP
No, it was setup working with the Shaw tech support, to an assigned IP from Shaw. They were good. However, a few weeks later this problem was handed to me, they helped me pin it down to a DNS issue, but they could not help me any further since it was a mac/ipad/iphone problem they did not have any suggestions for.
Thus, the efforts to find a solution to a problem centric to Apple devices, that Apple kinda admits exists, but will not address outside of the Apple ecosystem. One of their suggestions was to replace everything with Apple Airporters and macbooks. Not particularly helpful.
Oh, by the way - it was not the signatures in the emails, as tested and proven by tech support. The dynamic address had been used by somebody really suspiciously before we got it, and on days our 4 PC's were really chatty with emails going out with forwards and pictures of frigging cats in the mix - we went over the boundary and stuff got tagged. Fixed IP, simplified sigs, cautious forwarding and minimal cats have pretty well resolved the problem of junk tags by the Shaw SMTP servers. Lotsa fun getting to that point though....
SMTP issues are annoying to work though, for the most part it is a points system, so your signature may be the final point that flags it, someone else sending spam using that IP definately adds a lot of points...
If Apple kind of acknowedges an issue, I don't know what to suggest then, but replace everything non-Apple is in-line what I've gotten in the past...
Much more fun when everything is Apple...
Sorry man, I don't have any other suggestions
nslookup tests in a Terminal maybe
Yeah, Apple makes nice stuff, they just have an interesting outlook on co-existing.
I'll try nslookup in a Terminal session, otherwise I have to flash up Wireshark, which is a bunch of time I hoped to not put into this ... sigh ...
Hi, while Shaw was apparently having trouble with junk rules, the emails being sent out (from a shaw.ca address) were getting erroneously labelled as junk by the Shaw mail servers. Being sent from a dynamic address is one of the strikes against when evaluating "junk - ed- ness", so went to a fixed IP address and removed all the cute sigs and html graphics, so the outgoing emails were not tagged and then nuked.
Had way too many outgoing emails evaporate or labelled as junk, so had to do some serious digging on that one. Works well now.
Thanks for the interest, it all helps.
Likely the signature - lots and lots of experience with this one
Sending using a dynamic IP, using Shaw's outgoing mail server wouldn't be a factor
Sending using a dynamic IP, directly to another email server simply wouldn't work (Outgoing TCP 25 block)
I had similar issues maintaining a reliable connection with my Apple Time Capsule, I thought it was a DNS issue as well when I first started looking into it. Strange thing is I had the same problems with my linksys WRT54G running dd-wrt firmware. I called Shaw support and the tech assigned two IP addresses to my account. My connection is now very stable and all my routers and devices work well, I wouldn't mind getting an explanation as to why this was necessary.
Retrieving data ...