Quote :

campsoup1988 wrote :   I hope I am not in the same situation.  If I am, my dad will kill me

If the situation is that critical, I could try to offer some help but I'd need to know more about your current configuration.

Quote :

meckelbu wrote :   If the situation is that critical, I could try to offer some help but I'd need to know more about your current configuration.

its not that critical.  he will just be mad that I did not realise it would not work and stop him from buying it.

We have WinXP on our comps.  Our ISP is Bellsouth.  The DSL modem is Westell 6100 and the router is linksys wrh54g

Quote :

campsoup1988 wrote :   its not that critical.  he will just be mad that I did not realise it would not work and stop him from buying it. We have WinXP on our comps.  Our ISP is Bellsouth.  The DSL modem is Westell 6100 and the router is linksys wrh54g

According to some information I dug up the Westell you have is most likely also configured as a router, and so putting another router behind is problematic as you've noticed. The 'correct' way to do it would be to reconfigure the Westell as a bridge, then put the wlan router behind it and plug all your machines behind the router. Or for a quick fix you can try this : configure the router's wlan side, turn off the dhcp server on it and plug the cable coming from the Westell into one of the ethernet ports instead of the internet port (unless you've already tried that).

If you want to check whether your Westell is a router, open a command prompt (Start -> Run -> type "cmd.exe" (without quotes) into the box), then type "ipconfig" (again without quotes) into the command prompt window and see if the 'IP Address' looks like 192.168.x.y .  

--Last edited by meckelbu on 2007-12-10 13:33:47 --

Quote :

meckelbu wrote :   According to some information I dug up the Westell you have is most likely also configured as a router, and so putting another router behind is problematic as you've noticed. The 'correct' way to do it would be to reconfigure the Westell as a bridge, then put the wlan router behind it and plug all your machines behind the router. Or for a quick fix you can try this : configure the router's wlan side, turn off the dhcp server on it and plug the cable coming from the Westell into one of the ethernet ports instead of the internet port (unless you've already tried that). If you want to check whether your Westell is a router, open a command prompt (Start -> Run -> type "cmd.exe" (without quotes) into the box), then type "ipconfig" (again without quotes) into the command prompt window and see if the 'IP Address' looks like 192.168.x.y .

I tried to turn on the bridge setting on the Westell without luck.  The instructions I find at bellsouth's site did not match the screens I was getting.  Ill look into your other suggestion.  Last time I looked, I couldnt find the settings

Quote :

campsoup1988 wrote :  I tried to turn on the bridge setting on the Westell without luck.  The instructions I find at bellsouth's site did not match the screens I was getting.

Possibly from a different firmware version, there are sometimes pretty drastic changes between them.

This page has info about configuring different Westell modems :

http://www.dslreports.com/faq/6096

Quote :

campsoup1988 wrote : Ill look into your other suggestion.  Last time I looked, I couldnt find the settings

My other suggestion pretty much just bypasses the router part on the wlan router, also assign some other local ip address to it than the default 192.168.1.1, like 192.168.1.100 . This setup worked for the crummy WRT54G I had here before I replaced it with the other AP that's capable of bridging.  

--Last edited by meckelbu on 2007-12-10 17:28:04 --

Quote :

meckelbu wrote :   Possibly from a different firmware version, there are sometimes pretty drastic changes between them. This page has info about configuring different Westell modems : http://www.dslreports.com/faq/6096 My other suggestion pretty much just bypasses the router part on the wlan router, also assign some other local ip address to it than the default 192.168.1.1, like 192.168.1.100 . This setup worked for the crummy WRT54G I had here before I replaced it with the other AP that's capable of bridging.

The strange thing is, the exact model number of the westell router I have is E90-610030-06, and the closest model number I have seen arround on westell's site or the site you reccomended is B90-610030-06.  Ill check your other suggestion tommorow, I dont have the time tor try setting it up tonight.

Tech support via the forum! What next? I've got Yuoogle and Tech Support!

how about me selling flooring to floridians via this forum?  My grandfather runs a flooring business!

~~~~~~~~~~~~~~~

YES!!!!!!!!

Somehow, dont ask me how, since I was basicly doing the same thing I was doing the other day, I got my modem and the router talking to each other and got the network set up!!!!  

--Last edited by campsoup1988 on 2007-12-11 14:38:33 --

My usual solution to that problem is to use someone else's DNS servers.

The ones I run for our customers at work are 64.135.1.20 and 64.135.2.30. Enjoy.

Im not sure in was the DNS server fault since I was able to get on without using the wireless router

Camp : You must have accidentally pleased some computer deity    

Good that you got it to work, it's depressing to try to setup/fix something for days and lose in the end.

I must have.

In my family I know computers this best, but have the worst luck with them...

For my part, I wouldn't say "addiction." I am, however, fully self-hosted.

This means that, in effect, I am my own ISP. My upstream provider (Drizzle Northwest, via Qwest) feeds me ADSL plus six static addresses. I do the rest: Authoritative DNS (I host multiple domains), Web, mail, NNTP (Usenet), FTP, the works. There's a big Compaq-branded rack in the garage containing our servers, and an open-frame one next to it containing the network goodies.

I will say that it has been quite the education. Most of what I know about Unix-ish OS's, routers, and firewalls I learned from having to set them up and run them. Best possible way to learn, actually, because if you screw up it's YOU that's off the air!  ;)

The only other thing I would add is that NONE of my Intenet-exposed systems are Windows-based. I'm not that crazy. Anything that's 'net-exposed is based on FreeBSD and other open-source goodness.

Keep the peace(es).

kyrrin : I have a similar situation here though I haven't bothered to setup DNS or mail servers of my own, at least not yet, and I only have one fixed ip since my provider won't give me more for an ADSL line. I'm not Windows-free either, one beefy PC with Windows XP for games and another XP installed "on" a SunPCi card installed inside a Sun E250, several closed-source Unixes too.

What kind of hardware do you use for you servers?

meckelbu: If you decide to do as I did, prepare yourself for lots of long hours of self-education, setup, and some frustration (at least until you figure out where the pitfalls are). I will say that it gets much easier with time and practice.

Anyway... I'm pretty much a Compaq/HP shop. That's what I maintained during part of my tenure at Boeing, so it's what I'm most familiar with. The two DNS and the mail server are all HP NetServer LP1000R 1U boxes. Interestingly enough, they were retirees from Amazon.com (I got them for cheap when they showed up at a local computer surplus wholesaler I'm friendly with).

The web server, and our two Windows 2000 domain servers, are all Compaq DL380 Gen 2 boxes. Our voicemail and network FAX are also based on the Win2000 boxes.

As for the big FTP archive, it's a Compaq Proliant ML530 with an additional external RAID array. Quite the monster, in the physical sense, but it runs surprisingly quiet for its size. The only systems that are Windows-based are the two domain boxes, and they're not directly Internet-exposed. Every other system is based on FreeBSD, Apache, Postfix (mail transfer) and other open-source goodies.

Our border router/firewall is a Watchguard Firebox X1000. Our main LAN switch is a Cisco Catalyst 5505. I also have various minor components... cabling, patch panels, a little-used wireless node, DLT tape library for backup, etc.

Probably sounds expensive. Honestly, it wasn't. Naturally, there's no way that I could ever have afforded even a tenth of the current setup had it been purchased new. Every single box I've got is a refugee from the surplus market, either from Boeing (back when they still had a retail surplus store) or other scrounge trips to various spots. Total hardware investment over the last decade or so is probably less than $5,000 for everything.

'Tis amazing what one can do with some judicious scrounging.  

Happy travels.

No offense, but believe me when I say that I know a little something about self-education, setup and frustration.  

Your setup sound quite professional, mine is more like slapped together with whatever I had handy.  ;)  Like this (I'm only listing my "active" machines and not my projects) :

• Router/firewall/rudimentary traffic logger-shaper/dhcp-bootp server, self-built dual processor PC, 466MHz Celerons and a single scsi disk. Debian Linux.
  

• Fileserver, ftp/sftp/samba/nfs, another self-built PC with 1.4GHz AMD Athlon. Eight ide disks totaling around 1.5TB, a twelve disk FC-AL array with 73GB 10k rpm disks, a scsi card with a 10-tape DLT tape library attached and to which I could attach a scsi disk array or two if I had enough spare SCA scsi disks. Debian Linux.
  

• Web/ssh/whatever server, NCR Worldmark 4400 (a large PC with 4*400MHz Xeons and hardware scsi raid), slow but reliable as it has never failed me in five years, and has even survived a very short power loss without an UPS while two switches and another computer connected to the same outlet rebooted. Gentoo Linux.
  

• Alphaserver 1000RM (300MHz Alpha EV5, 256MiB ram), my scanner machine and provides X-Windows through the network to my main rig so that I can use it. Debian Linux (or Tru64 Unix).
  

• Noname 166MHz Alpha EV4 (it is really known as a Noname!) that I've been trying to turn into a radius server for my wlan. Debian Linux.
  

• Ups controller, a HP9000 pizzabox (50MHz pa-risc), it's only job in life is to monitor my UPS, warn other machines of a power failure and send shutdown commands to them once the battery get too low (battery lasts about 30-35 minutes). Debian linux.
  

• Network equipment : 24-port 10/100Mbit Baystack 350T-HD switch, a 16/4Mbit Baystack Token Ring hub (yes, I run token ring here) and one 10Mbit HP Advancestack hub for thin ethernet. I might replace all of them in the future with this : LINK , once I buy one token ring and one 1000Mbit fibre-optic ethernet switch module for it.
  

Also some of my more interesting desktops :

• SGI Octane, a desktop I use for my online banking and other similar more sensitive stuff. IRIX 6.5.30.
  

• Sun E250 (2*400MHz UltraSparcIIs), another 'desktop' machine I use for this and that. Solaris 10.
  

• HP Visualize J5600 (2*552MHz pa-risc), yet another desktop that's connected to the same display and keyboard/mouse as my main rig so that I can use both from the same spot. HP-UX 11i.
  

As for my other machines/components/projects, they are so many that listing them here would take all day, ranging from small components to entire servers. Stuff like three RS/6000s, another HP9000, a quad processor Sun E450 server, SGI Origin 200 and huge loads of components.

I have no idea how much money I've spent over the years and I don't really care either, as this is my only actual hobby and hobbies tend to cost money.     Electricity is another large expenditure as most of those machines are old, noisy and power-hungry beasts, the noise doesn't bother me but the enormous amounts of heat generated by them do.    

--Last edited by meckelbu on 2008-01-24 06:08:22 --

Dang... I know where to come for Tech support!