Problem was can't access Google Maps, Google News and Youtube. Found that the Network Address Translator thought 2 devices were addressing it. Solution was to reset Comcast modem and Netgear Ethernet Switcher. So not know a great deal on a NAT I am wondering why this got screwed up?
Announcement
Collapse
No announcement yet.
weard network problem
Collapse
X
-
Re: weard network problem
is it a modem and a network switch? no router? having a network switch on a MODEM and not a ROUTER will attempt to assign PUBLIC ip addresses to your device. Most ISP's only allow one or two public IP's. Having a router (NAT) lets you map the single public IP to several private IP's. If you're using just a switch and a modem with no routing, the different devices connected are going to fight for IP addresses, and it will only assign one or two at a timeCap Datasheet Depot: http://www.paullinebarger.net/DS/
^If you have datasheets not listed PM me
-
Re: weard network problem
So it is a Comcast modem connected with through the Ethernet to to a Belkin wireless Router and that wireless Router is they connected through its Ethernet to a Netgear SW. So the complete description is there is one input line into a Comcast modem which then is connected through the Ethernet to a Belkin wireless router that Router is then connected through it's Ethernet ports to two separate Ethernet switches, one switch for the tenants and one for the staff. If other machines are connected to the wireless router wirelessly I do not know.
Comment
-
Re: weard network problem
Originally posted by stj View Postmy TP-Link stuff never needs a reboot.Things I've fixed: anything from semis to crappy Chinese $2 radios, and now an IoT Dildo....
"Dude, this is Wyoming, i hopped on and sent 'er. No fucking around." -- Me
Excuse me while i do something dangerous
You must have a sad, sad boring life if you hate on people harmlessly enjoying life with an animal costume.
Sometimes you need to break shit to fix it.... Thats why my lawnmower doesn't have a deadman switch or engine brake anymore
Follow the white rabbit.
Comment
-
Re: weard network problem
I can't say that I have any recent experience with any newer enterprise gear but when I was working in networks router reboots were required under certain circumstances every so often when errors accumulated too quickly and they basically ran out of RAM.
Home wifi routers I've used are not without issues, even using DD-WRT. ISP supplied modems also have a need to reboot once in a while in my experience.
Comment
-
Re: weard network problem
I do not know as the problem happened about 4 days after they reprogrammed the computers, after I took one computer over. Then this problem went on for about one week before I figured out what happened. I then convinced the live in manager to open a lock door and restart both the switcher and modem. That took care of the problem, but I figure the problem should not happened in the first place.
Comment
-
Re: weard network problem
To me if this is the case then the people who design and program these devices need to get together and figure out the problem so they do not happen again. Just accepting that this is the case, to me, is not an answer. When I was a technician and a problem occurred we would inform the engineering department. The engineering department would determine if it was created by one or several different areas. If it was several areas they would take 3 engineers and solve the individual areas that created the problem so the problem did not happen again.
Comment
-
Re: weard network problem
Originally posted by Uranium-235 View Postis it a modem and a network switch? no router? having a network switch on a MODEM and not a ROUTER will attempt to assign PUBLIC ip addresses to your device. Most ISP's only allow one or two public IP's. Having a router (NAT) lets you map the single public IP to several private IP's. If you're using just a switch and a modem with no routing, the different devices connected are going to fight for IP addresses, and it will only assign one or two at a time
Comment
-
Re: weard network problem
if it happens again, just reset the modem and see if it fixes it.
a lot of cheap modems / routers have badly written firmware that slowly leaks memory until you have no free ram left.
the Linux based ones are usually fine, it's the ones with less flash that use operating systems like VxWorks that seem to be poorly written.
Comment
-
Re: weard network problem
Originally posted by stj View Postif it happens again, just reset the modem and see if it fixes it.
a lot of cheap modems / routers have badly written firmware that slowly leaks memory until you have no free ram left.
the Linux based ones are usually fine, it's the ones with less flash that use operating systems like VxWorks that seem to be poorly written.
Comment
-
Re: weard network problem
Originally posted by stj View Postif it happens again, just reset the modem and see if it fixes it.
a lot of cheap modems / routers have badly written firmware that slowly leaks memory until you have no free ram left.
the Linux based ones are usually fine, it's the ones with less flash that use operating systems like VxWorks that seem to be poorly written.
I agree that the Belkin router would be better running a Linux-based OS if for no other reason than giving a lot more control of the router, but it may not cure the real problem if it is due to a hardware flaw that cause the memory leak. I've used a Belkin wifi router running DD-WRT but it still needed rebooting now and again. Tweaking parameters to use less memory helps delay running out of memory but it does not prevent it.Last edited by SteveNielsen; 11-16-2015, 06:22 AM.
Comment
-
Re: weard network problem
what are the makes and models of the equipment?
maybe it can be flashed with http://openwrt.org/
Comment
-
Re: weard network problem
Originally posted by SteveNielsen View PostWell, the modem and router are different devices in this situation. He said it was an NAT problem. The router does the NAT, not the modem. I'd reset the router.
I agree that the Belkin router would be better running a Linux-based OS if for no other reason than giving a lot more control of the router, but it may not cure the real problem if it is due to a hardware flaw that cause the memory leak. I've used a Belkin wifi router running DD-WRT but it still needed rebooting now and again. Tweaking parameters to use less memory helps delay running out of memory but it does not prevent it.
Comment
Comment