Local Access Only Issues

[HardCorePawn]

Excellent news... networking issues are a real hassle to diagnose and fix without being there!

[Ian Warren]

QUOTE (HardCorePawn @ Nov 21 2008, 11:13 AM) <{POST_SNAPBACK}>

... networking issues are a real hassle to diagnose and fix without being there!

Jared , maybe a 'Flying PC Doctor' service when trouble strikes .. call the FPCD !

[HardCorePawn]

"Victor Charlie Charlie to Mike Sierra Foxtrot..."

Was one of the few TV shows that my mum watched that I actually liked... only for the aircraft and the dodgy looking dirt strips!

[Ian Warren]

QUOTE (HardCorePawn @ Nov 21 2008, 11:19 AM) <{POST_SNAPBACK}>

Was one of the few TV shows that my mum watched that I actually liked... only for the aircraft and the dodgy looking dirt strips!

Just for interest sake .. they only had one Nomad and that was the star of that show , it displayed at the 1988 Bicentennial Airshow , now been sold on , maybe be a superb choice to fly into the crowded streets in Auckland or all over New Zealand to save PC's ....... thank god for the FPCD service

[ardypilot]

Uh oh HCP- just when I thought it was smooth sailing, I can't actually access the internet on my FS PC yet... I am able to get into the router back end and share files between it and my laptop, however it looks like it's 'local access only again'.

Is it possible to just enter some custom fields into the Internet Protocol (TCP/IP) properties boxes with like a slightly different IP address or something similar to fix this?

[HardCorePawn]

OK.... FS PC is connected via cable? Can you put up a screenies of:

- Router backend - LAN config page and DHCP settings
- IPconfig results on FS PC

[ardypilot]

Yep its on a ethernet cable- here's the screenies:





Cheers.

[NZ255]

Can't somebody use these IP addresses and numbers to get into and use your (Trolly's) internet?

[Alex]

Not easily at least. These addresses are only used on Andrew's local network - you'd have to already be a part of his local network to really use them.

Alex

[HardCorePawn]

as Alex said, those IP addresses are useless to anyone not on Andrews local network... 192.168.x.x is a reserved range for private networks (like 10.x.x.x)

Back to the matter at hand...

Andrew, can you try a quick test for me... do the 'cmd' thing and try these commands:

ping www.google.co.nz
ping 209.85.173.103

I am guessing that the first one will result in something like "Unable to resolve address"... and the second will hopefully return a whole bunch of lines that look something like:

Reply from 209.85.173.103: bytes=32 time=211ms TTL=232
Reply from 209.85.173.103: bytes=32 time=208ms TTL=232
Reply from 209.85.173.103: bytes=32 time=208ms TTL=232
Reply from 209.85.173.103: bytes=32 time=210ms TTL=232

[ardypilot]

???

[HardCorePawn]

interesting... you should have access to everything you need... it is resolving www.google.co.nz and returning pings, so you are definitely connected to the interwebs...



So you cannot connect to anything via your web browser?

[ardypilot]

QUOTE

So you cannot connect to anything via your web browser?[/quote]
Unfortunately not, every URL I enter in either Mozilla or IE just shows 'connecting to...' in the status bar, then times out after a few seconds.

My anti virus programs and Active Sky both refuse to update themselves also..

Last edited by ardypilot on Mon Nov 24, 2008 1:14 pm, edited 1 time in total.

[ardypilot]

Update- after reading that last post, I thought hold on, it's proberly just my firewall blocking it, so I disabled zone-alarm and now everything is sweet. (I'm typing this message from my FS PC).

I just need to restart ZA now and let it allow the new connection through there- problem solved, thanks for your continued help Jarred!

[HardCorePawn]

Ahhh... the old "My firewall ate my internet" trick...