Packetlogger Problem

03/19/2015 19:31 szymek111#1
Hey guys i have problem with packetlogger . Whenever i want to inject nospacket.dll into nostale client i got weird error . Access violation at adress .... bla bla (in every client version pl, de etc) . How to fix that ?
03/19/2015 21:28 Bombasticx3#2
Outdatet.
03/19/2015 21:45 szymek111#3
What do you mean ?
03/19/2015 22:11 *-OMG-*#4
@Bombasticx3 Elektrochemie packetlogger is not outdated.

However, there are 2 kinds of violations related to the injection:
- The dll is already injected, you must restart the client or unload the previous module
- The dll entry-point is bad programmed or the injector takes too much time to read the returned value, ignore it.
03/19/2015 22:18 szymek111#5
Quote:
Originally Posted by *-OMG-* View Post
@Bombasticx3 Elektrochemie packetlogger is not outdated.

However, there are 2 kinds of violations related to the injection:
- The dll is already injected, you must restart the client or unload the previous module

- The dll entry-point is bad programmed or the injector takes too much time to read the returned value, ignore it.
First - When i launch up client and just after when it goes into login screen when i inject it into nostale process i still got this error.
2nd - I tried many injectors like Cheat Engine,Pfand etc ..
Btw my windows is win 7 64 bit and i have avast . However i tried to disable avast but it isn't working.
03/19/2015 22:25 *-OMG-*#6
- Window appears ?
- Did you tried to disable UAC ?
- Can you post an error screen ?
- Which version of packet logger do you have ?

Help us to help you posting more details.
03/19/2015 22:28 IceTrailer#7
Quote:
Originally Posted by *-OMG-* View Post
@Bombasticx3 Elektrochemie packetlogger is not outdated.

Well - the functions (receive, send, log send, log receive) do not always work perfectly. The addresses should be updated or rather the packetlogger should be recoded.
03/19/2015 22:35 szymek111#8
Quote:
Originally Posted by *-OMG-* View Post
- Window appears ?
- Did you tried to disable UAC ?
- Can you post an error screen ?
- Which version of packet logger do you have ?

Help us to help you posting more details.
-Yep but when i click anything in nostale i got the same error and i can't do anything . I need to restart client.
-Doesn't work
-Screen :
[Only registered and activated users can see links. Click Here To Register...]
-1.1

It's weird because it doesn't work in win 7 64 bit but in my laptop which have win 8.1 64 bit it works perfectly.
03/19/2015 23:05 *-OMG-*#9
Quote:
Originally Posted by IceTrailer View Post
Well - the functions (receive, send, log send, log receive) do not always work perfectly. The addresses should be updated or rather the packetlogger should be recoded.
Please, avoid to write nonsense, limit yourself to write about what you know rather than go with the fantasy.

Quote:
Originally Posted by szymek111 View Post
-Yep but when i click anything in nostale i got the same error and i can't do anything . I need to restart client.
-Doesn't work
-Screen :
[Only registered and activated users can see links. Click Here To Register...]
-1.1

It's weird because it doesn't work in win 7 64 bit but in my laptop which have win 8.1 64 bit it works perfectly.
Well, now i got your problem. It is an exception related to memory access at the address 0x..

The packetlogger works and includes an auto-finder so there are 3 options:
- You are injecting something other before than packetlogger (to exclude ?)
- You are using a different client (to exclude ?)
- There is a tool installed in your computer that edits the opcodes at the client runtime (maybe, are you infected ?)

We can analyze it using a debugger, contact me on skype.. live:systemx64
03/20/2015 15:00 Bombasticx3#10
Quote:
Originally Posted by *-OMG-* View Post
Please, avoid to write nonsense, limit yourself to write about what you know rather than go with the fantasy.



Well, now i got your problem. It is an exception related to memory access at the address 0x..

The packetlogger works and includes an auto-finder so there are 3 options:
- You are injecting something other before than packetlogger (to exclude ?)
- You are using a different client (to exclude ?)
- There is a tool installed in your computer that edits the opcodes at the client runtime (maybe, are you infected ?)

We can analyze it using a debugger, contact me on skype.. live:systemx64
I and many others have the same problem like him.
All of the three reasons you said were proofed. Found nothing.
Like you said update the adresses.
03/20/2015 20:17 *-OMG-*#11
Quote:
Originally Posted by Bombasticx3 View Post
I and many others have the same problem like him.
All of the three reasons you said were proofed. Found nothing.
Like you said update the adresses.
1- I'm using packetlogger and i didn't got any problem with it.
2- Elektrochemie packet logger auto-find the address at the injection, nothing to update here \:
3- Limit yourself to what you know and stop to go away with your fantasy.
03/20/2015 21:20 Bombasticx3#12
I tried Elektros with 4 PC's. 5 Different Clients. x different Injectors. It's a general problem. Not only my stupidness.
You can logg packtes but you can't send it.
03/20/2015 21:55 Bejine#13
Everything works for me.
Tested with 3 injectors, 3 PCs and ~10 clients.
03/20/2015 22:36 *-OMG-*#14
I made an analysis on szymek111's computer. As i previously said, it is a compatibility problem. Some operating systems don't support the packetlogger. I have no depth, i only checked the addresses.. Maybe some missing library :)
03/21/2015 03:54 Jotamex#15
I have the same problem, the solution is to easy.

1. Go to "run" on ur pc ot botton windows + r. Write "cmd" (all unquoted) and enter.
2. In that window write:
a- " bcdedit.exe /set current nx alwaysoon"
b- "bcdedit.exe /set {current} nx optin" (Write a and b, dont choose, need the 2)
3. Reboot the pc and go to panel control, system and security, sistem, advanced system settings, performance, Data Execution Prevention, check the 2 option (Active DEP against all the programs and services...) and add "nostale.exe"


Sry for my bad english.