VeriSign call?

[wzab]

We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003?

 

[Bob Buckland ?:-\)]

Hi Wzab,

It's not part of a license verification but may be tied to the use of the features in the new to Office 2003 Research Task Pane.
What settings and features have you enabled?

=======
We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003? >>

 

[Bob Buckland ?:-\)]

Hi Wzab,

It's not part of a license verification but may be tied to the use of the features in the new to Office 2003 Research Task Pane.
What settings and features have you enabled?

=======
We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003? >>

 

[Bob Buckland ?:-\)]

Hi Wzab,

It's not part of a license verification but may be tied to the use of the features in the new to Office 2003 Research Task Pane.
What settings and features have you enabled?

=======
We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003? >>

 

[Bob Buckland ?:-\)]

Hi Wzab,

It's not part of a license verification but may be tied to the use of the features in the new to Office 2003 Research Task Pane.
What settings and features have you enabled?

=======
We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003? >>

 

[Bob Buckland ?:-\)]

Hi Wzab,

It's not part of a license verification but may be tied to the use of the features in the new to Office 2003 Research Task Pane.
What settings and features have you enabled?

=======
We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003? >>

 

[Bob Buckland ?:-\)]

Hi Wzab,

It's not part of a license verification but may be tied to the use of the features in the new to Office 2003 Research Task Pane.
What settings and features have you enabled?

=======
We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003? >>

 

[Bob Buckland ?:-\)]

Hi Wzab,

It's not part of a license verification but may be tied to the use of the features in the new to Office 2003 Research Task Pane.
What settings and features have you enabled?

=======
We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003? >>

 

[Bob Buckland ?:-\)]

Hi Wzab,

It's not part of a license verification but may be tied to the use of the features in the new to Office 2003 Research Task Pane.
What settings and features have you enabled?

=======
We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003? >>

 

[Bob Buckland ?:-\)]

Hi Wzab,

It's not part of a license verification but may be tied to the use of the features in the new to Office 2003 Research Task Pane.
What settings and features have you enabled?

=======
We just installed our first Office 2003 pilot on a bench PC. When Word was
launched (the first Office app selected) for the first time it seemed to hang
for a bit. We checked the firewall and noticed the PC was trying to make a
call to 64.94.110.11:80 (crl.verisign.com) but was failing as we proxy all
outgoing HTTP traffic.

This continued with subsequent launches until we finally logged the PC into
the HTTP Proxy and gained access to the Internet. Since then, Word 2003
launches normally even when off the Internet. I'm guessing this may be some
kind of initial EULA verification (?).

Are we imagining things, or do we have to include logging all PCs onto the
Internet as part of the rollout for Office 2003? >>

 

[Wzab]

Apologies for delayed response...dropped off the globe into overbearing
validation effort. We've installed all with the exception of Wizards &
Templates in Word and Office Assistant in Shared Features. Everything else
is 100% run from hard drive.

Marco security is set to medium to accomodate Avery Wizard 2K3. No
certificates are in use or installed. It's a vanilla installation onto a
generic 2000 Pro SP4 PC. One app that may be related is Adobe Acrobat 6.0
(full standard version). Not sure how though...however the issue hasn't
occured on PCs that don't have it installed.

With each case, the launch of Word hangs for several moments while the call
to crl.verisign.com times-out.

 

[Wzab]

Apologies for delayed response...dropped off the globe into overbearing
validation effort. We've installed all with the exception of Wizards &
Templates in Word and Office Assistant in Shared Features. Everything else
is 100% run from hard drive.

Marco security is set to medium to accomodate Avery Wizard 2K3. No
certificates are in use or installed. It's a vanilla installation onto a
generic 2000 Pro SP4 PC. One app that may be related is Adobe Acrobat 6.0
(full standard version). Not sure how though...however the issue hasn't
occured on PCs that don't have it installed.

With each case, the launch of Word hangs for several moments while the call
to crl.verisign.com times-out.

 

[Wzab]

Apologies for delayed response...dropped off the globe into overbearing
validation effort. We've installed all with the exception of Wizards &
Templates in Word and Office Assistant in Shared Features. Everything else
is 100% run from hard drive.

Marco security is set to medium to accomodate Avery Wizard 2K3. No
certificates are in use or installed. It's a vanilla installation onto a
generic 2000 Pro SP4 PC. One app that may be related is Adobe Acrobat 6.0
(full standard version). Not sure how though...however the issue hasn't
occured on PCs that don't have it installed.

With each case, the launch of Word hangs for several moments while the call
to crl.verisign.com times-out.

 

[Wzab]

Apologies for delayed response...dropped off the globe into overbearing
validation effort. We've installed all with the exception of Wizards &
Templates in Word and Office Assistant in Shared Features. Everything else
is 100% run from hard drive.

Marco security is set to medium to accomodate Avery Wizard 2K3. No
certificates are in use or installed. It's a vanilla installation onto a
generic 2000 Pro SP4 PC. One app that may be related is Adobe Acrobat 6.0
(full standard version). Not sure how though...however the issue hasn't
occured on PCs that don't have it installed.

With each case, the launch of Word hangs for several moments while the call
to crl.verisign.com times-out.

 

[Wzab]

Apologies for delayed response...dropped off the globe into overbearing
validation effort. We've installed all with the exception of Wizards &
Templates in Word and Office Assistant in Shared Features. Everything else
is 100% run from hard drive.

Marco security is set to medium to accomodate Avery Wizard 2K3. No
certificates are in use or installed. It's a vanilla installation onto a
generic 2000 Pro SP4 PC. One app that may be related is Adobe Acrobat 6.0
(full standard version). Not sure how though...however the issue hasn't
occured on PCs that don't have it installed.

With each case, the launch of Word hangs for several moments while the call
to crl.verisign.com times-out.

 

[Wzab]

Apologies for delayed response...dropped off the globe into overbearing
validation effort. We've installed all with the exception of Wizards &
Templates in Word and Office Assistant in Shared Features. Everything else
is 100% run from hard drive.

Marco security is set to medium to accomodate Avery Wizard 2K3. No
certificates are in use or installed. It's a vanilla installation onto a
generic 2000 Pro SP4 PC. One app that may be related is Adobe Acrobat 6.0
(full standard version). Not sure how though...however the issue hasn't
occured on PCs that don't have it installed.

With each case, the launch of Word hangs for several moments while the call
to crl.verisign.com times-out.

 

[Wzab]

Apologies for delayed response...dropped off the globe into overbearing
validation effort. We've installed all with the exception of Wizards &
Templates in Word and Office Assistant in Shared Features. Everything else
is 100% run from hard drive.

Marco security is set to medium to accomodate Avery Wizard 2K3. No
certificates are in use or installed. It's a vanilla installation onto a
generic 2000 Pro SP4 PC. One app that may be related is Adobe Acrobat 6.0
(full standard version). Not sure how though...however the issue hasn't
occured on PCs that don't have it installed.

With each case, the launch of Word hangs for several moments while the call
to crl.verisign.com times-out.

 

[Wzab]

Apologies for delayed response...dropped off the globe into overbearing
validation effort. We've installed all with the exception of Wizards &
Templates in Word and Office Assistant in Shared Features. Everything else
is 100% run from hard drive.

Marco security is set to medium to accomodate Avery Wizard 2K3. No
certificates are in use or installed. It's a vanilla installation onto a
generic 2000 Pro SP4 PC. One app that may be related is Adobe Acrobat 6.0
(full standard version). Not sure how though...however the issue hasn't
occured on PCs that don't have it installed.

With each case, the launch of Word hangs for several moments while the call
to crl.verisign.com times-out.

 

[Wzab]

Apologies for delayed response...dropped off the globe into overbearing
validation effort. We've installed all with the exception of Wizards &
Templates in Word and Office Assistant in Shared Features. Everything else
is 100% run from hard drive.

Marco security is set to medium to accomodate Avery Wizard 2K3. No
certificates are in use or installed. It's a vanilla installation onto a
generic 2000 Pro SP4 PC. One app that may be related is Adobe Acrobat 6.0
(full standard version). Not sure how though...however the issue hasn't
occured on PCs that don't have it installed.

With each case, the launch of Word hangs for several moments while the call
to crl.verisign.com times-out.