Recycle your Computers & Technology with us.

Why won't my computer allow me to view pop-ups?

Posted By : bin of Katharine Gibbs School - New York on March 18, 2003

Follow us on Facebook   Follow us on Twitter   Follow us on LinkedIn

Let Data Doctors be your personal IT department today

When I'm Browsing the internet I can't see pop-ups. I haven't installed/downloaded/used a pop-up killer and my settings are set to let me see them. When a pop-up is supposed to come on a window opens (the exact size that the pop-up would be). But it's blank, nothing is there. As if it's not trying to connect to the URL... well basicly it's not. Why isn't my computer letting me see them?

This question was answered on March 18, 2003. Much of the information contained herein may have changed since posting.


If I were you I would take that as a blessing not being able to see pop-ups All they do is slow down your connection by attemping to sell you some useless junk you don't really need

However if you really wanna see your popups all you have to do is reset the Hosts file If you are running windows XP it should be located in C:\WINDOWS\system32\drivers\etc Make sure you are set to view hidden files Once you get there open the HOSTS file delete everything and copy/paste the following and save.

# Copyright (c) 1993-1999 Microsoft Corp.

#

# This is a sample LMHOSTS file used by the Microsoft TCP/IP for Windows.

#

# This file contains the mappings of IP addresses to computernames

# (NetBIOS) names Each entry should be kept on an individual line.

# The IP address should be placed in the first column followed by the

# corresponding computername The address and the computername

# should be separated by at least one space or tab The "#" character

# is generally used to denote the start of a comment (see the exceptions

# below).

#

# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts

# files and offers the following extensions:

#

# #PRE

# #DOM:<domain>

# #INCLUDE <filename>

# #BEGIN_ALTERNATE

# #END_ALTERNATE

# \0xnn (non-printing character support)

#

# Following any entry in the file with the characters "#PRE" will cause

# the entry to be preloaded into the name cache By default, entries are

# not preloaded, but are parsed only after dynamic name resolution fails.

#

# Following an entry with the "#DOM:<domain>" tag will associate the

# entry with the domain specified by <domain> This affects how the

# browser and logon services behave in TCP/IP environments To preload

# the host name associated with #DOM entry, it is necessary to also add a

# #PRE to the line The <domain> is always preloaded although it will not

# be shown when the name cache is viewed.

#

# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)

# software to seek the specified <filename> and parse it as if it were

# local <filename> is generally a UNC-based name, allowing a

# centralized lmhosts file to be maintained on a server.

# It is ALWAYS necessary to provide a mapping for the IP address of the

# server prior to the #INCLUDE This mapping must use the #PRE directive.

# In addtion the share "public" in the example below must be in the

# LanManServer list of "NullSessionShares" in order for client machines to

# be able to read the lmhosts file successfully This key is under

# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares

# in the registry Simply add "public" to the list found there.

#

# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE

# statements to be grouped together Any single successful include

# will cause the group to succeed.

#

# Finally, non-printing characters can be embedded in mappings by

# first surrounding the NetBIOS name in quotations, then using the

# \0xnn notation to specify a hex value for a non-printing character.

#

# The following example illustrates all of these extensions:

#

# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC

# 102.54.94.102 "appname \0x14" #special app server

# 102.54.94.123 popular #PRE #source server

# 102.54.94.117 localsrv #PRE #needed for the include

#

# #BEGIN_ALTERNATE

# #INCLUDE \\localsrv\public\lmhosts

# #INCLUDE \\rhino\public\lmhosts

# #END_ALTERNATE

#

# In the above example, the "appname" server contains a special

# character in its name, the "popular" and "localsrv" server names are

# preloaded, and the "rhino" server name is specified so it can be used

# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"

# system is unavailable.

#

# Note that the whole file is parsed including comments on each lookup,

# so keeping the number of comments to a minimum will improve performance.

# Therefore it is not advisable to simply add lmhosts file entries onto the

# end of this file.

About the author

Posted by bin of Katharine Gibbs School - New York on March 18, 2003

Need Help with this Issue?

We help people with technology! It's what we do.
Contact or Schedule an Appointment with a location for help!