You need to be connected on the internet to download files.. (077 RC2)
#1
Posted 04 August 2009 - 08:51 AM
Can anyone help with this error
I am connected to the internet, but it doesn't matter whether I run this version or 077 RC1, 077 Beta 3 etc it keeps telling me I need to be connected to internet when I am
Running it on Windows 7 RC build 7100
#2
Posted 04 August 2009 - 09:26 AM
#3
Posted 04 August 2009 - 11:44 AM
yes AVG internet security, but tried disabling it and same problemis there any AV-firewall? I had it also on Vista sp0 with WB 0.77rc2,
#4
Posted 04 August 2009 - 07:17 PM
#5
Posted 04 August 2009 - 08:01 PM
no not using a proxy - works fine on my XP machine, but under win7.7100.x86 keep getting that same error and can't downloadI have no problems running winbuilder 77 rc2 on win7.7100 x64. I can download files with winbuilder. Are you using a proxy?
#6
Posted 06 August 2009 - 09:51 PM
Cannot use RC2 at all.
I have Eset smart security, and tried RC2 with the security/firewall disabled and still have that message,
It just will not do anything other than try and tell me I have no connection to the internet
Had to go back to using 076.
#7
Posted 06 August 2009 - 10:16 PM
glad I am not the only one, hopefully someone will listen now and try and fix the issueI have tho problem also
Cannot use RC2 at all.
I have Eset smart security, and tried RC2 with the security/firewall disabled and still have that message,
It just will not do anything other than try and tell me I have no connection to the internet
Had to go back to using 076.
#8
Posted 07 August 2009 - 02:31 AM
Maybe it does not like the UK.
#9
Posted 07 August 2009 - 07:41 AM
yes I live in the UK.
I have a pc with intel q6600 processor 4gb ram
a dual boot system, 2 hard drives.
1 hard drive has windows 7 x64 on it
2nd hard drive has Vista X86 which is where ALL winbuilder work is done.
There is nothing on the drive other than nero burning rom, winbuilder program/tools and VMware player.
Eset smart security which is not blocking anything, I get the same error message with Eset turned off and disabled.
#10
Posted 08 August 2009 - 03:41 AM
Did you try going to the Tools / Options tab. Try tweaking some of the Network Support Options.
#11
Posted 08 August 2009 - 08:32 AM
I only use winbuilder when the computer is booted up as a Vista X86 machine, and yes the network works perfectly on everything other than winbuilder 077
See
#12
Posted 08 August 2009 - 04:11 PM
Try in CodeBox:I don't use winbuilder on the X64 drive or windows 7.
I only use winbuilder when the computer is booted up as a Vista X86 machine, and yes the network works perfectly on everything other than winbuilder 077
If,PING,www.google.com,Echo,OK! Else,Echo,NOK!
Peter
#13
Posted 08 August 2009 - 04:15 PM
Try in CodeBox:
If,PING,www.google.com,Echo,OK! Else,Echo,NOK!
Peter
Then, try:
If,PING,74.125.53.99,Echo,OK! Else,Echo,NOK!
just in case the problem is in the DNS....
jaclaz
#14
Posted 08 August 2009 - 04:24 PM
Tried this, but cannot see where it is Echoing the OK or NOK too? as it doesn't show in log after running script in codebox?Try in CodeBox:
If,PING,www.google.com,Echo,OK! Else,Echo,NOK!
Peter
#15
Posted 08 August 2009 - 04:34 PM
Tried this, but cannot see where it is Echoing the OK or NOK too? as it doesn't show in log after running script in codebox?
The 'executed' Echo is that one with the 'i' icon
The 'not executed' Echo is that one with the cross icon (greyed in log.html)
But you also should see 'ping got answer' or 'ping got no answer' in the log.
Peter
#16
Posted 08 August 2009 - 05:28 PM
script entered in code box as shown in screenshot ping 1The 'executed' Echo is that one with the 'i' icon
The 'not executed' Echo is that one with the cross icon (greyed in log.html)
But you also should see 'ping got answer' or 'ping got no answer' in the log.
Peter
log shown in screenshot ping 2
no i or cross, and no "ping got answer" or "ping got no answer" either in log?!?!?!?
Attached Files
#17
Posted 08 August 2009 - 06:28 PM
This is my result with 077 RC2 on an XP SP3 host:
Something is different with your local installation.
Maybe you download WB 077 RC2 into a fresh directory and try again.
If the troubles remain, let's decide that it depends on your W7 RC1 (which is really not yet declared as stable)
Peter
EDIT: I tried on Win7 RC1 64 bit German. Log is the same like the above picture.
#18
Posted 08 August 2009 - 06:53 PM
I've been a bit foolish not to see that.
Your CodeBox snippet cannot run, because it is not in a [process] section.
You need:
[process] If,PING,www.google.com,Echo,OK! Else,Echo,NOK!
Peter
#19
Posted 08 August 2009 - 07:01 PM
whoops, my mistakeOOPS!
I've been a bit foolish not to see that.
Your CodeBox snippet cannot run, because it is not in a [process] section.
You need:[process] If,PING,www.google.com,Echo,OK! Else,Echo,NOK!
Peter
I now get NOK for both ping by ip and name
File [%BaseDir%\Projects\win7pe\CodeBox.txt] Version [1]
IF - Ping got no answer [www.google.com] evaluated string: [If,PING,www.google.com,Echo,OK!]
ELSE - executing command: [Echo,NOK!]
NOK!
IF - Ping got no answer [74.125.53.99] evaluated string: [If,PING,74.125.53.99,Echo,OK!]
ELSE - executing command: [Echo,NOK!]
NOK!
Finished processing script: %BaseDir%\Projects\win7pe\CodeBox.txt
Script time: 95 miliseconds
Script has been sucessfully processed!
but I can ping by IP and name from command prompt fine
Microsoft Windows [Version 6.1.7100]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Users\Darren Rose>ping www.google.com
Pinging www.l.google.com [209.85.227.104] with 32 bytes of data:
Reply from 209.85.227.104: bytes=32 time=48ms TTL=40
Reply from 209.85.227.104: bytes=32 time=46ms TTL=40
Reply from 209.85.227.104: bytes=32 time=47ms TTL=40
Reply from 209.85.227.104: bytes=32 time=45ms TTL=40
Ping statistics for 209.85.227.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 48ms, Average = 46ms
C:\Users\Darren Rose>ping 74.125.53.99
Pinging 74.125.53.99 with 32 bytes of data:
Reply from 74.125.53.99: bytes=32 time=175ms TTL=43
Reply from 74.125.53.99: bytes=32 time=174ms TTL=43
Reply from 74.125.53.99: bytes=32 time=171ms TTL=43
Reply from 74.125.53.99: bytes=32 time=170ms TTL=43
Ping statistics for 74.125.53.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 175ms, Average = 172ms
C:\Users\Darren Rose>
#20
Posted 08 August 2009 - 07:26 PM
I'm currently not sure,l but even if you say thatb there is no proxy, I#m in doubt whether there are some M$ firewall activities.
Peter
#21
Posted 08 August 2009 - 07:32 PM
then run the 'WinBuilder.exe' i get these:
on XP SP3 host, no third party antivirus or firewall installed, no proxy used
Edit:
the built-in XP firewall is enabled
maybe these errors caused by the fact:
nowadays at me in Hungary the servers usually are not available at the first time (have to try to connect more times)
e.g. www.boot-land.net, livexp.boot-land.net, vistape.winbuilder.net etc.
but finally i am able to download a project after many-many try
Edited by dera, 08 August 2009 - 07:51 PM.
#22
Posted 08 August 2009 - 08:38 PM
right I understand nowThe difference is that M$ Ping uses information and functionality of M$ Internet Explorer, while since WB 077 beta WinBuilder uses Indy functions independent from IE.
I'm currently not sure,l but even if you say thatb there is no proxy, I#m in doubt whether there are some M$ firewall activities.
Peter
all very strange, ms firewall disabled, AVG internet security installed, but tried with it disabled/removed too
Checked all settings, and I work in IT so have thoroughly checked everything
#23
Posted 08 August 2009 - 11:50 PM
It seems to me there were far less problems with internet access with winbuilder when MS functionality was used. However maybe that's my imagination.
#24
Posted 09 August 2009 - 06:06 AM
But at home connected via Wireless it won't download, complaining it is not connected to the internet even if I disable the other interfaces).
Megaduck99
#25
Posted 21 August 2009 - 03:36 PM
I've a similar problem as obviously Winbuilder 77 doesn't recognize an internet connection through my proxy. It seems that Winbuilder uses a ping to detect the online state and ping is regulary prohibited by professional firewalls. I suggest to use something like this:
Echo.
Echo *** Check Internet connection
netsh diag ping dns|find "TTL=" > nul
if errorlevel 1 goto _NoConnection
netsh diag ping gateway|find "TTL=" > nul
set connected=Yes
Echo connected
goto _search_appl
:_NoConnection
set connected=No
Echo !!! not connected
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users