Tech Support Forum banner
Status
Not open for further replies.

Belkin Wireless G not working

9K views 23 replies 3 participants last post by  2xg 
#1 ·
My roommate bought a Belkin F5D7234-4 V5 router at Walmart and it keeps dropping the internet. Our computers stay connected but the router keeps telling us that it's trying to connect to the internet again. The apartment wired connection is just fine. Right now I'm writing this and the stupid router is blinking at me... Our apartment complex provides internet so I don't have access to the modem, or even know if it's dsl or cable. I've checked the firmware and it's up to date. All the settings are factory pre sets. The only thing we changed was the name and password for the wireless. Any ideas?
 
#3 ·
Yeah, it will work for about a minute or two and then the internet and modem lights start blinking. The only log I could find was under "security log". I have no idea what to look for. So I will paste it. Sorry I don't know too much about routers.

Log File System Log 01/21/2011 23:13:06 DHCP Client: [WAN]Send Release01/21/2011 23:12:19 192.168.2.2 login success01/21/2011 23:10:55 NTP Date/Time updated.01/21/2011 23:10:45 DHCP Client: [WAN]Receive Ack from 10.1.1.10,Lease time=17280001/21/2011 23:10:45 DHCP Client: [WAN]Domain name = stonebrook.local01/21/2011 23:10:45 DHCP Client: [WAN]Send Request, Request IP=10.1.0.24701/21/2011 23:10:45 DHCP Client: [WAN]Receive Offer from 10.1.1.1001/21/2011 23:10:45 DHCP Client: [WAN]Domain name = stonebrook.local01/21/2011 23:10:45 DHCP Client: [WAN]Send Discover01/21/2011 23:10:43 DHCP Client: [WAN]Send Release01/21/2011 23:10:41 DHCP Client: [WAN]Receive Ack from 192.168.0.1,Lease time=8640001/21/2011 23:10:41 DHCP Client: [WAN]Send Request, Request IP=192.168.0.10001/21/2011 23:10:41 DHCP Client: [WAN]Receive Offer from 192.168.0.101/21/2011 23:10:41 DHCP Client: [WAN]Send Discover01/21/2011 23:10:27 sending ACK to 192.168.2.2 Firewall Log 01/21/2011 23:13:01 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:12:54 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:12:49 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:12:48 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:12:48 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:12:47 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:12:40 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:12:34 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:12:28 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:12:20 **IP Spoofing** 192.168.2.1, 138->> 192.168.2.255, 138 (from WAN Inbound)01/21/2011 23:12:15 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:12:15 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:12:14 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:12:13 **IP Spoofing** 192.168.2.1, 67->> 192.168.2.2, 68 (from WAN Inbound)01/21/2011 23:12:09 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:12:02 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:11:55 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:11:53 **IP Spoofing** 192.168.2.7, 5353->> 224.0.0.251, 5353 (from WAN Inbound)01/21/2011 23:11:49 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:11:43 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:11:42 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:11:42 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:11:41 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:11:36 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:11:30 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:11:28 **IP Spoofing** 192.168.2.1, 0->> 224.0.0.252, 0 (from WAN Inbound)01/21/2011 23:11:25 **IP Spoofing** 192.168.2.1, 0->> 224.0.0.252, 0 (from WAN Inbound)01/21/2011 23:11:22 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:11:21 **IP Spoofing** 192.168.2.1, 0->> 224.0.0.1, 0 (from WAN Inbound)01/21/2011 23:11:15 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:11:10 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:11:09 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:11:09 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:11:08 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:11:02 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:10:56 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:10:49 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:10:43 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:10:37 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:10:36 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:10:36 **IP Spoofing** 192.168.2.1, 32769->> 192.168.2.255, 10111 (from WAN Inbound)01/21/2011 23:10:35 **IP Spoofing** 192.168.2.1, 1900->> 239.255.255.250, 1900 (from WAN Inbound)01/21/2011 23:10:34 **IP Spoofing** 192.168.2.7, 0->> 224.0.0.251, 0 (from WAN Inbound)01/21/2011 23:10:33 **IP Spoofing** 192.168.2.1, 67->> 255.255.255.255, 68 (from WAN Inbound)01/21/2011 23:10:32 **IP Spoofing** 192.168.2.1, 0->> 224.0.0.1, 0 (from WAN Inbound)
 
#4 · (Edited)
Put a password on the router. The default is not good enugh. You used to be able to not need a password all you had to do was press the submit button with a blank pass and it would let anyone into the belkin.
Looks like someone is tryin to config/hack your router from outside but it might be a false positive. Are you running file sharing? don't and thats all well say about that cause you cant talk about it here.

Anyone else notice this pattern----DHCP discovery > offer > Request > ack > Client send released hmmmmm... i gotta think about that plus the spoofing warnings.
 
#6 ·
A password for the wireless connection or to access the web interface? Neither of us are running any file sharing programs. We just got the internet turned on a few weeks ago and the router about a week ago. My roommate told me that one of his previous roommates had a different router hooked up to the apartment internet when they had it 6 months ago and had no problems at all. Could it just be that the router is crap?
 
#9 ·
Ok so this is weird. I wanted to see what the router would do on another internet source but it was too late to go to any friends. So I connected the router to my desktop which I have two network adapters. (I installed a second one to connect to my PS3. It was more stable and cheaper than a wireless card) Anyways I shared the internet between the cards and voila. The router works like a charm! Of course I'd like to figure out how to not have to have my desktop running all the time to have wireless...
 
#12 ·
Ok, I tried setting up the static IP and it didn't work. Although I'm not sure if I did it right because when I changed it, it asked me for the "subnet mask" and "default gateway" of which I had no idea what they were. I googled around and found something that told me to put the subnet to 255.255.255.0 and the default gateway to 192.168.0.1 But anyways it did the same thing as before.

The only way I can get the router to work is to hook up the internet to my desktop and share internet with the router. Any ideas as to why it works this way and not the other?
 
#13 ·
Hi Futureboy63,

If ICS works well, you may keep it this way.
he only way I can get the router to work is to hook up the internet to my desktop and share internet with the router. Any ideas as to why it works this way and not the other?
We can also still help you resolve the wireless issue if you want.
From the problematic wireless computer pls. install and run Xirrus Wi-Fi Inspector.
Click on the 'Show Networks' to display all wireless networks on the xirrus icon on your desktop of if you have one running in a corner. Tap the Printscreen key on your keyboard, open up Paint then choose Edit from the Menu and select Paste, then SAVE it. Upload and attached it here, click on Go Advanced and locate Manage Attachments Tab and attached the file.

Please let us know.
 
#15 ·
From your computer make sure that DHCP is enabled in your wireless connection and 'Obtain DNS server address automatically' is selected.

Let's do a test, try removing the network encryption completely from the router, test your connection. If you're able to get a solid wireless connection, lets try a very low Security - WEP, test your connection again then report back here.
 
#16 ·
DHCP is enabled and Obtain DNS is selected. I tried taking the wireless security off and going to WEP and it did not work.

With all due respect, I don't think that you're understanding what my problem is. There is NO problem with the wireless. We are connecting to the router just fine, there has never been a problem with that. My problem is that the router is not staying connected to the internet if I plug in directly into our source. Our complex provides internet. We just plug into the wall. So what I'm thinking is that our source is doing something that is messing with the router.
 
#17 ·
Alright....got it now, things can be confusing sometimes.
Since your Apartment is providing the Internet, the Belkin router that you're trying to configure to connect to the WAP has DHCP Enabled. Have you disabled DHCP from your Belkin Router and use a Static IP within the WAP's DHCP Range?

Before I proceed with further instructions, I think it's best for you to get a permission from your Landlord to add second Router. If you have your own subscription from the ISP, you're free to do anything, since it's your Apartment's WAP, it will be nice to ask for permission.
 
#20 ·
No there are not two sources. Our complex provides internet via a wired network. We just plug into the wall. What I meant by "we just got the internet turned on" is that they did whatever it was that they needed to do to let us plug in and get internet. We only get internet provided by the complex if we sign up for a year contract. When I moved in we were at the end of a 6 month contract which does not include internet.
 
#22 ·
Sorry didn't see that one. I'll try that tomorrow. I've got friends over right now using the wireless I rigged up. One thing, though, is that we have people all around us who have no problems with their routers hooked up like we are trying to. And my roommate had previous roommates that had a router that had no problems with the apartment internet. I'm going to ask a friend if I can borrow his router and see what happens along with trying what you asked in 17. But I think I'm getting tired of fiddling with this stupid thing and you guys are probably getting tired of trying to understand me. I really do appreciate your patience though. I've seen many forums where the people are very rude and impatient to those who don't know much about computers. You guys have been great!:pray:
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top