|
|
|
I have just bought a Billion 7700N router to replace my failing Netgear DGN2000.
Having followed all the instructions I just cannot make any connection to it either by the Wizard or the browser. Have tried my working Netgear LAN cable as well as the supplied and one other that I have.
I am using the address 192.168.1.254 as per manual, also read elsewhere that 169.254.82.196 can be used to get into it.
Tried the other computer but to no avail.
I use fixed addresses but have reset them to auto and still no luck.
Tried the reset button.
Lights on are Power, LAN1, WLAN, DSL when the cable is connected but trying it without at the moment as I don't wish to disconnect from the internet continually.
Any suggestions please. I have seen this problem raised elsewhere but no cure.
|
|
|
With the PC connected, open a command prompt and enter
route print 0.0.0.0
The router IP address should be shown under gateway.
Edited by deleted (Sat 10-Nov-12 15:08:06)
|
|
|
Is your PC configured to get its IP address automatically? Or have you manually set one in the past, and the Billion is using a different IP range
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
|
Thanks
Setting it back to DHCP no routes are found - so reckon it is dead then?
|
|
|
Is your PC configured to get its IP address automatically? Or have you manually set one in the past, and the Billion is using a different IP range
Usually on static routes but reverted to auto, the wizard anyway seemed to do this. Have only used Netgears in the past and they were simple to set up.
|
|
|
|
Well, the DHCP server isn't giving an IP address to the PC anyway. Maybe just a configuration issue.
|
|
|
The billion should be the same really, i.e. simple enough
If DHCP is not working, then try a reset of the router. And if that does not work try manually setting the IP figures to be one in the appropriate range
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
The billion should be the same really, i.e. simple enough
If DHCP is not working, then try a reset of the router. And if that does not work try manually setting the IP figures to be one in the appropriate range
I have tried all that and nothing happens.
It seems that DHCP is not working on this machine even for the Netgear. I did have it disabled under Services but have re-enabled that and DNS, also anything else that seemed relevant. Rebooted several times.
When using it in auto the network icon shows and error and is asking for an address. I have set an address for the network card but that does not seem to help.
Any ideas please.
|
|
|
So as the Netgear is broke too points at PC, how do you normally use the connection?
IP settings that should work based on router IP earlier
IP 192.168.1.10
Subnet 255.255.255.0
Gateway and DNS 192.168.1.254
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
So as the Netgear is broke too points at PC, how do you normally use the connection?
IP settings that should work based on router IP earlier
IP 192.168.1.10
Subnet 255.255.255.0
Gateway and DNS 192.168.1.254
It is not completely broken - I am using it for this.
Two of the LAN ports were showing orange instead of green but since it has seen the new one they are working correctly again, but I guess it may fail again - hence the reason for the new one.
I will try those settings above and see what gives.
I the meantime I have used my Linux computer and set it up for DHCP and that will not connect either.
I discovered that when I used the wizard on the CD it automatically sets the computer to DHCP.
Thanks for your advice.
|
|
|
|
Are you trying to connect to the billion whilst connected to the netgear? If so then netgear normally defaults to 192.168.0.1 and billion is 192.168.1.254 - whilst on one you won't see subnet of the other.
You need to shutdown the netgear and let the pc get the IP address from the billion. Then you should be able to get at it.
|
|
|
So as the Netgear is broke too points at PC, how do you normally use the connection?
IP settings that should work based on router IP earlier
IP 192.168.1.10
Subnet 255.255.255.0
Gateway and DNS 192.168.1.254
Thank you - as soon as I saw that I realised what I was doing wrong, though I did not know you could not cross realms (if that is the correct word - probably not).
The router is now up and running on my preferred settings.
I do appreciate the effort that goes into this forum making it the success it is.
|
|
|
Are you trying to connect to the billion whilst connected to the netgear? If so then netgear normally defaults to 192.168.0.1 and billion is 192.168.1.254 - whilst on one you won't see subnet of the other.
You need to shutdown the netgear and let the pc get the IP address from the billion. Then you should be able to get at it.
Thanks
I wasn't using the Netgear for access but direct from the computer but it seems that I cannot access 192.168.1.xxx from 192.168.0.xxx
|
|
|
|
I think the word is subnet. You can't access them because of the Subnet mask being 255.255.255.0. Now if the mask was 255.255.192.0, then you may be able to but that's another story.
|
|
|
Where you say realm we say subnet
The linking between two is usually the job of a router, or some nifty configuration of the PC, the sort of thing that is not advised unless you know what /24 means
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
I think the word is subnet. You can't access them because of the Subnet mask being 255.255.255.0. Now if the mask was 255.255.192.0, then you may be able to but that's another story.
Thanks - will try to remember that.
|
|
|
Or even 255.255.254.0 for those two subnets.
Comms is hard 
|
|
|
|
True, but I chose that one because it looks significantly different.
|
|
|
Where you say realm we say subnet 
The linking between two is usually the job of a router, or some nifty configuration of the PC, the sort of thing that is not advised unless you know what /24 means
Ok - still think this is all black magic.
|
|
|
Lol - don't worry still get confused some days here.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|