Re: Can a bad Etherlink card effect browser ability to access the net?

Brian K wrote:
On 6/6/2009 7:29 AM GlowingBlueMist while holding "Agent 99",
exclaimed:
GlowingBlueMist wrote:

Brian K wrote:

On 5/31/2009 1:45 PM GlowingBlueMist conferred with the ghost of
Faye Wray and said:

JAD wrote:


"Brian K" <brian1951BLOG@xxxxxxxxxxxxx> wrote in message
news:U-2dnUC3A_bMiLzXnZ2dnUVZ_qmdnZ2d@xxxxxxxxxxxxxxxx


On 5/29/2009 12:56 PM JAD conferred with the ghost of Faye Wray
and said:


"Brian K" <brian1951BLOG@xxxxxxxxxxxxx> wrote in message
news:O82dnVTRh_USCoLXnZ2dnUVZ_r2dnZ2d@xxxxxxxxxxxxxxxx



I am really in need of some help. Suddenly, I've lost the
ability to access the Internet with either Mozilla Firefox .x
or IE 8. I've done virus scans, gone to my ISP for hard
codding IP Addresses for gateway IP , Primary DNS and
Secondary DNS IP addresses. I've contacted Microsoft Update
support to see if one of the auto updates caused a problem.
What I am wondering is could my Ethernet Card be the source of
this problem? While I can't access the Internet via my DSL
connection, I can access the net via dial-up. Rather than
list a laundry list of specs which might confuse, I'll
happy to help you help me. I can provide whatever tech
information you might need to help me.


XP?
Traffic lite is 'lit' on the card by the RJ45 cable?
Try repairing the connection (contl panel-network
connections-right click your active connection{is it enabled?}
-properties-repair) Use the home network setup or run
connections setup with in IE tools

That's the wired thing Both Network Connections and Zone Alarm
report the DSL as "Connected". The green and yellow lights are
lit. The Ethernet is a VIA PCI 10/100 mb Fast Ethernet that's on
board. All of the lights on the new modem are lit. The Ethernet
and DSL
lights blink and Zone Alarm blocks the stuff it's supposed to
block. The Zone Alarm Traffic Icon and DSL modems lights blink
even though I am accessing the net via dial-up. I did have
connectivity for a
brief period when the Earthlink Tech
had me switch the connections around on the dsl cable. But
after a Windows Update and reboot connectivity was lost even
though it was reported as connected.


Kill all your firewalls and protection for a fw minutes and see
if that opens the web. It sounds like the days of ole and Norton
firewall blocking everything...maybe ZA has adopted those
characteristics



________
To email me, Edit "blog" from my email address.
Brian M. Kochera "The poor dog is the firmest friend, the
first to welcome the foremost to defend" - Lord Byron
View My Web Page: http://home.earthlink.net/~brian1951


I agree with disabling Zone Alarm for as a test. I seem to
remember way back when I was using it that with a router change
resulting in a different subnet. Zone Alarm would not pass the
traffic as it "thought" it was a new subnet illegally trying to
access the PC. I had to delete the entry that was my local
network in ZA and have it re-learn the local network. I could
have just changed the entry but was too new with the software at
the time. Another thought would be to try one of the Linux Live
CD's as they usually have compatible Ethernet drivers and such. If it
can access the network using Firefox or what ever built in
browser came with the Live Linux CD then you would at least know
that the problem is software related and not the gateway/router
or cables. Puppy Linux can be found at
http://www.puppylinux.com/info.htm and
is easy to use.
Others can be found at the http://www.livecdlist.com/ site. If
you download one of these make sure you choose a Desktop or "Live"
version and not an OS Installation version.




I did disable ZA and no joy. At Earthlink I've been given 4
different sets of DNS IP addresses. None of them worked Using
Ping, I can ping my own IP address and get a reply, duh. I can
ping any website and get a response. But when I ping the default
gateway, all I get is "timed out".

Much as it pains me to say it, a default gateway can be set to
ignore the ping command. Almost never done but it is possible. Here is
a test for you that might identify if the problem is your
providers DSL DNS servers or some other problem. While on Dial-up
open a "Command Prompt" window and issue the command "tracert
www.google.com", minus the quotes. This will show you the route
your computer is using to get to one of the Google servers. The final
line should have the
www.google.com name followed by an IP address in brackets. In my
case it was [209.85.225.147]. With the "Command Prompt" window
still opened issue an "ipconfig /all" command. This will show you
your PC's current IP address, Default Gateway, DHCP server, and DNS
servers (usually two of them). It will also show if your provider
is setup to use a DNS Suffix Search List. Write these values down
for later comparison with your DSL link.
Now switch back over to the DSL connection and kill the dial-up
link. See if your browser can get to the www.google.com web site
using the .com name. If not, try opening a "Command Prompt" window
and issued a "ipconfig /release" followed by an "ipconfig /renew", minus
the
quotes. Then try connecting to the .com address for google. If it
the browser still fails to connect tell it to use the IP address
that your tracert command showed you was Googles. If you now get
that web page then there is indeed a DNS problem somewhere, but we
do not yet know if it's the fault of the ISP or something wrong
within windows. The fact that your computer can use the .com
address to connect while on dial-up usually clears Windows, but that is
not always the case.

I have had DNS problems in the past with Comcast and Qwest and found
a nice freeware program that will allow your computer to use other
DNS servers other than your ISP's. It will try to use the ISP's
first but if that fails it will then try other DNS servers from a
list it maintains. The program is called TreeWalk DNS and can be
found at http://treewalkdns.com . I have not had any DNS problems
after installing the program. For me it just runs as a service in
XP and keeps things going, at least so far...

If all else fails it might help if you post the results of your
ipconfig /all from both the dial-up connection and the DSL
connection. Someone here might see something that is being missed
by you or me.
Good luck.


Another thought. Be sure to try to set your DSL connection up using
DHCP and not a fixed IP. After that works then think about a fixed
IP if you still want one for some reason.

Also if your PC is given a DHCP IP address starting with
169.xx.xx.xx then your PC and the DSL box are not talking together. A 169
address is the default that Ethernet cards default to when
they can not connect to a DHCP server, in your case that should be
your DSL box. You might need to actually log into your DSL box and
verify the DHCP server is turned on and not disabled by mistake.


Earthlink.com Tech services has escalated my issue over to the
engineers dept. they're going to check the server settings for my
account. Also, they may send a field test rep out to my house.

Just out of curiosity, How might I log into my DSL box and verify the
DHCP server is turned on ? Shouldn't I invoke Windows Computer
Management > Services and Applications > Services > DHCP Client and
see if this was disabled first?

Another thing has occurred to me. When I had the old Netopia box, to
avoid paying for another line extension to the phone company, I ran a
15' phone cord, which came with the Netopia, from the jack to the DSL
box. The phone cord that came with the ZyEXL is maybe 4' tops. So,
rather then continuing using the old Netopia phone cord... I am biting
the bullet and putting another extension close to my DSL modem. I'm
not going to tap into the original extension the distance of phone
wire would be doubled from the NID (spelling?). I'm going to run the
wire from the NID or is it NAD and terminate with an extension by the
box.
I was wondering, instead of just using the RED and GREEN cond,
connected to the RED and GREEN terminals, would it provide more
conduction to add the yellow and black cond. too? Or, would that not
work or cause a problem sending the Verizon gods breathing fire upon
my humble self?

Either way a shorter distance from the NID to the DSL box can't hurt.

On the cabling side, do not connect the yellow/black wires to the red/green
ones. It could cause noise and on some home wiring there might even be an
old transformer (to power the dial light on the old princess phones) or a
second phone line connected to them. Those old princess phones are mostly
history but I have seen a few of them around and a few houses where they
were removed but in the basement or crawl space a small transformer was
still supplying voltage to the black and yellow wires.

You need to make sure that you have the small phone filter installed at the
wall jack and plug the phone in the indicated jack and the DSL in the other.
You need to have one filter installed for each phone plugged into the house
unless you have a filter installed at your Telco interface and run a
separate pair of wires from that filter to the DSL box.

With good connections you should not have any problems with cable length
inside your house. I would not worry about the length you are using at this
time.

You should be able to see if your computer is set to use DHCP by opening a
"Command Prompt" window. On an XP machine that can be found by going to
Start|Programs|accessories|Command Prompt and clicking on the Command Prompt
option.
That should open a black window labeled "Command Prompt"
Left click your mouse anywhere inside the black window and type the
following command followed by the enter key.
ipconfig /all

You should wind up with something similar the following in the window.
Windows IP Configuration

Host Name . . . . . . . . . . . . : santa
Primary Dns Suffix . . . . . . :
Node Type . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . : No
WINS Proxy Enabled. . . . : No
DNS Suffix Search List. . . : domain.actdsltmp

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . : domain.actdsltmp
Description . . . . . . . . . . . . : NVIDIA nForce 10/100/1000
Mbps Ethernet
Physical Address. . . . . . . . : 00-1D-92-DA-24-A2
Dhcp Enabled. . . . . . . . .. . : Yes
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . .. . . : 127.0.0.1
192.168.0.1
205.171.3.65
Lease Obtained. . . . . . . . . : Wednesday, June 10, 2009 2:36:17
PM
Lease Expires . . . . . . . . . . : Wednesday, June 17, 2009 2:36:17
PM

As you can see in the above, my computer does have Dhcp Enabled, My
computers IP address is 192.168.0.3, and my Default Gateway is 192.168.0.1
My IP address is being assigned from the router portion of my DSL modem (not
same model as yours). The real world IP address stops internally in the DSL
modem unless you are in the bridged mode, but that is not too common.

As for gaining access to the DSL box, here is a link showing what "should"
be the default IP address of your DSL model according to Earthlink's support
web site.
http://kb.earthlink.net/case.asp?article=157473
It appears to be 192.168.1.1 according to the article. Try pinging that
address, if it answers try to connect to it with your browser.

Most likely you need to be setup as PPPoE and not Bridged, but only your
local tech support knows for sure. This info is quite often supplied with
the setup or activation paper work they send you.

If your PC has DHCP configured then the PC should normally be assigned an IP
address starting with the first 3 groups of numbers for the Default Gateway.
If the info supplied on the support web link is good and your PC has DHCP
then your Default Gateway should be 192.168.1.1 and your PC should have an
IP address of 192.168.1.xxx where xxx is any number between 2 and usually
254.

If your computer is indeed setup to be configured with a Fixed IP (Dhcp
Enabled = No) then you should be able to gain access to the DSL modem but
you will need to write down the IP address your computer presently has and
then change the IP address in the PC to 192.168.1.(2-254). I personally
would use something like 192.168.1.5. Then try use a browser and go to
192.168.1.1.

One last thing, you might want to take your PC and DSL modem physically to
your Telco demark and plug the DSL modem directly into the demark. Yes this
will kill all internal phones on that line while you are doing this but if
the problems go away then you don't need Earthlink to visit, you need your
internal wiring fixed or DSL filter(s) replaced. Yes the filter can go bad
but not too often.

I know, I type too much... Good luck.



.

Relevant Pages

  • Re: Can a bad Etherlink card effect browser ability to access the net?
    ... Primary DNS and Secondary DNS IP ... While I can't access the Internet via my DSL ... Try repairing the connection (contl panel-network ... that might identify if the problem is your providers DSL DNS servers or some ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: Can a bad Etherlink card effect browser ability to access the net?
    ... Primary DNS and Secondary DNS IP ... While I can't access the Internet via my DSL ... Try repairing the connection (contl panel-network ... DNS servers or some other problem. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: Yet another "network cable unplugged" issue (w/DSL)
    ... I have ATT DSL service on two PCs, the main one in my basement office, and secondarily on my son's PC upstairs. ... I should mention that my main PC uses a 2wire 1000HW DSL modem, and the second one connects via HPNA with a 2wire PC Port USB connection. ... The PC Port is properly connected as indicated by its power light, as well as being connected to its phone line, which is in turn connected to the DSL filter which is plugged into the wall. ... I suspect that the ATT tech replaced your original 2wire filter that went between your 2wire gateway and the wall jack with a standard DSL filter. ...
    (microsoft.public.windowsxp.network_web)
  • Re: OT udp port 138 BROWSER traffic
    ... >> dsl issues extend from at least June, and I could say more, but won't. ... >> issues that are interfering with my connection at their end. ... >> happening is the router is simply ignoring my traffic, ... it was a BAD filter that was not doing it's job. ...
    (comp.os.linux.security)
  • Re: Firefox browser?
    ... DNS or Proxy problem. ... >> I set it to automatically detect the connection. ... Where I am located the DSL connections are all pppoe so I ...
    (Fedora)