Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread OLE IE container doesn't work in EWB 2 or EWB 3 today... don't know if this is unique to me
Tue, Feb 9 2021 6:46 PMPermanent Link

erickengelke


Microsoft Patch Tuesdays are always scary,.

Today the embedded IE OLE container in EWB 2 and EWB 3 failed for me.  It just displays an empty window when you hit F9 in either EWB.

I don;t know if others see this problem.

I am on a Mac running Windows under Parallels, I don't have access to a non-VM Windows right now... covid and all.

I don't see anything on the Web about it, but it only failed partway through the day, so I may be ahead of the curve.

I had just rebooted, it's got oodles of RAM, and IE runs fine though it gives a startup warning about recommending Edge.   

I can use external browsers just fine, IE, Edge and Chrome all work, but it's an extra step.


Erick
EWB Programming Books and Component Library
http://www.erickengelke.com
Tue, Feb 9 2021 7:51 PMPermanent Link

erickengelke

erickengelke wrote:

> I don't see anything on the Web about it, but it only failed partway through the day, so I may be ahead of the curve.

As you can see in the attachment, it cannot find localhost.

I ran onto a similar problem before on Unix where localhost default assumed IPv6 (which this VM has in addition to IPv4), but did not connect to IPv4.  I don't know if that might be the problem but it looks similar, I don't see EWB listening on IPv6

Hmm,

C:\Users\erickengelke>ping localhost

Pinging ERICKENGELK1E4A [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms


Yep, localhost defaults to IPv6 now!  That seems to be new in Windows update.


Windows IP Configuration

Ethernet adapter Ethernet:

  Connection-specific DNS Suffix  . : localdomain
  IPv6 Address. . . . . . . . . . . : fdb2:2c26:f4e4:0:8d8f:3788:e349:3555
  Temporary IPv6 Address. . . . . . : fdb2:2c26:f4e4:0:206a:3f46:ea34:9b02
  Link-local IPv6 Address . . . . . : fe80::8d8f:3788:e349:3555%4
  IPv4 Address. . . . . . . . . . . : 10.211.55.4
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 10.211.55.1

Erick
EWB Programming Books and Component Library
http://www.erickengelke.com



Attachments: 0.png
Thu, Feb 11 2021 11:13 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Erick,

<< As you can see in the attachment, it cannot find localhost.

I ran onto a similar problem before on Unix where localhost default assumed IPv6 (which this VM has in addition to IPv4), but did not connect to IPv4.  I don't know if that might be the problem but it looks similar, I don't see EWB listening on IPv6 >>

No, EWB doesn't use IPv6 yet, but that shouldn't affect how localhost is resolved for client connections from a browser.

<< C:\Users\erickengelke>ping localhost >>

I get the same ping results, but my localhost references work fine.

Which Windows patch are you suggesting is responsible for this ?

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com
Thu, Feb 11 2021 1:20 PMPermanent Link

erickengelke

Tim Young [Elevate Software] wrote:

Erick,

<< As you can see in the attachment, it cannot find localhost.

> No, EWB doesn't use IPv6 yet, but that shouldn't affect how localhost is resolved for client connections from a browser.

From what I've read online and the hosts.ini file, the DNS lookup does conversion from Localhost to an address internally.  

Some people have reported that IPv6 preference happened months ago (on various web pages).  For me the switchover to IPv6 preference was effective this Tuesday afternoon.  It worked fine Tuesday morning.  And it fails for both EWB2 and EWB3.

What slowed me down figuring this out was that it takes a long time to timeout, so initially there is no response, just a blank window.  But about a  minute later it fills in the error message I sent, about localhost being down.


> I get the same ping results, but my localhost references work fine.

Which Windows patch are you suggesting is responsible for this ?

I'm not certain it was a windows patch, I'm just suspicious because it happened on a Tuesday.  Also, I am running Parallels on a Mac, so maybe that affects things.

Note however, using Chrome, Edge always work, but IE with hardcoding http://127.0.0.1/test.html.  works perfectly, but http://localhost/test.html. So it seems peculiar to IE and IPv4.

My computer is running 20H2 os build 19042.746

Thanks,
Erick

Tim Young
Elevate Software
www.elevatesoft.com
EWB Programming Books and Component Library
http://www.erickengelke.com
Image