If you need assistance, please send an email to forum at 4hv dot org. To ensure your email is not marked as spam, please include the phrase "4hv help" in the subject line. You can also find assistance via IRC, at irc.shadowworld.net, room #hvcomm.
Support 4hv.org!
Donate:
4hv.org is hosted on a dedicated server. Unfortunately, this server costs and we rely on the help of site members to keep 4hv.org running. Please consider donating. We will place your name on the thanks list and you'll be helping to keep 4hv.org alive and free for everyone. Members whose names appear in red bold have donated recently. Green bold denotes those who have recently donated to keep the server carbon neutral.
Special Thanks To:
Aaron Holmes
Aaron Wheeler
Adam Horden
Alan Scrimgeour
Andre
Andrew Haynes
Anonymous000
asabase
Austin Weil
barney
Barry
Bert Hickman
Bill Kukowski
Blitzorn
Brandon Paradelas
Bruce Bowling
BubeeMike
Byong Park
Cesiumsponge
Chris F.
Chris Hooper
Corey Worthington
Derek Woodroffe
Dalus
Dan Strother
Daniel Davis
Daniel Uhrenholt
datasheetarchive
Dave Billington
Dave Marshall
David F.
Dennis Rogers
drelectrix
Dr. John Gudenas
Dr. Spark
E.TexasTesla
eastvoltresearch
Eirik Taylor
Erik Dyakov
Erlend^SE
Finn Hammer
Firebug24k
GalliumMan
Gary Peterson
George Slade
GhostNull
Gordon Mcknight
Graham Armitage
Grant
GreySoul
Henry H
IamSmooth
In memory of Leo Powning
Jacob Cash
James Howells
James Pawson
Jeff Greenfield
Jeff Thomas
Jesse Frost
Jim Mitchell
jlr134
Joe Mastroianni
John Forcina
John Oberg
John Willcutt
Jon Newcomb
klugesmith
Leslie Wright
Lutz Hoffman
Mads Barnkob
Martin King
Mats Karlsson
Matt Gibson
Matthew Guidry
mbd
Michael D'Angelo
Mikkel
mileswaldron
mister_rf
Neil Foster
Nick de Smith
Nick Soroka
nicklenorp
Nik
Norman Stanley
Patrick Coleman
Paul Brodie
Paul Jordan
Paul Montgomery
Ped
Peter Krogen
Peter Terren
PhilGood
Richard Feldman
Robert Bush
Royce Bailey
Scott Fusare
Scott Newman
smiffy
Stella
Steven Busic
Steve Conner
Steve Jones
Steve Ward
Sulaiman
Thomas Coyle
Thomas A. Wallace
Thomas W
Timo
Torch
Ulf Jonsson
vasil
Vaxian
vladi mazzilli
wastehl
Weston
William Kim
William N.
William Stehl
Wesley Venis
The aforementioned have contributed financially to the continuing triumph of 4hv.org. They are deserving of my most heartfelt thanks.
Registered Member #1262
Joined: Fri Jan 25 2008, 05:22AM
Location: Maryland, USA
Posts: 451
I've got 1.5mbps DSL from earthlink (verizon is the actual provider) with a ZyXEL modem/router connected through 100T ethernet. It's had been working fine until I tried to configure my NIC card and router for a static local IP (using this guide: ), something must have gone wrong at some point! I had gotten the static IP set up and then disabled DHCP on my modem/router thing, at which point I could no longer connect to the internet, or even get back to the modem config page!
My NIC card is fine, it even sees that there is something connected to to it when the modem is on. The modem also reports that ethernet is working. I just can't get DSL to work at all, netstat turns up everything as blank. I'm back to my monthly 20 free hours 56k until tech support can do anything.
Something is definatly screwed up with either the modem or the NIC settings.
BTW: the reset button on the modem/router doesn't seem to do anything.
EDIT: With dialup on, oddly, I can access the modem's config page at 192.168.1.1.
Registered Member #16
Joined: Thu Feb 02 2006, 02:22PM
Location: New Wilmington, PA
Posts: 554
Hold the reset button on the router down for 30 seconds. Then reset your NIC to use DHCP. You'll regain connectivity.
Double check the local IP address, DNS, and gateway addresses you gave your NIC. For whatever reason, one of your settings is outside the router's current configuration.
It sounds like it could potentially be an IP conflict between the router and your computer, or your computer and the modem.
You shouldn't need to disable DHCP on your router to configure a static IP address for your computer. Simply setting your NIC to use an IP address outside the router's DHCP address block will usually get it working just fine.
As an example, if your router used 192.168.1.1 as its IP, chances are good the DHCP block is 192.168.1.100 to 192.168.1.200 or similar. Setting your NIC to use a static address of 192.168.1.25 should permit it to connect to the router just fine, and its highly unlikely that your modem is using .1.25, ensuring there won't be an IP conflict.
Registered Member #1262
Joined: Fri Jan 25 2008, 05:22AM
Location: Maryland, USA
Posts: 451
Thanks, Dave!
I got DHCP re-enabled a few minutes ago and DSL is working again.
The whole reason for this is because Vuze seems to be the only torrent program that allows you to pick one single file out a huge torrent. And Vuze is a real ***** about port settings. Any other torrent programs out there that let me pick one file out of a huge torrent for downloading?
If not, I'll try to get my DSL as static local IP tommorow.
Registered Member #538
Joined: Sun Feb 18 2007, 08:33PM
Location: Finland
Posts: 181
Backyard Skunkworks wrote ...
Thanks, Dave!
I got DHCP re-enabled a few minutes ago and DSL is working again.
The whole reason for this is because Vuze seems to be the only torrent program that allows you to pick one single file out a huge torrent. And Vuze is a real ***** about port settings. Any other torrent programs out there that let me pick one file out of a huge torrent for downloading?
If not, I'll try to get my DSL as static local IP tommorow.
µTorrent can do that and 1000 other things + its very light.
Registered Member #56
Joined: Thu Feb 09 2006, 05:02AM
Location: Southern Califorina, USA
Posts: 2445
but it will still not get great speeds unless you open up a port for it.
You should be able to get away with assigning yourself a static IP at an addres that your router is never going to assign anyway. If you have 5 computers that will get addresses in the 192.168.1.2-10 range, you can statically set your computer at like 192.168.1.240 you should be fine (make sure to use the same 255.255.255.0 subnet mask and 192.168.1.1 default gateway, you can use 192.168.1.1 for your dns server, or 208.67.222.222 if you like opendns.com, or whatever was shown in ipconfig -a). Unless you have a really big lan party some day...
BTW, the guide you were using makes no mention of what hapens when you assign your computer an address that you router has already given to a different computer--neither of the computers work properly.
This site is powered by e107, which is released under the GNU GPL License. All work on this site, except where otherwise noted, is licensed under a Creative Commons Attribution-ShareAlike 2.5 License. By submitting any information to this site, you agree that anything submitted will be so licensed. Please read our Disclaimer and Policies page for information on your rights and responsibilities regarding this site.
DSL/Ethernet Problems
