[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re: [OT]ish Router +modem problem
Hi Peter,
The numbers have changed since January and now seem to make sense.
The routing table did not display properly and I'll try formatting how
I think it should look:
Destination Mask Gateway Metric Active
192.168.1.0 255.255.255.0 192.168.1.1 1 Yes
192.168.2.0 255.255.255.0 192.168.2.102 1 Yes
0.0.0.0 0.0.0.0 192.168.2.101 1 Yes
I would quibble that the final "Metric" value in the routing
table is
wrong because it's two hops away from the Internet, not 1, but I don't
think that's the problem.
I'd be interested in the output from TRACERT on the PC for both
gateway address and an internet address, e.g.:
tracert -h 4 192.168.1.1
tracert -h 4 192.168.2.101
tracert -h 4 212.58.246.94
Also if the modem has an option to turn off NAT then do so.
Interesting the logs confirm that the router is talking to the
Internet because DYNDNS is sending you an error message:
Sat, 08/27/2011 02:41:16 - DYNDNS.ORG: The update changed no settings, and
is considered abusive.
You ought to
a) Check that you have the latest router firmware that handles dyndns
corre=
ctly.
b) Disable the routers dyndns settings before doing too many reboots
otherwise dyndns will block your account.
Nick.
--=20
On Sat, Aug 27, 2011 at 12:06 PM, Peter Church <yahoo@xxxxxxx> wro=
te:
> Hi all (Nick especially!)
>
>
>
> I parked this thread a while back because I couldn't make changes to
the
> system at the time but I'm now back with it and have another week here
to
> try to fix it.
>
>
>
> A quick recap - I'm trying to set up a remote network and I cannot get
th=
e
> LAN to connect to the web via a Netgear Router/Firewall and a 3G
modem. =
=A0It
> should be a simple plug and play problem but isn't! I understand
enough t=
o
> know this should work, but not enough to fix it! I've added some logs
and
> parameters =A0at the end of this note.
>
>
>
> I'm happy to take this offlist if someone can help me out as I know
this
> isn't really the place for it, but most of us here have some
networking
> experience - and the ultimate aim is to control Comfort, DVR and
1-wire i=
n a
> holiday home from remote locations so ultimately HA!
>
>
>
> Thanks in advance
>
>
>
> Pete
>
>
>
> Modem WAN:
>
> IP Address: =A0 =A0 =A0 =A0 92.251.xx.xx
>
> DNS Server: =A0 =A0 =A0 =A083.136.47.249
>
> =A0193.120.14.101
>
>
>
> Modem LAN
>
>
>
> IP Address: =A0 =A0 =A0 =A0 192.168.2.101
>
> Subnet Mask: =A0 =A0255.255.255.0
>
> DHCP Server: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Enabled
>
> Start IP Address: =A0 =A0 =A0 =A0 =A0 =A0 =A0192.168.2.102
>
> End IP Address: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0192.168.2.200
>
> DHCP Lease(s): =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 86400
>
>
>
> Router WAN
>
> Connection Method =A0 =A0 =A0 Dynamic IP
>
> IP Address =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0192.168.2.1=
02
>
> Network Mask =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0255.255.255.0
>
> Default Gateway =A0 =A0 =A0 =A0 =A0 =A0 =A0192.168.2.101
>
> DHCP Server =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0192.168.2.101
>
> Lease Time =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 86400
>
> Domain Name Server =A0 =A0 192.168.2.101
>
>
>
> Router LAN
>
> IP Address =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0192.168.1.1
>
> DHCP =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =
=A0 DHCP Server
>
> IP Subnet Mask =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0255.255.255.0
>
>
>
> PC IPconfig
>
>
>
> Ethernet adapter Local Area Connection:
>
> =A0 DHCP Enabled. . . . . . . . . . . : Yes
>
> =A0 Autoconfiguration Enabled . . . . : Yes
>
> =A0 Link-local IPv6 Address . . . . . :
> fe80::f1fd:9e5b:70a9:2d8c%11(Preferred)
>
> =A0 IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
>
> =A0 Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> =A0 Lease Obtained. . . . . . . . . . : 27 August 2011 10:34:43
>
> =A0 Lease Expires . . . . . . . . . . : 30 August 2011 10:51:43
>
> =A0 Default Gateway . . . . . . . . . : 192.168.1.1
>
> =A0 DHCP Server . . . . . . . . . . . : 192.168.1.1
>
> =A0 DHCPv6 IAID . . . . . . . . . . . : 240920074
>
> =A0 DHCPv6 Client DUID. . . . . . . . :
> 00-01-00-01-15-5F-74-9B-5C-26-0A-55-3D-87
>
>
>
> =A0 DNS Servers . . . . . . . . . . . : 192.168.1.1
>
> =A0 NetBIOS over Tcpip. . . . . . . . : Enabled
>
>
>
>
>
> I also rebooted the router and this is what the initial Security Log
show=
s
> (I can't seem to see any other logs to see if they give any other
details=
)
>
> Sun, 01/01/1900 00:00:00 - Netgear Activated.
>
> Sun, 01/01/1900 00:00:00 - Successful administrator login -
> Source:192.168.1.2, 62287, LAN - Destination:192.168.1.1, 80, LAN
>
> Sun, 01/01/1900 00:00:00 - DYNDNS.ORG: Starting update!!
>
> Sat, 08/27/2011 02:41:16 - Get NTP Time: Sat, 08/27/2011 02:41:16
>
> Sat, 08/27/2011 02:41:16 - DYNDNS.ORG: The update changed no settings,
an=
d
> is considered abusive.
>
> Sat, 08/27/2011 02:41:24 - TCP connection dropped -
Source:212.161.8.3, 8=
0,
> WAN - Destination:192.168.2.102, 16488, LAN - 'Suspicious TCP Data'
>
> Sat, 08/27/2011 02:41:30 - TCP connection dropped -
Source:79.107.138.124=
,
> 50057, WAN - Destination:192.168.2.102, 80, LAN - 'WEB'
>
> Sat, 08/27/2011 02:41:36 - TCP connection dropped -
Source:83.132.250.182=
,
> 1441, WAN - Destination:192.168.2.102, 80, LAN - 'WEB'
>
> Sat, 08/27/2011 02:42:00 - TCP connection dropped -
Source:193.109.81.89,
> 443, WAN - Destination:192.168.2.102, 18942, LAN - 'Suspicious TCP
Data'
>
> End of Log ----------
>
>
>
> Also a Routing Table from the Router:
>
>
> Destination
>
> Mask
>
> Gateway
>
> Metric
>
> Active
>
>
> 192.168.1.0
>
> 255.255.255.0
>
> 192.168.1.1
>
> 1
>
> Yes
>
>
> 192.168.2.0
>
> 255.255.255.0
>
> 192.168.2.102
>
> 1
>
> Yes
>
>
> 0.0.0.0
>
> 0.0.0.0
>
> 192.168.2.101
>
> 1
>
> Yes
>
>
>
> Other thing to note:
>
>
>
> When I connect either a PC or a LAN port of the router directly to the
mo=
dem
> the modem RJ45 lights are both on as orange on, green flashing,
whereas w=
hen
> I connect the Internet port of the router to the modem I just get one
lig=
ht
> the green flashing.
>
>
>
>
>
> From: ukha_d@xxxxxxx [mailto:ukha_d@xxxxxxx] On Behalf Of
> Nick Austin
> Sent: 08 January 2011 12:31
> To: ukha_d@xxxxxxx
> Subject: Re: [ukha_d] Re: [OT]ish Router +modem problem
>
>
>
>
>
> Peter,
>
> Well those numbers look good but the DNS is a bit odd. It should work
> but I would of thought that the FVS318 router had it's own DNS server
> (for the LAN ports) and DNS client (for the WAN port) in which case
> the PC should be using a DNS of 192.168.1.1. Even if the DNS isn't
> working you should still be able to access the web via IP addresses so
> something else must be wrong. The logs will probably reveal all when
> you next have access..
>
> Nick.
>
> On Sat, Jan 8, 2011 at 9:47 AM, Peter Church <yahoo@xxxxxxx
> <mailto:yahoo%40petechurch.co.uk>
> wrote:
>> Nick,
>>
>>
>>
>> Sorry I can't actually make any configuration changes as this is
the
> remote
>> system and I won't be with it for another few weeks. =A0What I do
rememb=
er
> was
>> that the (Windows XP) PC is getting
>>
>>
>>
>> DHCP enabled =A0 Yes
>>
>> Autoconfig =A0 =A0 =A0 =A0 Yes
>>
>> IP =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 192.168.1.2
>>
>> Subnet =A0 =A0 =A0 =A0 =A0 =A0 =A0255.255.255.0
>>
>> Default Gateway 192.168.1.1 (the router)
>>
>> DHCP Server =A0 =A0 192.168.1.1 (the router)
>>
>> DNS Servers =A0 =A0 =A0192.168.3.1 (the modem) & 192.168.3.2
(the modem =
+1 which
>> is odd)
>>
>>
>>
>> I might need to park this thread and pick it up again when I am
near the
>> system. =A0It just seemed odd to me that a router cannot sit
behind a mo=
dem
> as
>> surely that is what a router is designed to do, so I thought there
might
> be
>> a very straigntforward answer
------------------------------------
<*> Join the Automated Home Forums
http://www.automatedhome.co.uk/vbulletin/
UKHA_D Main Index |
UKHA_D Thread Index |
UKHA_D Home |
Archives Home
|