oke here's my problem i can't get the ftp server online on a host i want 2 hack...
It's kinda really noobish 2 ask but well i'm despret I tried so many things and stillcan't get it
to work. So help would be apriciated if i'm correct there is nothing wrong with the commands i give.

the host I hacked is a SQL server:

commands I gave:

try to do net start serv-u and serv-u /i more ! sometimes it dont work and u have to redo the cmd ! normally i dont help ppl wanna hack sb else cause this is security forum and not a hacking portal ! but if got the same prob a year ago so i replyt !

mfg crackie :/

crackie,

I apoligize for my post and i thaknk your for my help. But this leaves me with one more question. The Ip i'm hacking doesn't show up in the startuplog. How is that possible and is it right? I mean I don't think ic an connect to the ftp if it sn't hosted on the target ip number

greetz Alex Trust

if the FTP server is started on your victim/target machine, then it appears that it is on a network using NAT.

So in your connection program, ther should be some option to connect to an IP behind a router/NAT. enable that option and try to connect.

dragon .. the real service name is : Serv-U
hope it works now .. cya

nope sry,

If nat is in use and it obviously is then the ports you are choosing to open ftp on is probably being blocked. Scan your target's IP for all 65535 ports to see what is being allowed. You'll have to choose something open. Since SQL is in use, there's a good chance that the IP is firewalled. Run nmap to help verify it. Also run netstat -an on the target to see what is connecting to it, perhaps there is another server out there with more ports allowed.

If you find an open service, determine what is running and if killing it will raise the alarm. Kill the service and run your ftp on that port.

oke that last peice of advize is very usefull. Thnx for all the help guys I will try these things

its pulling the wrong ip for connection. in ur .ini file set it to the ip that ur sql is running on and restart the Serv-U Deamon. should work . 2. if firewall is stoping it. try a netstat -an. for listening ports. open, and try those. 3. if these two havent worked. try and see if this sql server hasnt already been hacked and running a version of serv-u when u start servu and u get no errors then you should be good. while u do a netstat -an look for ur port u set in the ini file to connect to. if u see the internal ip and port in listening mode should be good to connect. if u dont see ur port then its not running right and need to check into it more. hope this gets u in the right path just some steps ive done on servers with the same issues.

good post

this is the sort of stuff that's going to get us closed down.

although what you post is interesting, you can't just ask for help in directly breaking the law - you just can't!

-ed.

Here are your potential problems:

A: Just because servu is started, doesn't mean it's yours, it could be somebody else's

B: If it's firewalled to allow port 1433, but not any others, you can't get it anyway

C: 192.168.* are non routable ip's, and if things aren't being port forwarded, then you're screwed.

maybe port 1433 is filtered, or maybe this server has already been hacked and the servu process is already running... you can't run 2 times the same process..
check the running processes on the machine, even the Servu proces that could be renamed and kill it... then runn it again..
you can also use psexec instead of netstart..

try uploading tlist, and check if your servu is running, or some other servu is running(to make sure it's your you can try renaming it), and if your is running, then something strange occured, if not, and no other servu is running, it's propably some kind of firewall, or AV, so just get to the next scan, you can do nothing with this one.

You can also see for the services that are running and kill 1 for example sql ( admin will notice probally or a more uncommon service ) and use the port then when it is open ( will be 1433 then for SQl ) when it has a firewall/router you dont have the problem then anymore

if u hex edit ur serv-u and change the mutex name, u can run 2 at the same time if u want i can post a tut that shows how

it looks routed/nat too me if anything see if you can look at the gatewat maybe can shead a little more light on the routing situation..

mate it happent to my a lot of times when something like that usual happens i think u need to wait for the Server to restart so it will load b4 the Firewall loads up...