Cycoz
@rr.com
| reply to YeOldeStonecat
Re: [General] BEFSX41 / Siemens 4100 DSL Modem problem and solut
YeOldeStonecat, You summed it up as the right way to do it, BUT as graffixjones was mentioning; is that there seems to be a problem with the 4100 and befsx41 router specifically. Im sure what you posted works 99 percent of the time with other routers.
I to have spent 6 hours, 2 calls to the sbc guy who installed the dsl, 2 calls to the sbc tech support, and 1 call to linksys to try and solve this issue to no avail I might add.
Leaving he modem in default -allows 1 pc to get online perfectly. If you install the linksys router behind it, the router receives the WAN ip and gateway, but has the modems ip as the DNS numbers(192.168.0.1).
I put the modem in bridge mode, with router behind it, set router up to PPPoe with login, pass, keep active, and put in sbcglobal.net in the domain name. Like graffixjones mentioned with this setup, if your lucky, you may get to one or two sites, then nothing. Talk about frustrating.
I put the modem in "in computer" mode and it was pretty much the same as in bridge mode. The funny thing is, is I could reach google, and search it, searches came up, but then could not access a single website. I could ping any ip or url through the cmd propt.
Im going to try what graffixjones did with the private ip setting and see if this works. I don't recall seeing the setting private ip tho, im going by memory here. Is this a seperate setting? What do you set the modem to default, in computer or bridge? In saying set modem to negotiate pppoe is this the first setting on the modem connection?
thanx |
|
efrem
join:2002-04-03
Westport, CT
|
Have encountered the same problem here, too.
Speedstream 4100 just decides to no longer communicate with the router. Have tried other routers, both Linksys and non-Linksys, so this is not a BEFSX41 issue.
As reported by previous posters, this is an intermittent problem to the extent that we can occasionally get it all up and running for a few minutes, but once the LAN side of the 4100 locks up we are back to trying to find some mystical combo of device startup order and dumb luck.
Have flashed the firmware on the 4100 from .48 to .53, have tried all iterations of PPPoE location on modem/router, public vs private IP, etc................
Have even added static route in the router, to modem, and the problem still recurs.
The 4100's WAN side certainly appears to hold the connection to SBC/ATT, but the LAN interface just dies. Can't even ping the 192.168.0.1.
SBC/ATT tech supp has not been helpful at all. They have refused requests to swap for another modem.
Have run out of ideas and patience for SBC/ATT, and am about to suggest switching to cable.
Any ideas? This whole thread probably belongs in an SBC forum, according to our experience.
Thanks. |
|
YeOldeStonecat
join:2001-03-19
Groton, CT
| reply to Cycoz
said by Cycoz :
YeOldeStonecat, You summed it up as the right way to do it, BUT as graffixjones was mentioning; is that there seems to be a problem with the 4100 and befsx41 router specifically. Im sure what you posted works 99 percent of the time with other routers.
The method I use always worked for me in the past...doing another one today, another one next week...//shrug |
|
Mountaineer1
Big WVU Fan
Premium,MVM
join:2002-01-12
Universe
 ·AT&T Yahoo
| said by YeOldeStonecat  :The method I use always worked for me in the past...doing another one today, another one next week...//shrug Which method is that,by the way?
--
I'm just a Material Handling Tech.If it's too heavy,get a Forklift. |
|
YeOldeStonecat
join:2001-03-19
Groton, CT
| said by Mountaineer1 :said by YeOldeStonecat :The method I use always worked for me in the past...doing another one today, another one next week...//shrug Which method is that,by the way? My reply up 6 posts....bridge the modem, let the router be the only NAT device, and the router does PPPoE if required. |
|
d_l
Barsoom
Premium,MVM
join:2002-12-08
Reno, NV
| Sorry, I'll have to disagree with you on that one. Bridging prevents fast access to the modem's GUI. If you have a stable DSL line, that you don't need line stats or can get them at your leisure by recabling, then it would be ok, but when it is absolutely necessary to catch a transient DSL problem or run a continuous scan on line conditions, then bridging won't cut it. |
|
YeOldeStonecat
join:2001-03-19
Groton, CT
| said by d_l :Sorry, I'll have to disagree with you on that one. Bridging prevents fast access to the modem's GUI. How does it prevent fast access to the modems GUI? |
|
