Westell 9100EM - DNS issue.

Some time ago DNS started to work unstable.
I've read similar cases around, but none of them looks similar to mine...
DNS stop functioning all the time for several seconds...
E.g.. If I constantly do the nslookup than at least once a minute I'm getting behavior showed below.
At the same time, Google DNS responds with no issues.
I managed to configure most of my numerous devices to use Google DNS, but I do not like such approach.
Router firmware update did not help.
In router logs there is a line:
Apr 19 22:31:23 2011 System Log Message daemon.warn DNS: unknown PTR name format
I could not find correlation between this line and issue, but I did not look deep enough, though.
Any ideas?
Thank you.
DK
C:\Program Files (x86)\Far2>nslookup verizon.com 192.168.1.1
Server: myrouter.home
Address: 192.168.1.1
DNS request timed out.
   timeout was 2 seconds.
DNS request timed out.
   timeout was 2 seconds.
Non-authoritative answer:
Name: verizon.com
Address: 192.76.85.245
C:\Program Files (x86)\Far2>nslookup verizon.com 192.168.1.1
Server: myrouter.home
Address: 192.168.1.1
Non-authoritative answer:
Name: verizon.com
Address: 192.76.85.245
C:\Program Files (x86)\Far2>nslookup verizon.com 192.168.1.1
Server: myrouter.homeAddress: 192.168.1.1
DNS request timed out.   timeout was 2 seconds.
DNS request timed out.   timeout was 2 seconds.
Non-authoritative answer:
Name: verizon.com
Address: 192.76.85.245
C:\Program Files (x86)\Far2>nslookup verizon.com 192.168.1.1
Server: myrouter.home
Address: 192.168.1.1
Non-authoritative answer:
Name: verizon.com
Address: 192.76.85.245

(I'm topicstarter here)...
Funny thing, I contacted Verizon customer support recently and encountered very intellegent and responsive person who read all the details (I used the live chat option) and suggested to replace router for free with the new one - not Westel, something starts with letter A.
I was little bit disappointed that new router had only 100Mb switch and no 5GHz band support... But at least it supports the wifi-N...
Anyway, I do not need all these bells and whisles cause I'm using NetGear router for wifi + Cisco home switch for wired network.
Sorry, I deviated from the main issue course.
I do not have any update on the DNS issue cause all my devices still configured to use Google DNS servers.
However, I expect that quite soon I will get Logitech Revue and will have update on this issue.

Similar Messages

Westell 9100EM VPN Issue

I have a work laptop that utilizes a Cisco VPN in order to communicate to the work server. I connect wirelessly thru my home network via the Westell 9100EM. This has worked flawlessly for 3-4 years.
Less than a week ago, it stopped working. I could access server based drives via a hard IP address but not the normal way. Likewise, OUTLOOK no longer would access the email server.
Three observations:
1. I went to a Starbucks and attempted to use the VPN. This was successful (wireless).
2. At home, I then tried a wired connection to the Westell router and it also successfully connected via the VPN.
3. Normal wireless connectivity (no VPN) via the Westell functions correctly.
The VPN connection fails only at home and when using wireless connectivity - this failure only manifested itself about a week ago after 3-4 years of successful operation. I have also performed a hard reset of the router to no avail.
Any insight into this issue and resolution would be appreciated.

Well, I just got the replacement Westell router (a Rev. B - mine was a Rev. A) and set it up to try it out.
**bleep** if it didn't fail in the same way! I guess it's not a router issue after all. I am completely stumped as to why the VPN fails wirelessly only at my home. More ideas and comments are welcome.
BTW, I think I will keep my old router and return the new one. My old router is "burned in" and has more options than the new one in some areas. Also, Verizon gave me a contact number for Westell tech support - I'll be calling them next week.
Harvey

Computer not being registered in DNS on Westell 9100EM

I have a Westell 9100EM in my office where some systems register in the DNS and some not. All the systems are in the connections page. All Three PCs are Windows XP, 2 have no problem, just one. I have tired ipconfig /release, ipconfig /renew and ipconfig /registerdns in that order, checking the Westell DNS each time, no change. The two printers register no problem, my D-Link NAS registers. I just need to get this last PC to register. I have compared TCPIP properties, all 3 XP systems are the same. Any ideas?

This came from another thread, but worked for me. Problem is with newest iTunes 4.62 and Windows 8.1. Unistall iTunes, as well as its helper programs (Apple Application Support, Apple Mobile Divice Support, and Apple Software Update). Reboot, and reinstall iTunes. It will reinstall all the other ones and you should be able to connect your nano. Good luck.

Westell 9100em router forgets custom DNS Setting

Is anyone else trying to use custom DNS settings with their Westell 9100em routers? My problem is that when/if it loses its connection to Verizon (either system glitch or power on/off), the DNS settings revert to the system default (choose automatically). I use OpenDNS...and its great. This is very frustrating. I used to have an Actiontec that worked just fine before the router itself died.. This problem seems to be specific to Westell - it remembers everything else (SSID, security keys etc) but resets the DNS settings.
Tech support has been no help. They just send me a new Westell (arrrrrgh!) that does the same thing . Apparently the shipping people just pull "a router" off the shelves and ship them. Seems like a firmware bug to me. Today they sent me to the 'Billing group" who told me that I'd have to pay $150 if I wanted an Actiontec!!!!
All I want is for them to send me the latest Actiontec (since I never had this problem with them before).
Anyone else run into this? How'd you resolve it?
Thanks

The router rebooted itself...DNS lost.
Aug 16 18:55:54 2011System LogMessagedaemon.info WAN-en2210: link down, device will be down

Fios Westell Model 9100EM firmware issue

So i'm a born again Fios Internet owner, since I move from an area where I had Fios to an area that didn't and now move again to an area that has it.
I was given a cd about my router, and saw information about updating the firmware. I log into the router control panel where it asked about the URL to the firmware. I did not know, so I Google the model and firmware, and I was brought to this POST...
So I looked up the fireware for my router and they provided a firmware of 1.02.00.04, but the firmware on my router currently is 1.03.00.08. Of course it wouldn't allow me to install the downgrade, but why isn't the 1.03.00.08 not on there?
Fios Router Firmware Download Site

It's actually a good thing 1.03.00.08 isn't on there.
It breaks routers, as you can see from the post I made a couple days ago: http://forums.verizon.com/t5/FiOS-Internet/Where-have-all-my-router-s-features-gone-Westell-9100EM/t...
But, if you're really interested, here's the URL for the firmware: http://download.verizon.net/webdownload/firmware/upgrades/westell_router_9100em/A90-9100EM15-10-1.03...
Also, if you read through my post, downgrading is possible, but it takes more work than the average user may be willing to do (and even still, Verizon forces new updates on your router, even if you don't agree to them).

Wireless IP Camera Won't Connect To Westell 9100EM Router

I'm trying to connection an IP camera, on Fios, to my Verizon Westell 9100EM router.
Connecting the camera via a wired connection works fine. Port forwarding is automatically configured when turning the camera on, at TCP ANY 554, and the IP camera is viewable on the web. No worries.
However, when unplugging the cord, the router never recogizes the camera. Not after resetting, powering off/on, etc. Both the WEP and SSID are set correctly on the camera. All other wireless devices (laptops, Xbox 360, iPhone, etc.) work fine on the router.
Naturally, the camera people blame Verizon and Verizon blames the camera people.
Does anyone have any ideas?
Thanks!

What are the details on the camera (Make, model, etc) ?
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it.
If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Trouble replacing Westell 9100EM router w/ Asus RT-AC68U

I got a new router (ASUS RT-A68U) and want to replace the Westell 9100EM that came installed w/ my FiOS package.
I have the new router connected, and it can get to the internet just fine. It's gui says it's connected to the internet, and I can use it's onboard diagnostics to ping google.com, do a tracert, etc. However, none of the devices I connect to the new router can get an IP address. My WIRED connection from the PC to the router is unable to get an IP, even after ipconfig /release and /renew (Windows 7, from command line). My mobile phone can connect wirelessly to the new router, but is also unable to get an IP address.
Are there some settings I need to manage in order to have it automatically assign IPs to connected devices? I've set the new router to use google's DNS servers (8.8.8.8 and 8.8.8.4). Do I need to use verizon's servers first? Is there a change to the subnet mask or anything else that I'm missing?
Thanks to anyone who can offer some advice
-Adam

ajhartman wrote:
I got a new router (ASUS RT-A68U) and want to replace the Westell 9100EM that came installed w/ my FiOS package.
I have the new router connected, and it can get to the internet just fine. It's gui says it's connected to the internet, and I can use it's onboard diagnostics to ping google.com, do a tracert, etc. However, none of the devices I connect to the new router can get an IP address. My WIRED connection from the PC to the router is unable to get an IP, even after ipconfig /release and /renew (Windows 7, from command line). My mobile phone can connect wirelessly to the new router, but is also unable to get an IP address.
Are there some settings I need to manage in order to have it automatically assign IPs to connected devices? I've set the new router to use google's DNS servers (8.8.8.8 and 8.8.8.4). Do I need to use verizon's servers first? Is there a change to the subnet mask or anything else that I'm missing?
Thanks to anyone who can offer some advice
-Adam
Reset the router to factory defaults by pressing the reset button,
By default the router is set up as 192.168.1.1 so enter that address in a browser and connect
The default login is uerid admin and password admin
you should be able to use Quick Internet Setup QIS
Your fios account will give you an automatic dhcp address and no userid and password is required for that
at this point your router should be connected to the internet.
Using the main manu select lan and make sure the dhcp server is turned on (it's the radio button toggle at the top), should be by default and it should be handing out addresses on the 192.168.1 subnet.
On your machine run cmd and type in ipconfig /all - certify that you have an ip address of 192.168.1.x
If you've set the router dns to the google dns servers after the router reset then ipconfig should also show you that your dns servers are what you entered on the router if so
All is OK an you should be up and running
You'll probably want to change the default wireless settings, how to do that is inb the user manual.
There is no need to reference the Verizon dns servers

Westell 9100em crashes periodically

I have had a Westell 9100em for about a year - (model no A90-9100EM15-10, firmware version 1.02.00.04),
Every so often, the router crashes and loses all configuration information. In addition, all log entries are wiped out except for a number of entries that read December 31, 2002. This usually happens when I am away and most dependent on having access to my network.
UPNP is disabled. I am using WPA/WPA2 security on the wireless. I have static mac addresses that are working fine when the router is up and my connection is coax.
More recently I have discovered that one thing that can cause it to crash is trying to access the wireless from a MAC laptop. Even if a machine is not authorized to access the wireless, I don't think it should be crashing the router,
Verizon replaced the router a couple months into this and it seemed to go away for awhile, but maybe I was just lucky and no MAC users were trying to access my wireless. It seems like a firmware issue and I see similar symptoms reported but only the one solution - turning off UPNP - which didn't help in my case. As near as I can tell, the firmware version I have is the latest. Any ideas anyone?
Thanks in advance!

This is a problem with verizons equipment i have the same issues. I recently was contacted by someone at verizon who is contacting the distributors of these routers. Hopefully they get the problems fixed.

Flaky VOIP with Westell 9100em

After adding FiOS TV last week my voip started flaking out, working sometimes, then not. I've moved my voip box to the DMZ of the router without any change of behavior. I can receive calls, but as soon as I do I cannot dial out for a while.
After chatting with my voip provider they said the Westell 9100em is the problem and SPI is getting in the way. I tend to agree with that diagnosis but do not know how to fix it. I don't know a lot about SPI, but it's frustrating the the DMZ isn't really wide open to the world.
I tried some Advanced Filtering rules to disable SPI without luck.
Any suggestions greatly appreciated. I really like my voip provider but I'm unwilling to put their box in front of the Westell router.

You did setup a static IP that is outside of the DHCP range of the router:
portforward.com -> forum -› Knowledge Base -› How to choose a Static IP address
http://forum.portforward.com/YaBB.cgi?num=1116577357
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Westell 9100em: Ports not forwarding

I moved into a new apartment recently with Fios and a Westell A90 9100EM15-10 and I haven't figured out how to port forward with it yet. I need these ports forwarded:
7777(TCP/UDP)
28900 (TCP)
27900 (UDP)
28910 (TCP)
I followed the instructions an admin posted in this thread: http://forums.verizon.com/t5/FiOS-Internet/port-forward-on-new-Westell-9100em/m-p/3021
However, when I test the ports (for instance, port 7777 http://www.utorrent.com/testport?port=7777 here,) it never says any of them are open. I have followed the directions step by step. On the port forwarding menu, it lists my entry for these ports as active for the local host and address 192.168.1.35, the static IP I have assigned to my computer. The protocols read as follows:
TCP Any -> 7777
        UDP Any -> 7777
        TCP Any -> 28900
        UDP Any -> 27900
        TCP Any -> 28910
I have experience with port forwarding in the past with a Linksys router, but it apparently simply is not working out for me with this Westell. Any assistance is appreciated...

Do yours actually open? I know Borderlands has serious connectivity issues right now. My issue is that it doesn't seem like these ports are ever actually open for me. I don't see why every port check site I used should return "closed" if they're actually open.

DNS Issues with Time Capsule - DNS Proxy periodically dies

hi all .... looking for some suggestions
I have a time capsule 1TB, connected to a linksys adsl modem in bridge mode, with the TC acting as DHCP server for my local clients. In the PPPoE settings I also enter the primary and secondary addresses for DNS that my ISP supplied.
I am able to successfully connect to the internet, and all clients successfully pick up an IP address, and each client picks up the TC as the DNS proxy. Everything works perfectly as it should.
Usually once per day, there seems to be a slight hickup with the internet connection (hard to tell whether I am losing the PPPoE or some other issue). When this happens, the PPPoE connection remains active, as I am able to access anything on the internet from an IP level. However, the DNS proxy service on the TC seems to die and as a result, all internet browsing fails. If I reboot the TC, everything comes back to normal. If I dont reboot, the only way to get browsing working is to manually enter the DNS IP address from ISP into the client PCs. However, this is a manual fix that I should not have to perform.
Looking for advice and guidance. Seems like a bug but I cant tell. If I was able to set the DHCP server to pass out the ISP supplied addresses that would also work, but I cant.

Just got off the phone with support for this very same problem. DNS Proxy is definitely dying in the TC, looks like a firmware issue to me.
This is the 3rd TC I'm on. First was a 500GB, had this problem, replaced it under warranty at Apple's direction, replacement did the same, just upgraded this weekend to 1GB, and same issue still. All on 7.3.2 firmware.
TC 1TB, PPPoE to my ISP, ISP's DNS Servers listed in the PPPoE config in the TC.
When a host gets DHCP from the TC the only DNS returned is the TC itself, since it proxies the ISP DNS servers.
Once every day or two, the DNS proxy dies. local network works, and I can add my ISP's DNS addresses in my host config and I have DNS again, but this is definitely something dying in the DNS proxy in the TC.
Just for kicks trying to switch from my ISP's DNS servers to OpenDNS now since someone said that worked for them, but I am not hopeful... I don't see this as a host DNS issues at all.
The dead proxy is very clear:
$ nslookup apple.com. 192.168.1.1 # that's the TC
Server: 192.168.1.1
Address: 192.168.1.1#53
** server can't find apple.com: SERVFAIL
$ nslookup apple.com. 208.67.222.222 # that's OpenDNS
Server: 208.67.222.222
Address: 208.67.222.222#53
Non-authoritative answer:
Name: apple.com
Address: 17.149.160.49
I replaced a linksys router with the TC and am kind of unhappy that a $500 router dies every couple of days. My cheapo Linksys router never needed to be restarted, it only ever got rebooted once every year or so when the house lost power long enough for the UPS to run out of battery.
Help us out here Apple, I replaced a $50 router with a $500 because I like the flavor of your kool aid, and this thing dies every day or two. Even if you can't fix why the proxy is dying every couple of days, can you please at least update the firmware to maybe restart the proxy if it quits working?

ITunes not responding due to DNS issues?

iTunes 11.1.0.126 on Windows 7, never had a problem in the past 5 years... iTunes runs 24/7 on this machine. It has been running for days since my last reboot, maybe a week. I was listening to a podcast, then went into the store to search for an artist, clicked on an album, listened to preview, back button, different album, preview, back button, different album, etc then one time when I clicked the back button iTunes became unresponsive until I had to kill it.
I can no longer open iTunes, it always opens as a transparent window with a border and is immediately "Not responding" in task manager. Same thing happens in safe mode. I tried rebooting too.
Around this time I started noticing other problems with my internet connection. Seems like my provider is having DNS issues because certain websites hosted on the east coast won't load, but west coast websites will (I am on the west coast). I tried loading these websites on my phone through cell data and they worked, so I figured my provider is having problems.
Now I'm wondering if iTunes calls home or tries to make some sort of connection when it loads, regardless of safe mode or not, and this causes the application to hang immediately. Does anyone know anything about this, or how I might be able to get the iTunes application to run again?

Well, it wasn't a DNS issue, it was a routing issue that affected ISP customers in half of the country. https://community.shaw.ca/thread/9284?start=0&tstart=0
I can confirm that iTunes will now open and is functional. It seems that if the application can't access some internet resource immediately when it launches it will immediately lock up and never come back! No offline mode??!?!

Internet DHCP/DNS issues with WRT1900ac

I've had a WRT1900ac now for about 2 weeks and the problems seem to be escalating. Need help. And yes, I've already read dozens of threads about these issues and nothing seems to be working.
Most of the problems seem to be centered around this DHCP/DNS issue that so many have been reporting.
First, the symptoms:
Galaxy S4 phones when connected via wifi have some apps that don't update (facebook and google play)
Some computers (both Win 7) will connect to the network just fine, both wired and wireless - but won't be able to get to the internet
I've spent the last 2-3 days of my life reading forums and trying all sorts of things to get this to work properly (like my old router) and I'm still stuck. Some things I've tried:
Firmware is up-to-date (latest version: 1.1.8.164461)
Manually assigned static DNS in router config settings (connectivity -> local network) to various combinations including the router address, 8.8.8.8, 8.8.4.4, 75.75.75.75, 75.75.76.76 (I have comcast), OpenDNS addresses, etc. I read that the router address is not needed, so I stopped including it.
I manually assigned IPs and DNS on the Galaxy S4 phones and that seemed to work... but also seems unnecessary.
I've reserved DHCP addresses on the computers in question, that didn't seem to work, I also manually set DNS on one of the comupters (can't on the other... long story/not my computer) and that worked for a while and then stopped working.
The only way to get one of the computers on the internet now is to turn on the guest network (even though the computer is hard wired to the router), connect, and then the wired network works. No clue why this is, but my guess is that it needs the guest network for DNS, then it fails back over to the wired network. Once that happens, I can actually turn off the wifi on the computer and everything works great... until I reboot. Key point: I can't change any settings on that box other than entering in SSID/passphrase info for the wireless connection. I can connect to the regular (non-Guest) wifi just fine - I just can't ever get to the internet.
I've tried massaging DHCP settings on the router until I'm blue in the face - Static DNS, reserving DHCP addresses, hell I even put one of the computers in the DMZ to see if that would work and it still can't connect to the internet (it's worth noting that with my old router, Linksys WRT310N, the setup was literally plug-and-play - no hassle with any of this).
I've tried countless router reboots, factory resets, turning off my modem and router for 2+ minutes, and nothing is working.
I even read somewhere that if you modify your DHCP settings at all that the WRT1900ac stops doing DNS properly and breaks, so I even tried several "hard" factory resets and used all the default DHCP/DNS settings. And it worked... for a few hours.
Seriously, I'm at my wit's end. I'm out a lot of money on this thing and it's been one headache after another. Please help.

I think for most people its a bad idea to hold out that hope, lol. It seems like a great piece of hardware but if you really need a router and don't want to have to 'play' with it, its probably not a good choice. I have an EA6900 that I am very happy with but it has the same restrictions as far as DNS and I really hate the idea that I am forced to use the smartwifi portal. I would really like for them to give me a choice of the old gui or the new one and let ME decide. Lots of routers to choose from out there now and new ones seem to be coming out all the time so do some reading and see if something suits you better. Good luck!

[SOLVED] Greetings... and DNS issues... (why is it so slow?)

Hey everybody!
My name is Stephen. I'm new to Arch (hence I'm posting in the newb forum). A bit of background: I'm a CS major in the good 'ole US of A. I used Debian/Ubuntu for 2 years before now. I actually installed Arch just yesterday, so today is my second day of usage. Why do I want to switch from Ubuntu? Several reasons, but they can all be summed up thusly: I want to tinker with and understand how my machine works. I don't want to interface with a blackbox that just "works." Arch seems to be geared towards what I want.
And I've been learning alot, haha. Which I why I am now here to ask for help.
I originally installed Arch at school. Everything was great. Then I took my laptop home and I found out something was wrong. Pacman took an extra 5-15 secs before each download started, but once the download started, I got normal speeds. I observed a similar behavior in my web browsers I tried (Firefox/Surf). No matter what I do, this behavior persists. I suspect this is a DNS issue, and thus I have tried the follow methods of correction so far.
1) Reinstalling to a default configuration.
2) Disabling IPV6.
3) Screwing around with etc/hosts, etc/resolv.conf, and etc/dhcpcd.conf (though I probably did something wrong. Also, I'm not sure how to force Arch to accept my changes after modifying these files.)
I also read somewhere that using HTTP mirrors works better for pacman, but I already was using an HTTP mirror anyway, so I knew that couldn't be the problem.
I have not tried DNS caching yet. However, given that every other machine in the house runs fine, I suspect it is my configuration that is wrong. Does anybody know how I can pinpoint this as DNS for sure? And if so, how I can fix it? Thanks for all your time/help!
Here are some config files/snippets of interest. Most of this should be straight from a basic Arch install.
etc/resolv.conf
# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
domain domain.actdsltmp
nameserver 192.168.0.1
nameserver 216.165.129.157
# /etc/resolv.conf.tail can replace this line
Note that 192.168.0.1 is the address of my router on my LAN. I believe the second address is a DNS provided by my ISP.
etc/hosts
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost moebius
::1 localhost.localdomain localhost
etc/rc.conf snippet
HOSTNAME="moebius"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
Last edited by sskeirik (2011-03-14 23:21:19)

Output of 'dig google.com a'
; <<>> DiG 9.7.3 <<>> google.com a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52741
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 10000 IN A 74.125.65.104
;; Query time: 17 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Mon Mar 14 14:09:45 2011
;; MSG SIZE rcvd: 44
Output of 'dig @8.8.8.8 google.com a'
; <<>> DiG 9.7.3 <<>> @8.8.8.8 google.com a
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43373
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 229 IN A 74.125.45.105
google.com. 229 IN A 74.125.45.99
google.com. 229 IN A 74.125.45.103
google.com. 229 IN A 74.125.45.147
google.com. 229 IN A 74.125.45.106
google.com. 229 IN A 74.125.45.104
;; Query time: 74 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Mar 14 14:10:37 2011
;; MSG SIZE rcvd: 124

Linksys WRTP54G DNS issue

I have reviewed and tried HOURS of suggestions on this site regarding WI-FI DNS issue ie. "can't find the server" message. This appears to be Router model problem/resolution. Does anyone know the specific fix to get the ITouch to work with an linksys WRTP54G Router. General comments and fixes are not needed, only the one specific for this router. Thanks.

Don't give up on the iPod Touch. It's one of the most remarkable devices ever invented.
Your router routes IP traffic. That's all you need. Your iPod should work with any router. Somewhere, there a configuration setting that is not right.
There is one other possibility, and that's that your ISP is doing something funny like using a proxy server. Unlikely but possible.
You need to attack this systematically. Like has been suggested, narrow down if it is a connectivity or a DNS issue. If you can get to a site by its IP address, then you have a DNS issue. If you cannot, then it is something set wrong elsewhere.
Possibilities:
- MAC filtering (you have ruled this out)
- Encryption (you have ruled this out)
- Is your router not giving out enough IP addresses? If you set the limit to 2 and you have 3 computers, someone will lose out.
- Is your router correctly picking up its settings from your ISP (DHCP), or have you hardcoded some or all of it? Does your (working) PC have some of the missing bits hardcoded - for example, if your router doesn't have its DNS settings, but your IP settings on the PC have them hardcoded, the PC will work, but the iPod won't - unless of course you hard code them on the iPod as well
- Have you inadvertently coded something into your router like a static route, a filter, , or configured a DMZ that is conflicting with the DHCP address that your iPod is getting?
- Have you (or someone in your house) configured some access restrictions on the router, maybe for another PC in the house, like a child's PC?
If all of this is confusing, or something is really screwed up, you could always start form scratch, as if you just bought the router. There is a way to reset it to factory defaults (I believe holding the hidden reset button for a long time), then set it up correctly for your ISP again, and it should work for all computers, iPods, etc.
There is always the possibility that the Vonage firmware is somehow interfering. Do you use the Vonage features? You could always put in a more standard firmware.
Bottom line, it is far more likely that this is a setting on your router than the fault of the iPod. The iPod is just an every day IP device, and should work with just about everything. Do not give up on the iPod.

Westell 9100EM - DNS issue.

Similar Messages

Maybe you are looking for