+  planetsuper forums
|-+  Main» Games» Paintball2» Blocked Sites! GRRR
Username:
Password:
Advanced Search
Pages: [1]
  Print  
Author Topic: Blocked Sites! GRRR  (Read 694 times)
tipsyhitman
Member
**
Posts: 106


« on: Dec 30, 2006, 10:17 PM »

Ok i found out how my brother "blocked" certain sites. When i open a command prompt and type ipconfig /displaydns, it has all the sites that are blocked, then when i try to ping them it saids {"the site" (127.0.0.1)}. How do i reset my dns or like delete the sites from it?
Logged
KnacK
Senior Member
***
Posts: 284



« Reply #1 on: Dec 30, 2006, 10:39 PM »

Open up windows explorer

navigate to:

C:\WINDOWS\system32\drivers\etc

open up the hosts file with notepad and see if any of your sites are there.

Then try lmhosts ( might be lmhosts.sam) "l" is an "L"
Any sites that you want to unblock just delete them.
Logged
tipsyhitman
Member
**
Posts: 106


« Reply #2 on: Dec 30, 2006, 10:46 PM »

it said this is a sample lmhost file
Logged
jitspoe
Platinum Member
***
Posts: 1511



« Reply #3 on: Dec 31, 2006, 12:19 AM »

I always just edited "hosts", not "lmhosts.sam".  What's the difference?
Logged

BALETED!
KnacK
Senior Member
***
Posts: 284



« Reply #4 on: Dec 31, 2006, 07:44 AM »

the lmhosts file is used specify where network devices are on the network. 

The hosts file is used, for lack of a better term, like a mini-dns.  Say you have a problem spelling Google, and you spell it Goggle.  You could have an entry that points goggle.com to the ip address of google.com. 

The pc looks at the host files and lmhosts files before it goes out and checks the dns server.
Logged
Supermercado
Administrator
*****
Posts: 3802


Repeated head trauma can cause brain damage


« Reply #5 on: Dec 31, 2006, 08:56 AM »

Interesting. I'd never heard of lmhosts, either.
Logged

"I couldn't do that. Could you do that? Why can they do it? Who are those guys?"

Take my love, take my land, take me where I cannot stand. I don't care, I'm still free, you can't take the sky from me.
tipsyhitman
Member
**
Posts: 106


« Reply #6 on: Dec 31, 2006, 12:12 PM »

How can i get around it or delete it?
Logged
KnacK
Senior Member
***
Posts: 284



« Reply #7 on: Dec 31, 2006, 02:08 PM »

did you open them up with notepad?

or, did mommy install Net Nanny on your pc.... ( I'm actually serious here )
Logged
tipsyhitman
Member
**
Posts: 106


« Reply #8 on: Dec 31, 2006, 05:48 PM »

wordpad
Logged
KnacK
Senior Member
***
Posts: 284



« Reply #9 on: Dec 31, 2006, 06:09 PM »

Then post the contents here and lets take a look see.
Logged
tipsyhitman
Member
**
Posts: 106


« Reply #10 on: Jan 01, 2007, 12:38 AM »

# 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.




Logged
KnacK
Senior Member
***
Posts: 284



« Reply #11 on: Jan 01, 2007, 07:26 AM »

Nope,
That's the stock lmhosts file.

What about the hosts file?
Logged
KnacK
Senior Member
***
Posts: 284



« Reply #12 on: Jan 01, 2007, 07:27 AM »

On a sleepy thought, have you check the windows firewall configurations??
Logged
Pages: [1]
  Print  
Show unread posts since last visit

 
Jump to: