Ask
Reply
Solution
20-12-2023 07:15 PM - edited 20-12-2023 07:19 PM
I have a VF TGH3000 router. The router's IP address is 192.168.0.1, and all other addresses (e/g DHCP range) end in 0.XXX.
Plus a Netgear WGE game adapter, that has a factory default IP address of 192.168.0.202 - you can only change this by connecting to the .202 address, and configuring it.
I connected the WGE to the router via ethernet, and tried to ping it.
C:\Users\David>ping 192.168.0.202
Pinging 192.168.0.202 with 32 bytes of data:
Reply from 192.168.0.199: Destination host unreachable.
Reply from 192.168.0.199: Destination host unreachable.
Reply from 192.168.0.199: Destination host unreachable.
Reply from 192.168.0.199: Destination host unreachable.
OK, why is the reply IP address ends .199, when I was pinginging .202? I noticed the default DHCP range is .2 to .199, so wondered if there's a limit of .199 on other capabilities.
I tried a static DHCP, assigning IP address .202 to the WGE's MAC address. That made no difference.
I contacted VF support (in India). The support agent was useless, she didn't understand the issue and kept asking "Have you tried resetting the router?" even though I'd told her I'd done this several times before calling. She refused to escalate my request to 2nd line suppport who might know more about the router's capabilities/constraints, as "clearly your device is at fault"...
However, even if I don't have the WGE connected, a ping still returns the results above. So I worry that the router IP range only extends up to .199, and that any request for an IP above .199 is converted into a .199 request. Otherwise why would I get the ping results above?
Does anyone else see the same issue ? Just trying pinging 192.168.0.202.
What am I doing wrong ??
20-12-2023 10:52 PM
This is a 19yo kit - it may be time to upgrade. You might also want to reset the WGE too, and then attempt to set it up using the Netgear utility before connecting it to your network - if it still recognises such an ancient device! By default, this device uses WEP security and at best will use WPA(v1) with PSK (I don't know if the THG3000 will even connect to such a device over WiFi), which is all far from ideal!
20-12-2023 11:10 PM
@David00 The IP range of the. THG3000 is from 2 to 254, assuming that the router is on 1. I have used it with devices statically set at numbers higher than 240 without issue. You do have to adjust the IP range settings of the router.
22-12-2023 03:37 PM
Thank you for confirming this. I knew the WGE111 in question was working, I'd tested it using a Netgear DG835G router. But I wanted to be able to configure it from my VF THG3000 router. The reason I'm getting a ping response from 192.168.0.199 is that's the IP of the WiFi access point in the router, and it's responding to the ping (rather than the WGE, as the VF router can't find it). I didn't know that Win 7 and above behaved this way, but found an explanation on the web.
22-12-2023 03:31 PM - edited 22-12-2023 03:31 PM
Yes, you're right. It's old tech. I use pairs of WGE111's in ad-hoc mode to create point-to-point links for music streaming, one at the head end, and one at the amp/speaker end. I'm connecting via ethernet to try and re-configure one of them. Once configured they create a 1-2-1 separate network, ands whether WPA or WEP doesn't really matter.
22-12-2023 03:49 PM - edited 22-12-2023 03:51 PM
Quick update, intended to help anyone else in a similar situation.
I'm able to reconfigure the WGE111 with my "go to" DG834G. I've tried ever which way to do this using the THG3000, but the WGE config utility (via the router...) just couldn't see the WGE at the end of a 1m length of Cat5 UTP. There's some incompatability.
Once configured correctly, I connected the WGE via UTP to an old Roku Soundbridge. The WGE is connected via WiFi (WPA/TKIP) to the THG3000. TheTHG3000 can now see the Soundbridge's MAC address. But the THG3000 isn't responding to a DHCP request to allocate an IP address. I suspect I'll never know the reason why.
22-12-2023 03:52 PM
@David00Do you have time to dig into the logs on the router? There may be an error for the DHCP request. Alternatively, are you sure that the Soundbridge is looking for DHCP at the right address:port?
24-12-2023 03:54 PM
I'v tried to reply to this several times. My reply is posted, and then it disappears. If I try to PM it to you, I get an HTML warning - but it doesn't contain any HTML. If only I knew how to contact a moderator...
24-12-2023 04:38 PM
@David00 Contacting a moderator: Either look in other messages and put their name in the message, or, have the word "moderator" appear in what you type.... Oh, you just did that. One will be along, but it may be a bit like waiting for a bus as it's the festive season.
22-12-2023 08:24 PM
Using the WGE111 is just bringing back bad memories! This is from memory, a very long time ago, and not on my own network. I seem to recall that you had to reset the WGE111 and then access it via it's app or log into the SSID on the WGE111 - logging in via the ethernet port was problematic until you'd done this (possibly it was a subnet issue).