Messages

This will however mean that when the Topfield is turned on from standby no guide data will be seen until the Topfield has been powered up for 1 minute.

Daniel..... The new tap is great..............., but having to wait a full minute for the EPG to load is 'just' acceptable.

I loaded up the new TAP tonight, my wife turns on the toppy and she queries me, 'what's wrong with the pvr? I can't see what's on'.

I replied, I didn't know, I checked the announcement for the TAP and found the answer.

Any plans on increasing the speed of the EPG load on startup? Would love to have it back to normal!

Cheers.

Hi Peter,

Again thanks for the quick reply. We'll I tried the full reset and I still receive a timeout when trying to hit 192.168.1.17 address.. I followed your instructions to the letter with no joy... IE basically times out.. As said, I'll send the unit back to Syndey tomorrow and will hopefully get it back before the wkend!!????

There is at least one issue I can see already, both your laptop and access point are using 192.168.1.1 as their IP. That means the entire network is unstable.


Opps, that was a typo on my behalf... The current laptop IP is getting assigned a valid IP via DHCP. No conflicts are currently present on the network.

When I get the unit back, i'll carefully follow the instructions as specified and I'll set the network up now to work serve DHCP in the range 192.168.1.100 - 192.168.1.200.

I'll leave the static ip/dns/gateway settings alone!  :-[

Again thanks for the help!

Cheers,
Bennie.

Hi Peter,

Thanks for the quick reply. I think personally I've made three seperate errors. The first two were definately my fault however I would have thought that the third attempt would have worked.

Here's the setup:

Wireless Access Point : Billion 7402VGP Router
PC : D-Link DWL-G122 (USB Wireless connection to my billion router)
Laptop : Work laptop connect wireless from anywhere in the house

Originally the default IP for the AP was 192.168.1.254
Netmask : 255.255.255.0

DHCP is turned on.

The only firewalls that are currently utilised are software based types ( Symantec - Internet Security 2004 ).

The subnet range is from 192.168.1.1 ---> 192.168.1.20

The AP is now set to 192.168.1.1 ---- Both my PC and laptop connect to the access point via the SSID "WirelessNetwork". One problem that may have caused an issue was having a space in the SSID this has now been resolved. 128 bit static WEP keys are utilised to key the network (semi-secure)... Growl.... Why can't we have WPA????? Would be great to have!

So the laptop and the PC respectively are assigned 192.168.1.1 and 192.168.1.2

After the first two failed attempts of me entering in 'totally' wrong addresses into the IP/DNS and gateway settings Daniel and I attempted to set it up the third time.

I disconnected everything and plugged the AP directly into the back of my PC and then plugged the netgear into the AP as well.

The netgear was assigned an ip of 192.168.1.3 and the gateway/dns were pointed to 192.168.1.1

I couldn't get back in. I've tried every combination of trying to get back into the thing. Directly plugged into the AP, into the laptop, I've turned even tried turned off DHCP and assigned manual IP's to the other devices, to no avail. And to think that I'm a java programmer... Aarrrgghhh!

So when i get home tonight. I'll try the information from your second message about doing a full-reset on the netgear and see if i can get it back. If so need be I'll send it back to Sydney to get reflashed and then try the DHCP option.

Thanks for your help.

Cheers.

Hiya,

Ok, I've had a few problems setting up my netgear still to no avail... I've spoken to the Daniels at ICE and I must thank them for their efforts so far!

Here's the story.... Um..... Three times I've locked myself out of the netgear. Twice i've sent it back to Sydney to be reflashed. Hopefully not a third time.

Here's the scenario....

I have a Wireless Access point that was originally sitting on 192.168.1.254.....

The third time in trying to set this up and talking with Daniel we unfortunately pointed the unit to a static IP address of 192.168.1.3 and the dns/gateway settings at 192.168.1.1

We Daniel and I realised our error, we changed the IP of the access point to 192.168.1.1

When I try and access the 192.168.1.17 all get is timeouts when trying to connect.

The parameters for the install are:

WEP key (128bit) enabled (hex characters only)
Pointing to the right SSID.... no problems there.

When I connect the unit to the back of my router I can see it come up on the connected ethernet devices as icebox66

But still no connection via the wireless componet.

Is there any way I can get access to my unit. Or will I have to send it back to Sydney (boo hoo....)

The next time I think i'll try the standard DHCP settings again. Does the hard-coding of the dns/gateway perm. lock me out from resetting this device?

Any help would be great!

Cheers.