| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 82365 | 2007-08-25 00:13:00 | Modem/Router problem... weird | Myth (110) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 584386 | 2007-08-25 00:13:00 | Last night I decided it was well over time to harden up the firewall settings on my router (D-Link 504G - over 2 years old). I set up everything as I wanted, and then applied settings. Incidentally, I use static IP's within the network. Once it rebooted, I couldn't connect to the router at all. Couldn't ping it, couldn't do anything (cept swear at it). Pushed the reset button at the back, held it down for over 30 seconds (couldn't remember how long was required before it would restore back to factory settings and and factory assigned ip (10.0.0.1)). Tried to access at the factory ip, noticed that the router wouldn't reboot fully after reset. Pulled power supply, which reset it again (I am assuming it kept all the changes I had just entered). Set up another computer to be within same subnet as router. Nada, even with ping. Went out today and bought a Belkin. Read instructions, had same problem I'm like W T F????? Anyway, tried various means to access new router, all computers connected to it could ping each other, but couldn't ping the router. ??? I was trying all this from 3 different computers, all different O/S's, even had some turned off etc etc In last ditch effort, tried accessing the router wirelessly from my laptop. Success (at last :D) ... and configured router how I wanted. Anyway, can anyone explain what the heck happened, and why I wasn't able to access even a brand new router/modem via wired LAN. Is the D-Link dead in the water? I still can't do anything with it :( |
Myth (110) | ||
| 584387 | 2007-08-25 00:35:00 | Don't know if this is of any help, but had the almost exact problem yesterday. Was with a single PC though. Wireless would connect but wired setup wouldn't. it ended up being that ever resourceful windows firewall blocking the wired connection. Disable it, and bingo away it went. Stupid question time :lol: Not using cross over cables are you? [Quote] Read instructions [End] :D Who reads in structions :lol: thought that was the last ditch result when all else fails.:D Regarding the D-link 504G - I have seen LOTS of D-links give strange problems. One thing that comes to mind - whats the IP range in the router compared to the IP in the Modem - or is it a modem/router all in one? |
wainuitech (129) | ||
| 584388 | 2007-08-25 00:57:00 | Network was existing, not a new setup. So it all worked perfect before last night (and thinking about it, I was having an issue seeding with Azureus that I just put down to site problems). Its a router/modem (combined) |
Myth (110) | ||
| 584389 | 2007-08-25 01:04:00 | Strange Alright:confused: If it was just the D-Link I wouldn't be surprised, I have had many strange things happen with D-Links, I normally change them for Belkin myself. For Azureus, I found you have to go into the settings find what port its using and open that port in the router then it works lots better - faster. Options/pref/ Connection - Port Number |
wainuitech (129) | ||
| 584390 | 2007-08-25 02:42:00 | Last night I decided it was well over time to harden up the firewall settings on my router I set up everything as I wanted, and then applied settings. Once it rebooted, I couldn't connect to the router at all. ( Well yep, thats secure all right. |
pctek (84) | ||
| 584391 | 2007-08-25 10:44:00 | Well yep, thats secure all right. But maybe the bad guys could still get to it from the WAN side:) |
linw (53) | ||
| 584392 | 2007-08-25 10:52:00 | Default IP address for the DSL-504G is 10.1.1.1 and check the quickstart guide at www.dlink.com.au |
gcarmich (10068) | ||
| 1 | |||||