Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[FurryNutz]

I'm posting this for Bipolar Bear since he can't seem to keep connected. Anyone using ATT DSL by chance seeing this issue?

"I have recently changed out my motorola modem for a D-link 2320B and it has been running fine. I am using the D-link DGL4500 router. I am sure all of my gaming, DHCP, Ports and gamefuel are all correct. I have contacted my ISP numerous times and they will not give any advice on products other than what they offer.
While on the phone with my ISP yesterday I had three dis-connects while connected LAN directly to the modem they offer. They have agreed to send a tech out the following week. Although last time I received a work order number, a date, and a time a tech would be out. I received a phone call approx. 30minutes after I had ended the phone conversation, (of course this was a recording) stating "they didn't detect a problem with our lines"
11/28/09 I researched some more about your modem, and router specifications. Again i set the router up accordingly. I was able to play games on xbox live for close to 6 hrs. As of this morning 11/29/09 I have had numerous dis-connects as shown in the log below. I haven't been on xbox live, I am simply "surfing the web" there is not that big of a demand for a high-speed connection, and the computer I am using now is the only device on the connection.
I would like to know if this appears to be a ISP issue, a modem issue, or a router issue?
I would also like to know if there is any type of firmware update i need to install on my modem? I am currently running the build 3 on my router.

Obtained IP Address using DHCP. IP address is 70.142.58.96 [INFO] Sun Nov 29 12:43:24 2009 Lost lease on IP Address [INFO] Sun Nov 29 12:43:19 2009 Dropped packet from 192.168.1.2 to 255.255.255.255 (IP protocol 17) as unable to create new session [INFO] Sun Nov 29 12:43:19 2009 WAN interface speed measurement aborted as they did not converge [INFO] Sun Nov 29 12:43:10 2009 Estimating speed of WAN interface [INFO] Sun Nov 29 12:43:09 2009 Obtained IP Address using DHCP. IP address is 192.168.1.2 [INFO] Sun Nov 29 12:42:59 2009 Bringing up WAN using DHCP
Lost lease on IP Address [INFO] Sun Nov 29 12:31:52 2009 Dropped packet from 192.168.1.2 to 255.255.255.255 (IP protocol 17) as unable to create new session [INFO] Sun Nov 29 12:31:52 2009 WAN interface speed measurement aborted as they did not converge [INFO] Sun Nov 29 12:31:40 2009 Estimating speed of WAN interface [INFO] Sun Nov 29 12:31:39 2009 Obtained IP Address using DHCP. IP address is 192.168.1.2 [INFO] Sun Nov 29 12:31:37 2009 Lost lease on IP Address
Lost lease on IP Address [INFO] Sun Nov 29 12:08:41 2009 Dropped packet from 192.168.1.2 to 255.255.255.255 (IP protocol 17) as unable to create new session [INFO] Sun Nov 29 12:08:41 2009 WAN interface speed measurement aborted as they did not converge [INFO] Sun Nov 29 12:08:29 2009 Estimating speed of WAN interface [INFO] Sun Nov 29 12:08:28 2009 Obtained IP Address using DHCP. IP address is 192.168.1.2 [INFO] Sun Nov 29 12:08:24 2009 Lost lease on IP Address
Lost lease on IP Address [INFO] Sun Nov 29 11:33:26 2009 Unable to find DNS record for firmware upgrade server wrpd.dlink.com.tw [INFO] Sun Nov 29 11:33:08 2009 WAN interface speed measurement aborted as they did not converge [INFO] Sun Nov 29 11:32:56 2009 Estimating speed of WAN interface [INFO] Sun Nov 29 11:32:55 2009 Obtained IP Address using DHCP. IP address is 192.168.1.2 [INFO] Sun Nov 29 11:32:52 2009 Lost lease on IP Address
INFO] Sun Nov 29 13:04:33 2009 Lost lease on IP Address [INFO] Sun Nov 29 13:03:02 2009 Estimating speed of WAN interface [INFO] Sun Nov 29 13:03:01 2009 Obtained IP Address using DHCP. IP address is 64.149.39.91 [INFO] Sun Nov 29 13:02:58 2009 Lost lease on IP Address."


Side note, I Furrynutz, have been helping Bear setup his router with lean settings as not to introduce any other issues. And to confirm that we did play last night on XBL with out any disconnect. I feel this is a DSL ISP issue.

[BIPOLAR BEAR]

The AT&T tech came to my house today on a service call. I explained to him that over the past few months we had been experiencing disconnect issues. When the phone would ring or just random disconnects on xbl. That I had been trying to eliminate any firmware issues on my router. Went as far as to install another line in my house and had nothing but the modem on it. BLAH BLAH BLAH. It goes on forever.  With technical issues, things i have tried, and resetting the router to default and starting from scratch.
The tech informed me that "we shouldn't have been sold the elite service", "it is basically for people who live inside of 7000ft. from the office" "your house is roughly 9000ft." So he ran some standard tests and installed a filter/switch that would block the phone signal from coming over the line I am using for DSL. He came inside and ran some more tests and my signal is the highest it has ever been. He showed me on his laptop where at times we were only up to 70% efficiency on our bandwidth. Our connection now is over what they say is allowed. With 98-99% efficiency. Shortly after he left I experienced another disconnect. With a 192.x.x.2 ip in my router log. I am wondering where this comes from since I am on a public IP and my paremeters in my router are not set to the 192.x.x.x Before the tech came out I was noticing this on my router log along with an (IP protocol 17) along with my disconnects...any IDEAS, thoughts, recommendations?

[Tyrone Biggums]

BIPOLAR BEAR,

If your phone line is the same as your DSL connection then yeah A splitter with a filter would help.

As for your disconnects:
When you plug a PC directly into the modem what IP address are you getting?
Do you have static IP (single or a block)?
Does it require PPPoE?

Holla!

[Squirrel2]

Regarding a phone line with DSL:

You're SUPPOSED to have a DSL Filter on the lines that go to everything but the DSL Modem. It's no wonder you had issues before.

[BIPOLAR BEAR]

TYRONE,

We have moved the Static ip to a PPPoE setting as per AT&T instructions. Before I was unable to obtain a "public" ip. Which showed up as a "strict NAT" when trying to sign into xbl. The ip's The router is obtaining when it is finally able to reconnect are anywhere from  IE. 71.x.x.x to 64.x.x.x.x.

I think some misunderstood filter placement, filters have been installed since "day 1" on the phone jacks.
The filter the tech installed is inside the junction box on the side of the house. It stops the phone signal from coming over the DSL line before it ever reaches the inside of the house.

[Tyrone Biggums]

the PPPoE settings are entered in the Modem or the Router?

If you're pulling a public IP on the router you should be good to go. are you still seeing disconnects?

[BIPOLAR BEAR]

The PPPoE settings are on the modem, as per the AT&T techs instructions. If I set the PPPoE on the router it creates a conflict and the router cannot get to the internet. I have another option of moving the modem to "transparent" and setting PPPoE on the router. I know how to do this, I am just leaving it as an option.
Yes, I am still seeing disconnects while pulling a public IP. We had 3 xboxes on line lastnight and all 3 got disconnected at the same time, 2 are "hard lined" and 1 is on wireless. It is almost predictable when a disconnect is coming, due to "game play". It is almost like lag, although we are not showing any. Or maybe a loss of synchronization....Then the disconnect comes. The xboxes won't sign back into live without doing a "test xbox live connection", or power cycling the modem or router and sometimes both. So I pull up my router's logs and review. Everytime I see....an IP protocol 17 error, a 192.x.x.2 ip address, and up link wasn't established "as they did not converge"
Since my old modem's IP provided by my ISP ended in .2. I am going to move my modem IP to that IP, and go from there. Maybe it will fix this issue but, I have my doubts..LOL

[BIPOLAR BEAR]

I am going to try this first...before I change my IP on my modem. I am going to add a web filter and deny that 192.x.x2 address.. HMMMMMMMMMMM

[Tyrone Biggums]

If you set the PPPoE settings on the modem the modem needs to be in bridge mode with the LAn DHCP settings (Modem) turned off and on the router you enter in the static IP provided by your ISP.

[BIPOLAR BEAR]

Yeah I got it. Just trying other things before I make the modem transparent...So far with the web filtering I have maintained a connection for over 14hrs now. The firewall has been very active..lol

[djzoey]

Hows that Router and DSL modem working?

[BIPOLAR BEAR]

My modem was already set to a bridge. So after My last phone conversation with my ISP, they were still seeing my disconnection issues on their end but, could not explain why this was happening. So for my last attempt to resolve these issues I moved my modem to a "transparent" bridge and moved my PPoE settings to modem. Although I am still having some "lost lease on IP" issues, I manage to maintain my Public IP for days. (far better than losing a ip 6 times in an hour). I was reluctant to do this because when you move the modem to this type of bridge, you lose access to your admin modem settings page. You are unable to check the modem logs, make changes ect. It's not really an issue unless this didn't work..lol

Tyrone, I appreciate your help. My ISP didn't give me an Public IP to use. I can obtain a 192.x.x.x IP this is a private IP would be fine but, with playing on Xbox live you receive Strict NAT, and Firewall issues from xbl servers. In order to avoid this I have to let my modem obtain a public IP. To my knowledge my ISP does not issue public IPs, or if they did they would charge me for the use of one. I don't really care to do that when I should be able to obtain a lease on one for free that should last anywhere from 2 weeks to a month. This comes from one of their level 2 techs. Again, thank you.

[BIPOLAR BEAR]

The modem, router and dsl seem to be fine. I had the same IP for 15 days. We did have a little snow storm and some weather issues, so when I checked today I have only had my public ip for 6 days almost 7. I will continue to monitor it but, I am not concerned with my connection issues at this time. It has improved allot since I first started researching, changing modem and router settings.....and many many frustrating conversations on the phone with ISP. LOL

[FurryNutz]

Good to hear, now maybe I can do something else with my life beside give tech support to you all the time. 
Good to hear from you and glad you love DSL. LOL

[Corroded]

OK.. so you aregood bear?

IF it is working, or not, my standard recommendation is to turn down or off the logging.  It was,by itself, causing my router to go unresponsive.