Need Router Help - Cant Connect To The Internet

[Jeff]

I am configuring a new Linksys wireless router. All is going well until the
router tries to connect to the internet. The "Internet" light is on but I
can't connect to any web site.

I have seen some comments here before on this subject, something about a
subnet setting change, but of course I wasn't paying attention then. Can
anyone offer any help, subnet setting or otherwise? If it is a subnet
setting, where is this setting changed? In the router? In the connected
computers?

Jeff

[Disco]

dsl?

subnet should be 255.255.255.0

i believe it sets itself as 255.255.255.255 for some reason

if u are roadrunner then you need to clone the mac address of the card
registered with rogers

[Jeff]

Yes. it is DSL, the non-PPPoE version

The subnet mask in the router defaults to 255.255.255.0

Is it the other way around - should I set it to 255.255.255.255?

Jeff

"Disco" <jgreen_N...@roadrunner.nf.net> wrote in message
news:c2b7f6$3v5$1...@nntp-stjh-01-01.rogers.nf.net...

[Disco]

hmm thats right

can u go into the status section and see what your WAN settings are? are u
getting an ip at all?

a 142.whatever aliant one? (i think its 142 lol)

[Jeff]

I am getting an IP address from Aliant (yes, it is 142...). The DNS, IP
address, subnet mask, on the router status page are the same as when I see
in network properties when I am directly connected to the modem.. So the
router is connecting to the network and retrieving an IP address, and the PC
is connecting to the router and getting an IP address from the router.

All setting seem fine, I am getting the right IP address, and the "internet"
on the router light is on, but yet I cannot connect to any site, and I can't
ping anything. When I remove the router and connect directly to the modem,
I connect and can see web pages immediately.

HELP!

[John Ryan]

erm common sense here people,

you need to call aliant and get them to flush your mac address, as you can
see its set to use the one from the nic in your machine not the one in your
router.

get them to flush it and unplug yer router than plug it back in (resetting
without losing whats programmed into it).

that will fix your problem.

--chris

"Jeff" <jck...@nf.sympatico.ca> wrote in message
news:Uic2c.111085$IF6.3...@ursa-nb00s0.nbnet.nb.ca...

[Monty]

but, aliant doesn't bind the connection to a mac address like rogers.
if that were the case, all you'd need to do is use the router settings
to clone the mac of your nic. if the wan has a subnet of x.x.x.0, and
you're getting a 142 ip on non pppoe, then you should be fine.

usually this has to be set to static though as the default on the wan
port is x.x.x.255 when your settings are set to dhcp. make sure that
the wan port is the one with the x.x.x.0 subnet. the dhcp server on
the router will look after the lan port settings. i'd confirm this
before proceeding further to make sure we're on the same page.

[Disco]

is your router setup for dhcp and your machine set to use dhcp? and not
manually entered?

do u have any software firewalls running?

have u tried a release/renew on your machine (repair in xp)?

[Jeff]

In response to the questions asked:

- I know that Aliant does not bind the IP address to the MAC address. Even
so, I have cloned the PC MAC address into the router and checked that is
correct in the router.

- I am running DHCP, and the router is set that way. I have tried DHCP,
static IP, auto and manual subnet mask settings (every combination of
255.255.255.255 and 255.255.255.0) for the router and the PC.

- I am running Windows XP pro, no firewall software (never had it).

- Tried release and renew, the router IP address is released and renewed
properly.

- I have another PC (I was using a hub, now upgrading to a router). I
disconnected the other PC before I opened the router box. I did connect the
other PC alone to ensure that some odd setting in the first PC was causing
the problem. Same results with the other PC.

I continue to get an IP address (142...), subnet mask (255.255.255.255),
and correct DNS serves from Aliant on the router status page, and correct
router-generated IP and subnet on the PC. I can ping the router but
nothing on the internet. When I ping a server name (e.g. abc.com), I get a
timeout on the DNS server. When I ping an IP address, I get a response from
my router - can't reach address. I can ping my router fine.

I have tried every other combination of settings I and the Linksys tech can
think of, tried several router resets, and get the same result over and over
again.

Any other suggestions?

Jeff

"Disco" <jgreen_N...@roadrunner.nf.net> wrote in message

news:c2cirf$ep1$1...@nntp-stjh-01-01.rogers.nf.net...

[Peter]

XP has it's own built in firewall, try turning that off and see what
happens. Just another suggestion.
Peter

[Steve]

dns?
can you ping the external address (142) from an internal pc? (198)
if yes,
manually enter dns server entries on each pc....see if that does anything.
dns forwarding can get easily screwed up now because alot of the ISP servers
wont allow your router to register itself as a DNS forwarder.

"Jeff" <jck...@nf.sympatico.ca> wrote in message

news:P2l2c.111194$IF6.3...@ursa-nb00s0.nbnet.nb.ca...

[Jeff]

Yes, I can ping the 142 address of the router (but nothing past the router).
I had already entered the DNS servers manually - did not help.

The firewall in XP has been turned off. That didn't help either.

Keep the suggestions coming - all help is appreciated.

Jeff

"Steve" <customcomp...@roadrunner.nf.net> wrote in message
news:c2cq7p$h02$1...@nntp-stjh-01-01.rogers.nf.net...

[Disco]

i know for a fact u will manually have to enter in your static ip info (dns
etc..) into the router and change the subnet to 255.255.255.0)

set the router to use dhcp and set each machine to automatically obtain an
ip from the router (all these are the default settings)

but after that everything should work automatically

ive seen this before with people who enter in their pppoe info wrong or
didnt disable their pppoe software on their machines... but since u dont use
pppoe this cant apply

this is strange

[Steve]

try this.....see if its dns oriented or not.
ping to 142 from an internal pc means, you're online, just not getting
pages, or host information resolved.
when you ping yahoo.ca, an ip appears in brackets next to it........ping the
actual ip from an internal pc and see if it replies.
try the same thing with google.ca and the ip following it.
if you can ping 142, you should be able to ping beyond it, the packet has
already been routed off your network, the gateway for 142 is responsible for
it now.
are the manual dns entries you used real dns servers, or the router ip?

"Jeff" <jck...@nf.sympatico.ca> wrote in message

news:zEm2c.111247$IF6.3...@ursa-nb00s0.nbnet.nb.ca...

[Jeff]

In response to Steve's points:

When connected to the router, I can ping my PC (192-168.1.100), I can ping
the router (192.168.1.1), and I can ping the router at the address the
router has received from the network (142...). This seems to mean that a)
the router has some connectivity to world to get the IP address in the first
place and b) my PC is communicating with the router.

I can not ping anything else, and I can't see any web sites. I cannot ping
the "default gateway" (142...) as shown on the status page of my router.
Pings to a domain name (e.g. yahoo.com) result in a timeout and the error
"Ping request could not fine the host...". Pings to an IP address result in
a reply from my router "Destination not reachable".

Although I can ping my router and my router gets an IP address from Aliant,
I cannot connect to anything other than my router.

The DNS entries that the router gets are real. I have tried entering the
same ones manually, to the PC and to the router. No change. The DNS hosts
are: 142.163.127.61 and 209.128.1.4

I agree that, if I can ping 142, I should be able to ping beyond it. I
can't, and that is the summary of the problem.

This is now entering the frustration stage.

Any more suggestions? Anyone?

"Steve" <customcomp...@roadrunner.nf.net> wrote in message

news:c2d0oi$j31$1...@nntp-stjh-01-01.rogers.nf.net...

[Disco]

write down the WAN (aliant) info that your router receives via dhcp.

IP
SUBNET
GATEWAY
DNS SERVERS

set your router to use a static ip and enter the above in as your
information

**BUT** change your subnet mask from 255.255.255.255 to 255.255.255.0

then...

make sure DHCP (NOT THE WAN PART.. THE LAN PART) is enabled on your router

then on each machine connected to the router set them to obtain their ip's
etc..automatically using dhcp

DO NOT have any dns/ip/gateway/wins info etc.. entered in !!

then turn off your pc(s) then unplug your router.. and then your modem.

turn on your modem first... once all the status crap is done plug in your
router... when all of its crap is done turn on your machine

[PKS]

Follow Disco's instructions he is correct! Its a common problem with the
Warp service.

Paul

"Disco" <jgreen_N...@roadrunner.nf.net> wrote in message

news:c2dc5b$mrg$1...@nntp-stjh-01-01.rogers.nf.net...

[Jeff]

The problem is now solved, thanks to Disco's detailed instructions.

Thanks Disco!

"Disco" <jgreen_N...@roadrunner.nf.net> wrote in message

news:c2dc5b$mrg$1...@nntp-stjh-01-01.rogers.nf.net...

[Steve]

"Jeff" <jck...@nf.sympatico.ca> wrote in message

news:Tww2c.111617$IF6.3...@ursa-nb00s0.nbnet.nb.ca...