dreamup prob [ again ]

[alliv]

still no luck

ok i had the box set to
192.168.0.200
255.255.255.0
lan
192.168.0.201
192.168.0.201

network ticked
dhcp unticked
and i think port 80
in web brouser i was typing ftp://192.168.0.2**
so it should be http://192.168.0.2** is that right so far?
thanks once again guys.

ps i had to type ** here because the post wont go tru when i type 200 instead of 2**

[MILLWALLFC]

looks right to me as long as you set both PC and Computer on the same SM 255.255.255.0

[alliv]

right buddy sounds like your going through the wars with this hehehe best to step back at take a fresh look at it

what id do is set your pc to a static ip of
192.168.1.6
255.255.255.0

save it

now on dreambox before you insert the power press and HOLD the button on front of box keep it pressed while u power up

now everything is powered up your gunna have to ping all known ips (should be a post on here on how to find you ip this way) one way that may work is at dos window type ipconfig/all should show whats conected
once you found it open up internet browser and type the dreambox ip (http://192.168.x.x)
fingers crossed

cheers

osborne82

tried all suggested ,still no joy.red light still flashing after holding power button and powering up.

[kagon]

tried all suggested ,still no joy.red light still flashing after holding power button and powering up.

Still no joy meaning you can't even ping it? Get a command prompt and:

ping 192.168.0.200

Get that working before you try anything else.

Also, what's the state of the Dreambox now and what have you done to it to get it into this state?

[alliv]

well i had the 600 working on cli image and wanted to try a different one ,dreamup would not flash. [useing laptop / vista and comport converter ] so i thaught i,d do it as you suggested with telenet. ie
mount -o remount,rw /boot
rm -f /boot/*
reboot
used putty program to do this. i had ip set on the box and i could telenet to the box before this. after putting in the command mount -o remount,rw /boot
rm -f /boot/*
reboot the box went off and came on with red light flashinrg and the odd green flashing light every now and again. now i.m stuck,any idea,s m8? thanks for the reply.also tried restarting the box with power button held down , still no joy.???????

[kagon]

well i had the 600 working on cli image and wanted to try a different one ,dreamup would not flash. [useing laptop / vista and comport converter ] so i thaught i,d do it as you suggested with telenet. ie
mount -o remount,rw /boot
rm -f /boot/*
reboot
used putty program to do this. i had ip set on the box and i could telenet to the box before this. after putting in the command mount -o remount,rw /boot
rm -f /boot/*
reboot the box went off and came on with red light flashinrg and the odd green flashing light every now and again. now i.m stuck,any idea,s m8? thanks for the reply.also tried restarting the box with power button held down , still no joy.???????

Okay, you've got it in a mode now where it will (as far as my experience goes) only accept DHCP. Basically that static IP configuration is now forgotten. So, unless you have a DHCP server on your Windows Vista machine, which I doubt you do, then your best bet is to plug both the Dreambox and your computer in to your router so they can both get DHCP addresses. Once you've done that come back here and let us know what the IP address of your Windows Vista machine is.

[Saruman0]

If you are familiar with DHCP and you can access your router, you can always reduce the scope (available addresses) to two. Then you will know which address your Dreambox has, as your computer will have the other one.

Alternatively, look up an IP scanner to scan all addresses from your computer, this will essentially scan the network you are on to find any addresses in use. One of which will be your dreambox.

Lastly, you can look at your own configuration on your computer e.g. 192.168.0.200 and you can open a command prompt window in vista (click start, type cmd and press return) and then you can start using ping 192.168.0.1, increment by one in the last octet each time until you reach 254. (192.168.0.254) addresses that 'reply' are in use and you can try to open your browser to those addresses, you'll know the dreambox one because it will open to a firmware page.

Best of luck.

[Curious123]

(I think he said in one of his earlier posts that he didn't have a router which is why he is using a cross-over cable.

[alliv]

sorry guys i was working most of the weekend .its 4.40 am so i,ll have a go again in the morning.yep i dont have a router.alptop with vista and comport converter.thanks guys i,m off for a bit of shut eye.

[alliv]

got an ip scanner and scanned from 192.168.0.1 to 192.168.0.255 and only found one alive at 192.168.0.200 but i think this is my own pc as i can get in to the fils at this ip. the odd ip ie.. 164 , 168, 179 came alive but when pinged only came back at 100% or 75% loss and when scanned again they where not there. could it be my network settings? thanks again.

[kagon]

sorry guys i was working most of the weekend .its 4.40 am so i,ll have a go again in the morning.yep i dont have a router.alptop with vista and comport converter.thanks guys i,m off for a bit of shut eye.

Okay, so you're going to need a DHCP server. There is a simple (all we need) open source one available for Windows here:

http://sourceforge.net/projects/dhcp-dns-server/

Grab the Windows installer, install it and make sure to uncheck the "Run Program -- Install as a Windows service" checkbox at the end of installation. As this is a one time thing you don't need it as a Window service.

Next, configure your Windows machine's ethernet interface for:

IP address: 192.168.0.1
Netmask: 255.255.255.0

You can ignore default gateways, DNS servers, etc.

Next, execute Programs --> Dual Server --> Run Stand Alone. This assumes a 192.168.0.1 interface to exist somewhere so it should pick that up.

You should see the following in a terminal window:

...
Server Name: the name of your machine
Domain Name: the name of your domain
Listening on: 192.168.0.1
Lease Status URL: http://192.168.0.1:6789/

Accepting requests...

You can now plug your Dreambox in via the crossover cable and the DHCP server should come up with something like:

Client dreambox offered 192.168.0.2
Client dreambox offered 192.168.0.2 for 360000 seconds

You can check the status of the DHCP server by going to http://192.168.0.1:6789/ in your web browser. It should also tell you the MAC address there, give you the free leases, etc.

Let us know how you get on with that.

[alliv]

got it downloaded, just going to have a go at how to configure it. will keep you posted. thanks kagon.

<--alliv added 65 Minutes and 21 Seconds later...-->

Okay, so you're going to need a DHCP server. There is a simple (all we need) open source one available for Windows here:

http://sourceforge.net/projects/dhcp-dns-server/

Grab the Windows installer, install it and make sure to uncheck the "Run Program -- Install as a Windows service" checkbox at the end of installation. As this is a one time thing you don't need it as a Window service.

Next, configure your Windows machine's ethernet interface for:

IP address: 192.168.0.1
Netmask: 255.255.255.0

You can ignore default gateways, DNS servers, etc.

Next, execute Programs --> Dual Server --> Run Stand Alone. This assumes a 192.168.0.1 interface to exist somewhere so it should pick that up.

You should see the following in a terminal window:

...
Server Name: the name of your machine
Domain Name: the name of your domain
Listening on: 192.168.0.1
Lease Status URL: http://192.168.0.1:6789/

Accepting requests...

You can now plug your Dreambox in via the crossover cable and the DHCP server should come up with something like:

Client dreambox offered 192.168.0.2
Client dreambox offered 192.168.0.2 for 360000 seconds

You can check the status of the DHCP server by going to http://192.168.0.1:6789/ in your web browser. It should also tell you the MAC address there, give you the free leases, etc.

Let us know how you get on with that.

when i run the stand alon prog i get the message..

warning: interface 192.168.0.1 is not static.not used
error: interfaces/listening ports not available, stopped...
press enter

if i press enter it closes down.

[kagon]

got it downloaded, just going to have a go at how to configure it. will keep you posted. thanks kagon.

<--alliv added 65 Minutes and 21 Seconds later...-->



when i run the stand alon prog i get the message..

warning: interface 192.168.0.1 is not static.not used
error: interfaces/listening ports not available, stopped...
press enter

if i press enter it closes down.

Before you start the DHCP server, make sure you have configured your ethernet interface to a static IP of 192.168.0.1 otherwise it won't be able to start up with the default configuration.

[alliv]

i thought i did it but i must have done something wrong. i dont mean to be a pain but whats the best way to do this? i went into the network and sharing and hit properties on lan and then tcp/ipv4 and changed it in there, is this right. i can understand if you have other thing do, thanks for the help so far.

[kagon]

i thought i did it but i must have done something wrong. i dont mean to be a pain but whats the best way to do this? i went into the network and sharing and hit properties on lan and then tcp/ipv4 and changed it in there, is this right. i can understand if you have other thing do, thanks for the help so far.

Can you go to the command prompt and run "ipconfig -all" then copy and paste the results here?