| 5360 wan port issues? (prob interfacing w/routers) Greetings,
I'm just looking for any information regarding the 5360 that might help me better understand the problem I'm experiencing.
I got Ameritech DSL last week. It came with the 5360. When connected to a single PC, I've had no problems with it. (works fine) However when connected to either my SonicWall SoHo or my Linksys routers, I can never establish the PPPoE connection.
I've read on other posts that some people have had difficulty connecting even a single PC to the 5360 depending on the flavor of their ethernet card. It appears, from the posts, that there might be a problem if you are using a 10 base-T rather than a 10/100 card. One post even mentions a firmware update for the 5360, but I have not been able to find any mention of this on an offical web site....
My cards are all 10/100, so I've not personally been able to verify if this is a valid issue or not.
It did, however, get me thinking that the WAN ports on my routers might only be 10 rather than 10/100. If this is a known problem, it might shed light on my situation.
Does this sound legit to anyone or is this just a shot in the dark?
Thanks for your assistance! |
|
 Doctor OldsI Need A Remedy For What's Ailing Me.Premium,VIP
join:2001-04-19
1970 442 W30
kudos:18 | There are not any released to the public (or otherwise available to my knowledge) Firmware(s) for the 5360 modem. If there were any released 5360 Firmware(s) it would be listed here for download »support.efficient.com/drivers/ke···dex.html I've not see Efficient post any Firmwares for their Bridge only units. This could change in the future, but so far that is the current situation.
If there was an Ethernet port issue with your NIC and the 5360 then it would not work when connected directly to your PC, but you say that is the only way that it works right now, so that eliminates any compatibility issues with your NIC and the 5360.
When you put a Router between the 5360 and your PC's NIC, that NIC is invisible (all PCs on the Router become invisible) to the 5360 as all it sees is the Ethernet connector on the Router. If your Router will not connect using PPPoE then you should try a crossover cable or straight cable depending on which you are using at the time (use the opposite of what you have, in other words) since you have two different Routers that are not able to create a PPPoE connection through the 5360 bridge. The 5360 passes all traffic though it since is is classified as a dumb bridge. You may have the wrong cable to use a Router, but the right cable to use a single PC. 
Compatibility issues (if there are any) between the Routers and the PC's NIC would not have any effect on the actual Router creating a PPPoE connection and would not have any effect on the 5360 since it is invisible to all the PCs when a Router is connected.
Try a different cable. 
Regards,
Doctor Olds
--
Starfire is The Future Now!  Clarke's Third Law: "Any sufficiently advanced technology is indistinguishable from magic." |
|
 levI think there is a target on my backPremium,Ex-mod 2002-08
join:2001-05-30
Chicago, IL
kudos:2
 ·AT&T Midwest
| reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/rout I'm coming more public with an issue I've encountered with a client's 5360 and a Netgear RT-314 with Ameritech service.
When the client got sync, before they received their modem, I took an old Westell over, and got them connected on a temporary account. All was well until their 5360 arrived.
It synced just fine, but... and this is the strangest, spookiest thing, there was 80% packet loss ONLY going past ameritech.net.
Plugged back in the Westell, and everything was groovy.
Ordered a new 5360, which had the SAME behavior. I kept this one, and did a direct-connect with a computer that had a 10/100 port, and it worked fine.
Something is not kosher with the 5360s... at least the more recent ones. |
|
| reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/routers) Thanks for the reply.
Doc Olds, I've tried the cross over cable and haven't gotten anywhere... I seem to get better luck with the "straight through" type.
I've got it working atm, but it is not elegant. In order to make it work, I connect a single PC to the 5360 and use Microsofts PPPoE Broadband connection and it works great. This allows me to "trick" the 5360's WAN port... at least thats what I think I am doing. Next, I unplug the cable from my PC and connect it to the Linksys router. Now, the Linksys connects to the 5360 without a hitch. However, if I ever lose power for whatever reason on the 5360, I have to fake out its port with a direct PC sync first... (for lack of a better description..)
I'm not technical enough to understand what is exactly happening when that port/NIC sync first happens, but it sure looks like some sort of issue.
I'm going to try this on my Sonicwall and see if the same method will allow that configuration to work.
Lev, your situation is very interesting. When I first tried configuring this bridge with a SonicWall SoHo last week, I had the same exact problem. (huge packet loss outside ameritech's infrastructure)
Thanks again guys. |
|
| reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/rout If your Sonicwall or Linksys devices have 10BaseT port to the 5360 then it probably is the reported problem. |
|
|
|
 GPrestonHows Ya Durrin?
join:2000-04-15
Dallas, TX | reply to lev
I'm still using my old original Westell WireSpeed modem (>2.5 yrs old). I hooked up the new 5360 they sent me when I switched from CO to RT, get solid green on all the right lights, but cannot connect for some reason.
I'm using a Linky 4-port router, seems to me all I need do is swap the RJ-11 & -45 between modems (and plug the 5360 in) , then reconnect my Linky. Doesn't work, tho.....
Day-ham, I'm glad I have the old WireSpeed, I'd be pulling my hair out about now if all I had was the 5360...... |
|
| reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/routers) Add me to the list of having this same problem. Connecting my PC direct to the 5360 works kosher. I have tried both a SpeedStream 2602 and a Linky BEFSR41 router and neither of them work. I'm going to try SpeedStream tech support and see what they say.
Mike |
|
 TibbyWinbetaPremium
join:2002-06-01
Oswego, IL | reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/rout update me when there is a update about it and the linky instead of doing the trick way I posted a week or so ago
--
StarFire 0wns j00! |
|
| reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/routers) Tiburon-
Can you provide a link to the discussion (or the procedure itself) where you posted about this "trick"? I've searched through the forums but am unable to find it.
Mike |
|
TibbyWinbetaPremium
join:2002-06-01
Oswego, IL | reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/rout Here is what I did exactly.
-------------------------------------
NOTE: Throughout this process, you need a computer by the router for it to work.
1. Make sure everything is set right in the router
2. Disconnect modem from router(Make sure the "status" screen in the router sais "disconnected")
3. Disconnect a computer from the router(KEEP in mind if you have to turn off the modem between changing it, such as different rooms, this will not work!)The MODEM must be on during this process
4. Connect DSL modem into computer
5. Wait about 30 seconds while windows searches for a DHCP server and gives up.
6. Login normally with your favorite PPPoE Software.
7. Test it by going to a few sites(it gets messed up if you disconnect and reconnect really fast), so do somehting for about 30 seconds online.
8. Disconnect the PPPoE connection through your software.
9. Disconnect the modem from the computer(it MUST stay on, thats why earlier I said choose a computer where the router is located)
10. Connect the modem to the WAN port on the router
11. Plug the computer back into the router
12. Go to the status page in the router and hit "connect"
13.In a few seconds you should be "connected" with the router and DSL modem, and be able to surf happily.
--------------------------------
--
StarFire 0wns j00! |
|
| Tiburon-
Thanks for the tip. Unfortunately, that's not the problem I'm experiencing. My router connects fine with Atech, but I cannot access the internet or e-mail through the router. I can do both when I bypass the router and connect my computer directly to the modem.
Mike |
|
Doctor OldsI Need A Remedy For What's Ailing Me.Premium,VIP
join:2001-04-19
1970 442 W30
kudos:18 | Do you get an IP from the router and the router gets an IP from your ISP?
Have you tried pinging yahoo or dslreports?
C:\WINDOWS>ping yahoo.com
Pinging yahoo.com [66.218.71.113] with 32 bytes of data:
Reply from 66.218.71.113: bytes=32 time=80ms TTL=47
Reply from 66.218.71.113: bytes=32 time=94ms TTL=47
Reply from 66.218.71.113: bytes=32 time=79ms TTL=47
Reply from 66.218.71.113: bytes=32 time=79ms TTL=47
Ping statistics for 66.218.71.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 94ms, Average = 83ms
C:\WINDOWS>ping dslreports.com
Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
Reply from 209.123.109.175: bytes=32 time=38ms TTL=243
Reply from 209.123.109.175: bytes=32 time=52ms TTL=243
Reply from 209.123.109.175: bytes=32 time=43ms TTL=243
Reply from 209.123.109.175: bytes=32 time=58ms TTL=243
Ping statistics for 209.123.109.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 58ms, Average = 47ms
If that does not work then try ping on the IP addresses to see if this is a DNS issue.
C:\WINDOWS>ping 66.218.71.113
Pinging 66.218.71.113 with 32 bytes of data:
Reply from 66.218.71.113: bytes=32 time=77ms TTL=47
Reply from 66.218.71.113: bytes=32 time=78ms TTL=47
Reply from 66.218.71.113: bytes=32 time=119ms TTL=47
Reply from 66.218.71.113: bytes=32 time=80ms TTL=47
Ping statistics for 66.218.71.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 119ms, Average = 88ms
C:\WINDOWS>ping 209.123.109.175
Pinging 209.123.109.175 with 32 bytes of data:
Reply from 209.123.109.175: bytes=32 time=39ms TTL=243
Reply from 209.123.109.175: bytes=32 time=40ms TTL=243
Reply from 209.123.109.175: bytes=32 time=37ms TTL=243
Reply from 209.123.109.175: bytes=32 time=38ms TTL=243
Ping statistics for 209.123.109.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 40ms, Average = 38ms
Post back what you find out and then I have another test to try.
Regards,
Doctor Olds
--
Starfire is The Future Now! Clarke's Third Law: "Any sufficiently advanced technology is indistinguishable from magic." |
|
Doctor OldsI Need A Remedy For What's Ailing Me.Premium,VIP
join:2001-04-19
1970 442 W30
kudos:18 | reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/routers) said by FunkyDSL:
[snip]
I got Ameritech DSL last week. It came with the 5360. When connected to a single PC, I've had no problems with it. (works fine) However when connected to either my SonicWall SoHo or my Linksys routers, I can never establish the PPPoE connection.
[snip]
One post even mentions a firmware update for the 5360, but I have not been able to find any mention of this on an offical web site....
Can you find that post again that mentions the 5360 and a Firmware upgrade?
Regards,
Doctor Olds
--
Starfire is The Future Now! Clarke's Third Law: "Any sufficiently advanced technology is indistinguishable from magic." |
|
TibbyWinbetaPremium
join:2002-06-01
Oswego, IL | reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/rout This is a work around for problems of 5360 users and a linky router.
Here is what I did exactly.
-------------------------------------
NOTE: Throughout this process, you need a computer by the router for it to work.
1. Make sure everything is set right in the router
2. Disconnect modem from router(Make sure the "status" screen in the router sais "disconnected")
3. Disconnect a computer from the router(KEEP in mind if you have to turn off the modem between changing it, such as different rooms, this will not work!)The MODEM must be on during this process
4. Connect DSL modem into computer
5. Wait about 30 seconds while windows searches for a DHCP server and gives up.
6. Login normally with your favorite PPPoE Software.
7. Test it by going to a few sites(it gets messed up if you disconnect and reconnect really fast), so do somehting for about 30 seconds online.
8. Disconnect the PPPoE connection through your software.
9. Disconnect the modem from the computer(it MUST stay on, thats why earlier I said choose a computer where the router is located)
10. Connect the modem to the WAN port on the router
11. Plug the computer back into the router
12. Go to the status page in the router and hit "connect"
13.In a few seconds you should be "connected" with the router and DSL modem, and be able to surf happily.
--------------------------------
--
StarFire 0wns j00! |
|
| reply to FunkyDSL
Re: 5360 wan port issues? (prob interfacing w/routers) I've worked out the issue. Just keep throwing hardware at it! I went out and purchased a 3rd router, a SpeedStream 2614. That worked straight out of the box in about 2 minutes. Luckily Circuit City has a very lenient return policy and they allow returns on open box items.
Mike |
|
CCCMTechPremium,VIP,MVM
join:2002-05-17
Baxter, KY | reply to FunkyDSL
Checking ethernet settings for 5360 "slow/no surf" issues
Summary
Some DSL members are experiencing "slow surf" issues when using an ethernet card or hub set at 10Mbps with the Efficient 5360 modem. The latest revision of the Efficient 5360 (released in May 2002) has a firmware compatibility issue with certain settings in Windows operating systems and older Macintosh systems.
Efficient Networks is working on a firmware update that will fix this issue. It will be released shortly.
There are two ways to identify the affected modems:
The box that the modem is packed in will have the part number listed as 120-5360-520
On the modem chassis (the bottom of the modem), the following part number is displayed: 060-5360-023
Procedures
Select the appropriate Operating System and follow the procedure below.
Windows 95/98
Windows Me
Windows NT 4.0
Windows 2000
Windows XP
Macintosh
Windows 95/98
Right-click on Network Neighborhood located on the Desktop and select Properties.
Select the appropriate Ethernet card by highlighting it. Click on Properties.
Click on the Advanced tab.
You will see different parameters in the window labeled Property. Choose Link Speed/Duplex Mode by clicking on it one time.
Reset it to Auto-Detect from the Value drop down. If Auto is already selected, select 100Mbps/Half Duplex.
Click OK. Click OK again to close the Network control panel.
Windows may prompt you to reboot your computer.
Windows Me
Right-click on My Network Places located on the Desktop and select Properties.
Select the appropriate Ethernet card by highlighting it. Click on Properties.
Click on the Advanced tab.
You will see different parameters in the window labeled Property. Choose Link Speed/Duplex Mode by clicking on it one time.
Reset it to Auto-Detect from the Value drop down. If Auto is already selected, select 100Mbps/Half Duplex.
Click OK. Click OK again to close the Network control panel.
Windows may prompt you to reboot your computer.
Windows NT 4.0
Right-click on Network Neighborhood located on the Desktop and select Properties.
Click on the tab labeled Adapters.
Select the appropriate Ethernet card by highlighting it. Click on Properties.
A window titled Speed/Duplex Mode will appear. Select Auto. If Auto is already selected, select 100Mbps/Half Duplex. Click OK. Click OK in the window titled Input Network Address without making any modifications. Click OK in the window titled Input Tx Early Threshold without making any modifications.
You will be prompted to reboot the system.
Windows 2000
Right-click on My Network Places located on the Desktop and select Properties.
Right-click on the active Local Area Connection and choose Properties.
Ensure the correct Ethernet card is displayed under Connect Using. Click on the button labeled Configure.
Click on the Advanced tab.
You will see different parameters. Choose Link Speed & Duplex by clicking on it one time.
Reset it to Auto-Detect from the Value drop down. If Auto is already selected, select 100Mbps/Half Duplex.
Click OK.
Reboot the system.
Windows XP
Go to Start > Control Panel.
Double-Click on Network Connections.
Right-click on the active Local Area Connection and choose Properties.
Ensure the correct Ethernet card is displayed under Connect Using. Click on the button labeled Configure.
Click on the Advanced tab.
You will see different parameters. Choose Link Speed & Duplex by clicking on it one time.
Reset it to Auto-Detect from the Value drop down. If Auto is already selected, select 100Mbps/Half Duplex.
Click OK.
Reboot the system.
Macintosh
There is currently no fix for Macintosh systems. If the Mac is a newer model with a 100Base-T or 10/100 ethernet card, it will auto-detect the speed so there should be no compatiblity issues with the 5360. If the Mac is an older model with a 10Base-T ethernet card, it will not be able to communicate with the 5360 modem. Note that if the member's Mac worked previously with the 5360, there is no incompatibility issue.
--
ASI/SBC CCCM |
|
TibbyWinbetaPremium
join:2002-06-01
Oswego, IL | Re: 5360 wan port issues? (prob interfacing w/rout mine box sais 120-5360-502 and the modem has problems, but the fix I reported works.
--
StarFire 0wns j00! |
|
CCCMTechPremium,VIP,MVM
join:2002-05-17
Baxter, KY | said by Tibur0n:
mine box sais 120-5360-502 and the modem has problems, but the fix I reported works.
There are two ways to identify the affected modems:
The box that the modem is packed in will have the part number listed as 120-5360-520
On the modem chassis (the bottom of the modem), the following part number is displayed: 060-5360-023
apparently these are the only 2 affected according to SBC and Efficient Networks
--
ASI/SBC CCCM |
|
levI think there is a target on my backPremium,Ex-mod 2002-08
join:2001-05-30
Chicago, IL
kudos:2 Reviews:
·AT&T Midwest
| reply to FunkyDSL
Was just going to get on and post the part numbers, rbalthis. Had a tech on the phone from Efficient yesterday that confirmed the problems with the 5360-023, and offered to RMA it for a 5360-002. He wasn't aware of a fix coming, but knew that engineering was looking into it.
I waited to test out the situation with a model labelled 002 to confirm the revision issue.
For now, I'll hold tight and see what happens.
Also, confirmation that the 023's I've seen came in boxes labelled 002. Probably shouldn't have people checking the boxes at all, unless they're trying to determine problems with 020 boxes before people open them. |
|
CCCMTechPremium,VIP,MVM
join:2002-05-17
Baxter, KY | said by lev:
Also, confirmation that the 023's I've seen came in boxes labelled 002. Probably shouldn't have people checking the boxes at all, unless they're trying to determine problems with 020 boxes before people open them.
duly noted
--
ASI/SBC CCCM |
|
