 wayjacPremium,MVM
join:2001-12-22
Indy | reply to Hoibb
Re: Westell 7500 - interferes with server said by Hoibb:I assume you mean use the old wireless for the wireless connection That's not what I suggestedsaid by Hoibb:I guess I have to find out exactly what "bridge mode" is and how to invoke/enable it... I could attempt to explain it to you
I could also attempt to explain how to invoke/enable itsaid by Hoibb:Does bridge mode do something different or more thorough than disabling the wireless radio transmitter? Since you have a wireless router the server would physically connect to the wireless router |
|
|
|
Hoibb
join:2012-02-01
Exeter, NH | WayJac - let me see if I can simplify this:
What is "bridge mode"? The Westell comes with NO documentation. The folks at Fairpoint have never heard of the term "bridge mode". I know. I just called them checked with their tech support.
You said above, "...the server would physically connect to the wireless router". I'm saying as soon as I physically connect the two devices, the server begins a continuous rebooting loop which means it's unreliable for doing anything.
There is something about that Westell design that brings about this condition, I'm sure of it because of my extensive testing. That's why I brought the inquiry here - to see if anyone else has had the problem and has a solution.
OK?
H |
|
wayjacPremium,MVM
join:2001-12-22
Indy | said by Hoibb:WayJac - let me see if I can simplify this: What is "bridge mode"? The 7500 is a router and a dsl modem setting the 7500 to bridge mode disables the 7500 routersaid by Hoibb:The folks at Fairpoint have never heard of the term "bridge mode" Ok....said by Hoibb:You said above, "...the server would physically connect to the wireless router". I'm saying as soon as I physically connect the two devices, the server begins a continuous rebooting loop which means it's unreliable for doing anything Ok.. this is different than what you posted beforesaid by Hoibb:I brought in an old wireless router from home. Put it and the server together with Cat5 (again, just the two devices, no network). Server stayed lit for a couple of hours with no reboot Why not use a different adsl router |
|
Hoibb
join:2012-02-01
Exeter, NH | I'll try again, please
To review: I said, "So it's just the server and the Westell, nothing else." Also: "I simply powered the replacement up (sans config), plugged in the Cat5 to the server and fired it up."
Physically, then, the connection series is: Server to Cat 5 to Westell and the simple act connecting the two devices causes one to fail.
Anyway, I still have very little information about bridge mode. I could experiment with it, if I (or my ISP) knew the steps involved.
H |
|
wayjacPremium,MVM
join:2001-12-22
Indy | What I was trying to suggest was a setup like this:
server to cat 5 to wireless router to cat 5 to westell
Bridging the westell is one option there are other options that can be used |
|
Hoibb
join:2012-02-01
Exeter, NH | Oh, OK. I know this:
server to cat5 to Cisco 16-port switch to cat5 to Westell also fails. But, hey - Just to be sure I'll try it your way and see what happens.
Thanks.
Hoib |
|
wayjacPremium,MVM
join:2001-12-22
Indy | If you include the 16 port switch then, the connection series will be
server to cat 5 to 16 port switch to cat 5 to wireless router to cat 5 to westell
Since bridging the westell is not a option the westell should have a
static nat option that can be used for the wireless router |
|
Hoibb
join:2012-02-01
Exeter, NH | Failure!
server to cat5 to 16 port switch to cat5 to wireless router to cat5 to westell results in reboots.
server to cat5 to 16 port switch to cat5 to old wireless router from home results in no reboots.
Server to Cat5 to Westell results in reboots.
Again, anytime the server and the westell are connected, whether directly or indirectly (via the router) results in rebooting the server.
This is absurd. We're going to try a Cat6 cable next. Then we're going to try a new NIC card off the PCI bus on the server.
H |
|
