Help! Router and internet not working together!

Hyper_Kagome

Well-Known Member
Soooo, I've somehow did the impossible. (And I hope this is the right area for posting this.)

I have a D-link WBR-2310 Wireless Router. I was in the admin settings to get another WEP set-up since I just moved back into my dad's and it hasn't been used in a long time.

I got it working for my Laptop and my Nintendo DS. Went to go set up with my 360. Kept saying that it couldn't connect to my network/get an IP and to check that DHCP (or whatever) was enabled.
So I skipped onto the admin settings again and saw MAC Filtering and it talking about DHCP and thought "I'll set this to ENABLE as it will then let things onto the network". So I put in the MAC Address to my 360 into the list, saved...

AND NOW: I cannot get onto the internet with ANYTHING when the router becomes involved. I have completely locked it out.

Any ideas on how I can restore my router to factory defaults so I can just start from scratch and get everything up and running?

ALSO:
My dad says his computer seems to bog down whenever I have my router all hooked up... I'm thinking Bandwidth?
 

voyagerfan99

Master of Turning Things Off and Back On Again
Staff member
To reset the router, there is a little button next to the power plug. Hold it down with a paperclip for about 10 seconds and it'll reset to factory defaults.

As far as speed, yes. I'd imagine bandwidth.
 

Hyper_Kagome

Well-Known Member
Testing.

EDIT:
You never seem to disappoint, Travis.

Now for me to set this up right.
 
Last edited:

Nanobyte

New Member
You've probably reset already but here's how you may have got out of the fix.

1. Disable the MAC address settings (you don't have to delete the numbers you put in) until you sort things out.

2. Go to the LAN settings and enable DHCP Server like the 360 and everything else said. That will allow your 3 units to go to the router to get their LAN addresses 192.168....etc. If you do that, you have to ensure that each unit's TCP/IP Properties are set to obtain IP address automatically (if that's an option).

3. If the new security is messing things up, put in new settings.

If your wireless connection fails, you can connect to the router with an Ethernet cable and access the settings.

If you have port forwarding to any of the units you will have to use DHCP Server disabled and give each unit a unique address on the LAN. Alternatively have it enabled and give static addresses to those needing them outside the range of the DHCP Server addresses.
 
Last edited:

Hyper_Kagome

Well-Known Member
So I had my Wireless all set up and working. Got it on my computer and DS... then when I went away from the area where the router was - still worked on the computer but then later stopped working on the DS. Things like it couldn't obtain an IP or connect to the network when it did just 30 minutes previously.

BUT. I wake up today and my dad has unhooked it all. Again.
Apparently just having my router hooked up (even if he's a wired connection) "bogs his computer down."

I just don't know what to do.
Spend the money to get a Gateway from his ISP? (HE refuses to pay for it if it costs money.)
 

FairDoos

Active Member
Lol can i just ask why you did a post saying "Testing" surely if you can get on the website that automatically tested if it worked.. Postcountwhore.

ANYWAY. Yer that will be your bandwidth changing your router wont help i dont think so id upgrade your megabitings with your ISP :)
 

Hyper_Kagome

Well-Known Member
Lol can i just ask why you did a post saying "Testing" surely if you can get on the website that automatically tested if it worked.. Postcountwhore.

ANYWAY. Yer that will be your bandwidth changing your router wont help i dont think so id upgrade your megabitings with your ISP :)


I'm hardly a post count whore, and if you have an issue with my posting of a RESPONSE TO SOMEONE, leave the thread. :)

I was on a wired connection at that point, not my wireless. Sheesh. I come here for help, not to be slammed by users. It's people like you that make people not want to come back at times. Hope you know that. ;) Not very community like.

Anyway, it seems to be finicky. I have it all hooked up again now and it gives limited access unless it's been unplugged and rebooted one or two times. I just had my DS and 360 all going good and was about to move onto the PS3 when the 360 suddenly lost it's connection and is having issues connecting... again.
Now it's talking about MTU settings and how it requires a minimum of 1364 MTU setting... My God, there are issues everywhere that I don't even understand with this stuff.

2nd attempt:
Console can connect to Xbox Live but the router/gateway isn't properly responding to UCMP responses.

3rd:
I've changed the MTU as it was stating, and I'm right back to square one: Can't obtain an IP address.
Changing the MTU back to the router default. Can once again connect to the internet and obtain an IP... no Live as of yet. Troubleshooting is now telling me to restart the router for 30 seconds. - Which I did and now I can't get an IP again. AHAHAHHA. Fun game this is.
 
Last edited:

Nanobyte

New Member
How does Dad's computer fit into all this? You say his computer slows down when you hook up your router so he disconnects everything. What is his computer connected to? Regarding bandwidth, don't you have some idea of what/who is using what? Is the X-box problem occurring with Dad connected?

It seems the X-box is the problem, it would help if someone with X-box experience could chip in.
 

Hyper_Kagome

Well-Known Member
Well, HE says it bogs his computer down, which I think is absolute bull. Right now I have his computer and mine working fine. His is a wired connection as he has no wireless card in his desktop, and my Laptop is wireless.

Edit:
Xbox cannot obtain an IP.
DS randomly chooses when it can and cannot connect to the network, obtain an IP or completely connect.
PS3 can connect.
- I'm starting to think that whenever I get one more thing successfully onto the wireless with an IP and connection, another gets knocked off. I had the DS before. As soon as I got the PS3, I tested the DS and it wasn't able to obtain an IP. 360 still can't. PS3 is currently updating it's data. /edit

Odd thing is, I had it all working fine when I was living here last year. No MTU, IP, or UCMP issues. and I have it all hooked up as I did before.

Modem into the WAN of the router. Desktop into the LAN of the router. SSID and WEP key all entered right.

It was going fine for all of five minutes earlier until that silly MTU stuff. So I changed the MTU and then nothing got an IP. So I put it back to default... and well you saw that post I'm sure.

I've been reading over the troubleshooting things on the Xbox support site. I do the steps and it doesn't seem to help the issues at all (in the case of the MTU and router power off/on)
 
Last edited:

Nanobyte

New Member
There is a fairly long support post here. Not all is relevant. The wireless setup info may be helpful. Other than that, the advice I can find elsewhere for X-box basically says Enable DHCP Server and make network connection automatic, both of which I assume you have done.
 

Hyper_Kagome

Well-Known Member
It seems like it's going to work for now after manually putting in the IP, Subnet, Gateway and the DNS. Only issue is that I had to offput the secondary DNS by a number as my computer wasn't giving me a secondary number to copy in as shown in the Xbox Solutions.

Either way... it seems fixed for the time being, it's just time to see if it STAYS this way.

I thank you deeply.

If more issues arise I'll likely post back. But I do work in an hour as well. Blaaah.
 

Nanobyte

New Member
You probably know that you can use manual LAN IP addresses even if the DHCP Server is set to auto. You only have to make sure the address is not going to be in conflict. If the lower end of the DHCP Server range is 192.168.1.100 you could manually set a device to say 192.168.1.120 which allows 20 other devices to be added without issue, or to say 192.168.1.90 which is outside the range.

I think your main address change needs to be "not.at.your.dads"
 

Hyper_Kagome

Well-Known Member
You probably know that you can use manual LAN IP addresses even if the DHCP Server is set to auto. You only have to make sure the address is not going to be in conflict. If the lower end of the DHCP Server range is 192.168.1.100 you could manually set a device to say 192.168.1.120 which allows 20 other devices to be added without issue, or to say 192.168.1.90 which is outside the range.

I think your main address change needs to be "not.at.your.dads"

Well I had manually put in the IP like it told me to and then it gave me the DNS error. Hence the manual DNS entry.

But I do like that address change... Made me laugh.
If I get knocked off the network again I'll likely tinker with the last couple digits as you've stated to see if that helps.
 

FairDoos

Active Member
Well as you mentioned your router quite alot i assumed you were on a wireless connection i'm not exactly slamming you am i? Sorry i didnt give you the response you really wanted but in my opinion posting something saying TESTING is just +1 to post you clearly know your internet works when you automatically click your browser shortcut.

Anyway enough of that hope you can get it sorted! :)
 

johnb35

Administrator
Staff member
Usually doing a hard reset on the router fixes everythng, whch I know you already did. And if not, it might be that the router is just starting to die.

Does your dad have a router for himself or possibly a modem/router combo unit? If so, then you need to basically just turn your router into a switch by disabling dhcp and assigning it an ip address outside the range of your dads. For example, if your dads router ip address is 192.168.1.1 then your router should be set to 192.168.1.2. This way the ip addresses and dns and all that other good stuff is handled by your dads router. Basically all you need is a cable going from one of the 4 ports on his router to an LAN port on your router, do not use the wan port. The second router must be setup prior to being hooked up to the first.
 
Top