«

Thank you, thank you!
So that's what those addresses I've been using all these
years are called!
I have a hard time remembering acronyms that I don't use
every day. There are just so many of them.

Richard

"StarScripter" <> wrote in message
news:bv5p6p$ohpd8$...
> Richard Steinfeld wrote:
> > So, I've stirred up a bit of self-righteousness among
the
> > cogniscenti. However, nobody has replied with the actual
> > definition of "IP." For example, what do the initials
stand
> > for?
> >
> > Please, will someone answer me in English?
> >
> > Richard
>
> From Microsoft Computer Dictionary:
>
> *IP* n. Acronym for Internet Protocol. The protocol
within TCP/IP that
> governs the breakup of data messages into packets, the
routing of the
> packets from sender to destination network and station,
and the reassembly
> of the packets into the original data messages at the
destination. IP runs
> at the internetwork layer in the TCP/IP model-equivalent
to the network
> layer in the ISO/OSI reference model. See also ISO/OSI
reference model,
> TCP/IP. Compare TCP.
>
> *IP address* n. Short for Internet Protocol address. A
32-bit (4-byte)
> binary number that uniquely identifies a host (computer)
connected to the
> Internet to other Internet hosts, for the purposes of
communication through
> the transfer of packets. An IP address is expressed in
"dotted quad" format,
> consisting of the decimal values of its 4 bytes, separated
with periods; for
> example, 127.0.0.1. The first 1, 2, or 3 bytes of the IP
address identify
> the network the host is connected to; the remaining bits
identify the host
> itself. The 32 bits of all 4 bytes together can signify
almost 232, or
> roughly 4 billion, hosts. (A few small ranges within that
set of numbers are
> not used.) Also called: Internet Protocol number, IP
number. See also host,
> IANA, ICANN, InterNIC, IP, IP address classes, packet
(definition 2).
> Compare domain name.
>
> *IP address classes* n. Short for Internet Protocol
address classes. The
> classes into which IP addresses were divided to
accommodate different
> network sizes. Each class is associated with a range of
possible IP
> addresses and is limited to a specific number of networks
per class and
> hosts per network. See the table. See also Class A IP
address, Class B IP
> address, Class C IP address, IP address.
> Address Class Range of IP Addresses Networks per Class
Hosts per Network
> (maximum number)
> Class A (/ 1.x.x.x to 126.x.x.x 126 16,777,214
> Class B (/16) 128.0.x.x to 191.255.x.x 16,384 65,534
> Class C (/24) 192.0.0.x to 223.255.255.x 2,097,152
254
>
> IP address classes. Each x represents the host-number
field assigned by the
> network administrator.
>
>
>
> --
> S.S.
>
>

Richard Steinfeld wrote:
>> I gave sygate a 6 month try and except for one annoying thing, i
>> really liked it. I will go back if and when this one issue is
>> resolved. The problem i ran into was that it sometimes took as much
>> as 30 seconds once logged into windows to receive an IP from my
>> cable/dsl router. There was a definite delay before networking was
>> fully enabled.
>>
>
> What's an "IP?"
> I'm not using networking and I haven't experienced this
> delay, I think.
>
> Richard

First off the reference to IP should really have read IP Address, an
explanation of which you have received.
Regarding the 'bibs' on your hard drive, would you by any chance have the
auto update feature enabled?
FYI I have not found any of the personal firewalls that I have tried that
log their own activity - you will not see any traffic in the logs that shows
the auto update working - unless they have changed lately.
BTW those I have tried include Tiny/Kerio, ZA, Sygate, and Outpost. I
currently use Outpost.
Seán

ClareOldie wrote:
| Richard Steinfeld wrote:
||| I gave sygate a 6 month try and except for one annoying
||| thing, i really liked it. I will go back if and when this
||| one issue is resolved. The problem i ran into was that it
||| sometimes took as much as 30 seconds once logged into
||| windows to receive an IP from my cable/dsl router. There was
||| a definite delay before networking was fully enabled.
|||
||
|| What's an "IP?"
|| I'm not using networking and I haven't experienced this
|| delay, I think.
||
|| Richard
|
| First off the reference to IP should really have read IP
| Address, an explanation of which you have received.
| Regarding the 'bibs' on your hard drive, would you by any
| chance have the auto update feature enabled?
| FYI I have not found any of the personal firewalls that I have
| tried that log their own activity - you will not see any
| traffic in the logs that shows the auto update working -
| unless they have changed lately.
| BTW those I have tried include Tiny/Kerio, ZA, Sygate, and
| Outpost. I currently use Outpost.
| Seán

Thank you Seán.
Finally, someone who will speak English!
So, I've been dealing with some folks who are too lazy to use the
full term, which I've known for ages. Is that it? And then they
yell at me for not being as techno-adept as themselves. Hah!

I never allow any software to update itself automatically. When
Sygate is running and I'm connected to the Web (I mean a with the
browser open on DSL), I often get almost rhythmic hard drive
"blips." The drive is operating for a fraction of a second. I can
find no sign of internet activity nor, if I recall, any file
action at those times.

There was something vaguely related on the Sygate support page
mentioning something about needing a very clean install, so I may
try a fresh installation with every non-essential in residence
killed.

I like Sygate's interface very much. The human engineering
(usability) is unusually good for a security product.

Would you be so kind as to describe for me the differences you
find between Sygate and Outpost.

Thanks.

Richard