Here's the situation, hopefully this explanation is clear:
cable modem --> linksys 4port router (w/ one pc attached) --> dlink 4port lan router / WAP (TRYING to connect my laptop and roommates' computers w/ wireless nics to this)
I can access internet fine from the pc connected to the linksys (this linksys is set as a 'gateway' in the configuration). from my laptop, connected by cat5 into a WAP LAN port, I can pull an IP, ping outside IP ADDRESSES, and ping the WAP. I CANNOT ping outside hostnames, nor can I tracert to an IP addy past the linksys -- it times out after the WAP. I have alternated between having the WAP w/ a dynamic IP (pulled presumably from the linksys' dhcp) and setting it statically as the first IP in the dhcp range of the linksys; I think dynamic is the correct setting? either way, same results.
I just updated all of the firmware on the linksys (NR041), and WAP (DLink MA401).
One thing I did notice (which my co-worker suggested I look it) is that when trying to ping hostnames from my laptop, under ipconfig /all, my dns servers were listed as the WAP's IP. I assume these servers should be the same as listed in the linksys, which is to say Comcast's (ISP) dns servers, so I went in and assigned them manually. I was thinking/hoping this might resolve the problem with pinging hostnames, but no dice. And that still wouldn't explain why I can't tracert and ipaddy past the linksys. Any ideas? I was thinking it must be something with the built-in firewalls/filtering, but these appear to be allowing everythig through by default. I am stumped and frustrated. I plan to mess around more with the filtering tomorrow, but for now, I'm burnt out.......
If you finished this, thanks for reading it all. If you understood it,e ven better. If you can help, that would be incredible.
TIA,
Bob
			
			cable modem --> linksys 4port router (w/ one pc attached) --> dlink 4port lan router / WAP (TRYING to connect my laptop and roommates' computers w/ wireless nics to this)
I can access internet fine from the pc connected to the linksys (this linksys is set as a 'gateway' in the configuration). from my laptop, connected by cat5 into a WAP LAN port, I can pull an IP, ping outside IP ADDRESSES, and ping the WAP. I CANNOT ping outside hostnames, nor can I tracert to an IP addy past the linksys -- it times out after the WAP. I have alternated between having the WAP w/ a dynamic IP (pulled presumably from the linksys' dhcp) and setting it statically as the first IP in the dhcp range of the linksys; I think dynamic is the correct setting? either way, same results.
I just updated all of the firmware on the linksys (NR041), and WAP (DLink MA401).
One thing I did notice (which my co-worker suggested I look it) is that when trying to ping hostnames from my laptop, under ipconfig /all, my dns servers were listed as the WAP's IP. I assume these servers should be the same as listed in the linksys, which is to say Comcast's (ISP) dns servers, so I went in and assigned them manually. I was thinking/hoping this might resolve the problem with pinging hostnames, but no dice. And that still wouldn't explain why I can't tracert and ipaddy past the linksys. Any ideas? I was thinking it must be something with the built-in firewalls/filtering, but these appear to be allowing everythig through by default. I am stumped and frustrated. I plan to mess around more with the filtering tomorrow, but for now, I'm burnt out.......
If you finished this, thanks for reading it all. If you understood it,e ven better. If you can help, that would be incredible.
TIA,
Bob
 
				
		 
			 
 
		 
 
		 
 
		 
 
		 
 
		
 Facebook
Facebook Twitter
Twitter