RE: Re: [OT]ish Router +modem problem

["Peter Church" <yahoo@xxxxxxxxxxxxxxxx>]

Stephen

I don't think that is the problem. The .2. addresses are for the WAN side
of
the router, and the .1. addresses the LAN side.  The router has two
addresses - 192.168.1.1 on the LAN side, and is the DHCP/gateway for the
LAN, whereas the 192.168.2.102 is the IP address given to the router on the
WAN side by the modem.

All IP addresses are given by the DHCP server - none are fixed.

Thanks

Pete

-----Original Message-----
From: ukha_d@xxxxxxx [mailto:ukha_d@xxxxxxx] On Behalf Of
Stephen McGarry
Sent: 27 August 2011 13:29
To: ukha_d@xxxxxxx
Subject: Re: [ukha_d] Re: [OT]ish Router +modem problem

Hi Peter the problem is the PC address is 192.168.1.1 and router is
192.168.2.101 they are on different subnets .1. for PC and .2. for router.
Change the PCs address to 192.168.2.1 and this should fix things. Or select
'get address automaticaly' on the PC.

HTH
Stephen

On 27/08/11 12:06, Peter Church wrote:
> 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
> the LAN to connect to the web via a Netgear Router/Firewall and a 3G
> modem. It should be a simple plug and play problem but isn't! I
> understand enough to know this should work, but not enough to fix it!
> I've added some logs and parameters at 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 in a holiday home from remote locations so ultimately
HA!
>
> Thanks in advance
>
> Pete
>
> Modem WAN:
>
> IP Address: 92.251.xx.xx
>
> DNS Server: 83.136.47.249
>
> 193.120.14.101
>
> Modem LAN
>
> IP Address: 192.168.2.101
>
> Subnet Mask: 255.255.255.0
>
> DHCP Server: Enabled
>
> Start IP Address: 192.168.2.102
>
> End IP Address: 192.168.2.200
>
> DHCP Lease(s): 86400
>
> Router WAN
>
> Connection Method Dynamic IP
>
> IP Address 192.168.2.102
>
> Network Mask 255.255.255.0
>
> Default Gateway 192.168.2.101
>
> DHCP Server 192.168.2.101
>
> Lease Time 86400
>
> Domain Name Server 192.168.2.101
>
> Router LAN
>
> IP Address 192.168.1.1
>
> DHCP DHCP Server
>
> IP Subnet Mask 255.255.255.0
>
> PC IPconfig
>
> Ethernet adapter Local Area Connection:
>
> DHCP Enabled. . . . . . . . . . . : Yes
>
> Autoconfiguration Enabled . . . . : Yes
>
> Link-local IPv6 Address . . . . . :
> fe80::f1fd:9e5b:70a9:2d8c%11(Preferred)
>
> IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Lease Obtained. . . . . . . . . . : 27 August 2011 10:34:43
>
> Lease Expires . . . . . . . . . . : 30 August 2011 10:51:43
>
> Default Gateway . . . . . . . . . : 192.168.1.1
>
> DHCP Server . . . . . . . . . . . : 192.168.1.1
>
> DHCPv6 IAID . . . . . . . . . . . : 240920074
>
> DHCPv6 Client DUID. . . . . . . . :
> 00-01-00-01-15-5F-74-9B-5C-26-0A-55-3D-87
>
> DNS Servers . . . . . . . . . . . : 192.168.1.1
>
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> I also rebooted the router and this is what the initial Security Log
> shows (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,
> and is considered abusive.
>
> Sat, 08/27/2011 02:41:24 - TCP connection dropped -
> Source:212.161.8.3, 80, 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
> modem the modem RJ45 lights are both on as orange on, green flashing,
> whereas when I connect the Internet port of the router to the modem I
> just get one light the green flashing.
>
> From: ukha_d@xxxxxxx <mailto:ukha_d%40yahoogroups.com>
> [mailto:ukha_d@xxxxxxx <mailto:ukha_d%40yahoogroups.com>]
On
> Behalf Of Nick Austin
> Sent: 08 January 2011 12:31
> To: ukha_d@xxxxxxx <mailto:ukha_d%40yahoogroups.com>
> 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>
<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.
> What I do remember was  > that the (Windows XP) PC is getting  >
 >  >
> > DHCP enabled Yes  >  > Autoconfig Yes  >  > IP
192.168.1.2  >  >
> Subnet 255.255.255.0  >  > Default Gateway 192.168.1.1 (the
router)  >
> > DHCP Server 192.168.1.1 (the router)  >  > DNS Servers
192.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. It just seemed odd to me that a router cannot sit behind
a
> modem as  > surely that is what a router is designed to do, so I
> thought there might be  > a very straigntforward answer  >  >
 >  >
> Thanks all for the help.
>  >
>  >
>  > Pete
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  > _____
>  >
>  > From: ukha_d@xxxxxxx <mailto:ukha_d%40yahoogroups.com>
> <mailto:ukha_d%40yahoogroups.com>
[mailto:ukha_d@xxxxxxx
> <mailto:ukha_d%40yahoogroups.com>
<mailto:ukha_d%40yahoogroups.com>
]
> On Behalf Of  > Nick Austin  > Sent: 08 January 2011 08:45  >
To:
> ukha_d@xxxxxxx <mailto:ukha_d%40yahoogroups.com>
> <mailto:ukha_d%40yahoogroups.com>
 > Subject: Re: [ukha_d] Re: [OT]ish
> Router +modem problem  >  >  >  >  >  > Peter,  >
It would probably
> help to post any logs that the router is keeping  > (clear the logs
> first then do a reboot).
>  >
>  > Also if PC is running Windows then what is the output of the
> ipconfig  > /all command?
>  >
>  > Hard to say for certain at the moment if it's a gateway or DNS
or
> routing  > issue.
>  >
>  > Nick.
>
> [Non-text portions of this message have been removed]
>
>


------------------------------------