SmartCode Solutions Web Forum

Hi...

Can anyone help me understand VNC Managers Wake-On-LAN implementation?

I have numerous PC's that I can easily wake up with other WOL utilities... however no matter whta settings I use... VNC Manager wont wake the PC's up...

I've never seen a WOL utility that asks for server/client IP's... and Port numbers! It's usually just MAC addresses...

Can anyone explain? Point me at a website or something?

Many thanks in advance,

Mark.

Mark,
I'm probably won't be able to tell why it's not working in your case. But at least I'll be able to answer on other questions.

Port is required feature of WOL functionality. I guess the tool you use just uses a default value. But actually the port value might have different values.
The IP address is not needed for WOL at all. We asks to enter it, so VNC manager could lookup a MAC address for you (well this works for online PC's only, but once you enter MAC manually or look-up for it. The MAC value will be remembered and won't be asked again). We actually redesigned this dialog in v3.0 and made it more powerful.

You can take a look on WOL tool from AMD, it also asks for port number.

Hmmm...

I understand the port number aspect now....

Still not clear why VNC Manager doesnt work...

I have used both AMD's and a command line WOL utility to wake my PC's up 100% succesfully...

However when I use VNC Manager nothing happens...

Any idea's at all?

Thanks.

Mark.

Hi... Thats ok...

My mistake... I was misreading the field names in the dialog box...

With the correct info in each field it is now working as expected!

Thanks for the reply.

Regards,

Mark.

Would you be able to tell us how you were confused on the input fields?  Is there a way to word the fields better?

Adam

Hi...

Sorry for the slow reply... work!

I do love this program... but does anyone else find it frustrating that it crashes so frequently?

Just establishing and closing VNC/RDP sessions causes it to crash at least once or twice a day for me... if not more...

(I do use it frequently)...

Anyway... back to wake on LAN....

The fields are currently labelled:

Server address (This is probably what threw me... I can never envisage using WOL on a 'server'... clients yes.. not servers... so maybe this should be called 'Client address for MAC lookup'... just to make it VERY clear what it's for)...

MAC Addresss... (The key field obviously and very fairly named!)...

IP broadcast Address... (this one also got me... after being thrown by 'server address'... I was looking for a field to enter an IP to lookup... and just saw this... my brain completely ignored the 'broadcast' part)....

Port Number... (as has been pointed out this is perfectly valid WOL field... I have just never seen before... I assume because most utils and clients assume port 7)...

I was basically being too hasty... if you read every properly... and have your head around how WOL works... it all makes sense...

So... 1st field for IP to lookup (if needed)...

2nd is the MAC of the client you want to wake...

3rd is something like 192.168.16.254 (A multicast address to aim at a parituclar subnet)...

and the 4th is best left as 7 unless you've really got deep into WOL and changed it on your network...

In summary... it works perfectly...

Thanks,

Mark.

Mark,
thanks for detailed description. We actually already redesigned WOL dialog v3.0. Please take a look on a screenshot attached. This is how WOL looks in v3.0.

As for crashes problem. This is long story that started after v2.5 release. Some customers have this crash, some doesn't. None of are developers ever had it, so we are trying to fix it in a kinda blind way. But I thought that the latest 2.5.73.0 release, has much improved the situation. What build you are currently have installed?

Hi...

The screenshot looks great... very much looking forward to v3!

As to crashes... I am running 2.5.73.0.....

And still have them quite frequently... nothing unusual about my setup... one office PC... one home office PC... both Win XP SP2 with all hotfixes...

I should say that rather than 'crash' it freezes... the app locks up completely and I have to 'task manager' out...

Thanks for your help/comments.

Regards,

Mark.