Re: No one answered my question?

"mcguirem3m" <mcguirem3m@xxxxxxxxxxxxx> wrote in
news:JffPh.12378$5i7.11135@xxxxxxxxxxxxxxxxxxxxxx:


"DanS" <t.h.i.s.n.t.h.a.t@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns9903AE77C3BF5thisnthatadelphianet@xxxxxxxxxxxxxxxxx
"mcguirem3m" <mcguirem3m@xxxxxxxxxxxxx> wrote in
news:tRdPh.12308$5i7.11085@xxxxxxxxxxxxxxxxxxxxxx:

I can get connected and have a 192... IP address using IPconfig/all
but I can't ping anything therefore I'm not "really" connected. I'm
using a Linksys WRT54G Router and Gigabyte desktop wlan pci lan
cards in the workstation. It sees the SSID fine and gets a 24 to
36mbps connection but doesn't connect to the Internet nor can I ping
anything. What am I missing? I'm sure it's something I missed as
I'm just getting started with wireless connectivity. Any help from
you Gurus would be appreciated. Thanks

What are you trying to ping ? How are you configuring the access
point ?

I went through the 'setup' that comes with Linksys and entered the
data it ask for regarding SSID , the Login ID/PW for the DSL and then
the Passphrase. That's all that it ask me to do. I can access the
internet on the machine that is directly connected to the router with
an ethernet cable but not through the workstation downstairs that has
a Gigabyte Turbo 802.11 g/b wireless lan card. It detects the router
just fine with the right SSID and ask for the passphrase and I
carefully enter that and it gets connected at 24 to 36 mbps. But I
try to ping "anything" Amazon, an address and if I type it in wrong
it says I have the wrong name but with an IP address it comes back as
with all tries and returns 4 tries with no returns after 4 attempts.
Does that help?

Yes, I should have been a little more detailed.

1. You are trying to ping an internet address.

and 2. Can you access the rtr configuration over the wireless ?

If you can access the rtr page on the wireless, it may be a DNS issue. If
#2 is true, then you should be able to ping the rtr and anything else
connected to the network.

At that point, first thing to look at is a proper DNS setting in the
wireless PC. Try pinging 24.48.33.2, a direct internet address, which
doesn't rely on DNS.

ALL communications is done withe the IP address. When you type in
yahoo.com, your PC contacts the DNS server listed to ask for an IP
address of yahoo.com. It sends the address back to your PC, and then your
PC goes on and contact yahoo via its IP address. Pinging 24.48.33.2 take
DNS out of the loop. If that goes thru, probably DNS issue. This is in
the TCP/IP configuration of the PC.

Martin mentioned that it is usually set to the rtr IP, but if that fails,
the 24.48.33.2 address is a DNS server you can try out. I have seen rtr's
that didn't forward DNS properly.



.

Relevant Pages

  • Re: winsock error
    ... Ping sends 3 packets of data to a destination IP (or ... then my internet connection worked... ... wireless its ... Winsock and reboot), I would guess the next thing to check is the ...
    (microsoft.public.windowsxp.general)
  • Re: Primary DNS Suffix is blank
    ... " Mine is just a standalone machine. ... What DNS setting are you using? ... Ethernet adapter Local Area Connection: ... Ping statistics for 204.127.202.10: ...
    (microsoft.public.win2000.dns)
  • Re: Cant access broadband
    ... isn't working very well, ping it and look at the responses, if it varies ... from when it's not bad then it could point to a connection issue. ... be mitigated by a DNS caching/proxy problem. ... Not necessarily - could still be a DNS issue, where maybe invalid responses ...
    (microsoft.public.windowsxp.network_web)
  • Re: Problem on starting Wireless TCP communication from server
    ... The settings of the wireless adapter in the device ... the wireless connection is almost always ... I've ignored your code completely and will just address trying to get ping ... Dim client As Socket = CType ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: pppd daemon
    ... Yeah I knew I left ping on too long..I wasn't sure if it exited on its ... your connection is indeed working but you have no DNS. ... > which confirmed that you are indeed receiving the IPs of the DNS ... > complexity which could have more devastating effects if you're root. ...
    (Debian-User)