Waraxe IT Security Portal

F4r4Zm0In · Active user

May be this tutorial is helpful for N00bs Smile

This article is not meant for advanced users
because you may be already knowing this
but it may be helpful for the beginners

well, its time to exploit the network
yes i am talking about the lan [Local Area Network]
lets start:
1: click start>run>cmd>type ipconfig
then you will be seeing a picture like this one :

now, from the picture we can easily know what our "ip address" is
if in this case our ip address is "117.197.48.112"
then obviously the ip addresses of other peoples on the network must be similar to this one
yeah, the only thing which is different is the last part.

i mean [112]

now, our job now is to find a system that has file and printer sharing enabled
but first we have to find some live hosts
lets try:

now to find live hosts what we did is:
we start pinging systems by changing the last part [112]

and here is what we have got:

yea, we got ping response because our machine is still active LOL :d

Now, we dont want to exploit our own system so its time to ping some one else :

lets start pinging randomly:

117.197.48.112 [Owr own machine, which we already pinged]
117.197.48.111
117.197.48.110
117.197.48.109
................................. and so on.

in the first attempt we tried pinging 117.197.48.111 and our ping failed
in the second attempt we tried pinging 117.197.48.100 and got "Success"

now simply click on start>run>type \\117.197.48.100
Now hit Enter button.

and here is what we have got Smile

Now, we can copy, edit, or even delete the stuff from that machine Smile

In this exploit we got success at the second attempt because the machine is having "file and printer sharing enabled" option checked!
sometimes it happens that we got ping response, but Still can't explore the host over the network [and got some nasty errors while trying to exploit]
because the machine is most probably having "file and printer sharing enabled" option Unchecked!
or it may be behind the firewall!

All it depend on your day!

So its better that you try your luck.

Tom · Regular user

Nice tut for Noobs.

Smile

F4r4Zm0In · Active user

hunter · Regular user

MORE TUTS PLZ !

hacking servers would be good Smile

no luck yet, i guess not many ppl have pritner file sharing on?

also if i pinged one that worked...i would get "a device on your comptuer is not functioning" or something.

im on vista.

F4r4Zm0In · Active user

ToXiC · Moderator

F4r4Zm0In ,

i dont want to sound crawl or anything but having access into share files is NOT hacking ...

nice effort though ...

i will try to extend it a bit to make it more interesting..

well ..

some basic commands are :

nbtstat
nbtstat display protocol statistics and current TCP/IP connections using NBT (NetBIOS over TCP/IP).

usage nbtstat -a ip

article on nbtstat
http://articles.techrepublic.com.com/5100-1035-1058328.html

Beyond that you can play with null sessions :

A null session can be created by using the Windows net program to map a connection using a blank username and password. On Windows systems that are vulnerable, you simply have to enter:
net use \\ip_address\ipc$ "" "/user:" at a Windows command prompt.

This was a vulnerability of windows 2000 that could create a connection with no user or pass with enough priviledges to have access to network pcs and with programs such as Winfo, Walksam, certain Windows Resource Kit tools and even the net program that's built into Windows to glean tons of information off a Windows system

In windows xp now they decided to protect that resource but the still left the null sessions . So some not so well configured boxes could allow null sessions as well.

Nice tools to use for USER ENUMERATION and more..

autoscan:
http://autoscan-network.com/

cain and abel
http://www.oxid.it/cain.html
-
-
-
and 100000 more Smile

F4r4Zm0In · Active user

Kazuma · Beginner

You could have easy walked over to your roommates computer to avoid all the hassle with typing all those internal IP's Wink

Outside your (V)LAN this would be hard to find since most routers have NAT disabled for these ports (samba sharing?).
Cool