• October 12, 2024, 02:45:26 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 [2]

Author Topic: ATT DSL - dlink 2320b and 4500 disconection issues (RESOLVED)  (Read 27259 times)

BIPOLAR BEAR

  • Level 1 Member
  • *
  • Posts: 19
Re: ATT DSL - dlink 2320b and 4500 disconection issues
« Reply #15 on: December 30, 2009, 02:19:47 PM »

Yes I am calling it good for now. Although I am not completely satisfied with my ISP, I don't believe I can question my Dlink equipment anymore. If I have any further issues I will consider turning my log off, even though I have never felt it to be an issue since alot of my research and diagnosis comes from reviewing my logs. Without them I couldn't of shown the field tech they sent to my house what I was seeing.
Logged

Corroded

  • Level 2 Member
  • **
  • Posts: 49
Re: ATT DSL - dlink 2320b and 4500 disconection issues
« Reply #16 on: December 30, 2009, 08:37:14 PM »

I agree with the need for the logs, it was just that they were causing my router on fw1.2x to become non-responsive.

I have not had a need to touch the thing with over 20 days uptime on it. a first with the 1.2xfw.
Logged

Dalmo

  • Level 2 Member
  • **
  • Posts: 33
Re: ATT DSL - dlink 2320b and 4500 disconection issues
« Reply #17 on: December 30, 2009, 10:04:39 PM »

I agree with the need for the logs, it was just that they were causing my router on fw1.2x to become non-responsive.

I have not had a need to touch the thing with over 20 days uptime on it. a first with the 1.2xfw.

so if the logs are the issue's with this Router I hope d-link will have an update very very soon and I mean very soon not 6 mth from now I 'm ready to take this router back to where I purchase and never by a d-link again


This Router has been a nightmare since I purchased



 :(
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: ATT DSL - dlink 2320b and 4500 disconection issues
« Reply #18 on: December 30, 2009, 10:12:31 PM »

What version of FW are you running? I'm running Beta 08 and all my loggs are on. No issues accept for wireless drops.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Dalmo

  • Level 2 Member
  • **
  • Posts: 33
Re: ATT DSL - dlink 2320b and 4500 disconection issues
« Reply #19 on: December 31, 2009, 08:19:34 AM »

What version of FW are you running? I'm running Beta 08 and all my loggs are on. No issues accept for wireless drops.


running 08




 ::)
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: ATT DSL - dlink 2320b and 4500 disconection issues
« Reply #20 on: December 31, 2009, 11:00:41 AM »

So what kinda of issues are you seeing with ur 4500? Let us know the specifics. Maybe we can help. Overall the 4500 is doing pretty good here. There could be some other issues at hand that might make the 4500 look like it's the culprit however isn't. Just need to walk thru some steps and see if theres a problem and try to fix it.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

BIPOLAR BEAR

  • Level 1 Member
  • *
  • Posts: 19
Re: ATT DSL - dlink 2320b and 4500 disconection issues (RESOLVED)
« Reply #21 on: February 13, 2010, 01:56:17 PM »

I am going to try and keep this shorter than the actual battle I have had with figuring out my connection problems. Establishing weather or not it was a Firmware issue, or an ISP issue. The 4500 seems to have a bad reputation for various issues. I have never really held this product responsible.
  After I finally was able to get my ISP to send the tech out the first time and he installed the filter on the side of the house, diverting the DSL signal to an independent line for internet and keeping the phone signal directed to various phone lines throughout the house. My connection was much better, and I was well over the ISP's maximum Mbps. I was still unable to hold a public IP for more than 3 weeks. Without some random disconnection and then the modem would pull another public IP. I might have that IP for 1 week or 2 sometimes 3. Until sometime during the first week in February 2010. When I noticed that while I tried to connect to xbl, the modem "DSL" light would go off. Of course I couldn't connect to xbl, since this meant I had lost my DSL connection.
  Several attempts at this and I could finally connect. Again we are back to the same problem. Random DSL signal loss. Remember the tech whole came to the house initially told me we should have never been sold that "package" because we were at least 7000ft from their office. I still had my old case number where I could call my ISP and go directly to tier 2. Upon calling them I explained that I had recently started experiencing the same connection issues that I had a few months ago. I was told that they were seeing allot of "noise on their end, so they did another rip/rebuild. That didn't help. So the next day I called and again went over the case history with another tech> They agreed to send me another field tech. Continued>>>>>>>
Logged

BIPOLAR BEAR

  • Level 1 Member
  • *
  • Posts: 19
Re: ATT DSL - dlink 2320b and 4500 disconection issues (RESOLVED)
« Reply #22 on: February 13, 2010, 02:29:29 PM »

>>>> I was told by the ISP tech, they would send another field tech. I was told that I would probably receive a recording before the tech was sent out. I told the phone tech the recording I would receive would state that "they had tested my line and there was not a problem". The phone tech then replied, "if this happens, call this number and give them this field ticket job number, your lines are not fine". "I can see the issues here." The following day I called tier 2 and gave them the job #. I had a tech by that evening. He checked our lines and told me that we had dropped to 1/2 of our package speed, and that was intermittent. Again I heard you guys should have never been sold this package...LOLOLOL! He also told me that he figured 9000ft from where our DSL signal was coming from. He said the short run of line from our house, "pole to pole" had been giving people problems and that he had switched the house next door to a newer line they had installed. So he did the same for ours. It only brought us up about .5 Mbps. I then told him that the tech I had spoken with a few months back told me that they had installed a new hub just about a block or block and 1/2 away from our house but we would not be connected to it. He then told me he would put in a work order and see that we were put on it. He couldn't see why were weren't on it already. Once the work order is put into place it takes around 2 days for completion. So last week, shortly after 9a.m. The other field tech called and stated that he had completed the work order and we were on the new hub, he wanted to check our connection. While talking to him he said, you guys should have never been sold that package. LOLOLOL! He figured our distance to be over 13,000ft. If you count the way the cables run from the office. Straight maybe 9,000. Far from the 6,000ft recommended limit. To bring this to a close, I am on a new hub with fiber optic running to and from the location, excluding the 2 wire copper lines running to the house. The random connection loss has never been the 4500, it has been the random fluctuations in DSL signal strength and poor lines on the ISP's end. Not to mention a connection speed we should have never been sold due to distance. Maybe ISP providers need to pay more attention to QOS instead of $!?? This has been longer than I wanted, keep in mind this has taken over 8 months to resolve.
Logged
Pages: 1 [2]