last day (24 days later) » 

4:23 PM
Hi @miroxlav
 
Hi Rany.
Thank you for effort to help. Before that, two off-topics:
1. to keep the question tidy, could you please delete your previous comments which are no longer relevant?
2. Please how exactly did you create the chat room? I was never able to figure out a way how to do it.
 
@miroxlav sure
@miroxlav done :)
@miroxlav could you access the page from any other device?
 
probably not now
but I can reconnect as soon as possible
my question is, how to find out which device is occupying 192.168.0.34 which throws a general failure (see screenshots) even if the PC is disconnected from network
 
@miroxlav could you run the IP against nmap?
 
4:31 PM
is there a potrable version available? I'd prefer it but I can't see it...
 
@miroxlav I'll check
@miroxlav the link I just sent contains the command-line version of the program
 
oh. cool. downloading...
 
@miroxlav Note: you'll have to install winpcap.org and microsoft.com/download/details.aspx?id=40784
@miroxlav but I advise you to install nmap since it is way simpler (GUI etc.)
 
command line is perfectly ok, if you have specific command at mind
if not, then I'll reach for the GUI
 
@miroxlav no I know what command to run :)
@miroxlav but you still have to install winpcap.org and microsoft.com/download/details.aspx?id=40784
 
4:40 PM
ok, then I'm downloading the installer
 
@miroxlav what installer?
 
setup.exe for nmap
 
@miroxlav so you aren't downloading the command-line version?
 
I already did but after you said that it still needs additional installs, it can be more comfortable to install them all at once by setup.exe
OK, installed
 
@miroxlav open zenmap
 
4:44 PM
done
 
@miroxlav OK, could you send me screenshot of your screen?
 
there was no scan. the window is empty. are you sure you want the screenshot now?
 
@miroxlav wait a minute.
@miroxlav I am just trying to remember which command to run
@miroxlav long time since I last used nmap
@miroxlav put 192.168.0.34 in the target field
 
ok I did
 
@miroxlav is there a way to change the operation?
 
4:53 PM
what operation do you mean?
 
@miroxlav umm maybe profile?
 
yes. In the meantime I ran several scans (under various profiles) against the address. it appears it is the localhost - strange
Starting Nmap 7.12 ( https://nmap.org ) at 2016-08-10 18:51 Central Europe Daylight Time

NSE: Loaded 262 scripts for scanning.

NSE: Script Pre-scanning.

Initiating NSE at 18:51

NSE: [shodan-api] Error: Please specify your ShodanAPI key with the shodan-api.apikey argument

NSE: [mtrace] A source IP must be provided through fromip argument.

Completed NSE at 18:52, 12.84s elapsed

Initiating NSE at 18:52

Completed NSE at 18:52, 0.00s elapsed

Initiating NSE at 18:52

Completed NSE at 18:52, 0.00s elapsed
 
@miroxlav ah your IP is 192.168.0.34
@miroxlav your private IP is 192.168.0.34
@miroxlav now change the target to 192.168.1.1
 
if you check "ipconfig /all" in the question, the IP 192.168.0.34 is not mentioned there at all
 
@miroxlav strange...
 
4:58 PM
I have re-checked it right now
so the question is from where it comes
 
@miroxlav according to nmap your computer's IP is 192.168.0.34
@miroxlav I thought nmap could help :/
 
yes but I can find it nowhere else in Windows
probably some software or service is interfering, but which one?
 
@miroxlav did you rescan but change the target IP to 192.168.1.1
 
Question: Can you rule out that no other network adapter is the cause? I'm looking at "Wireless LAN adapter Local Area Connection* 12", Ethernet adapter OpenVPN, Ethernet adapter Team Viewer VPN. Maybe create a system restore point, uninstall their respective software and resore that point afterwards
 
@nixda – I'm very sorry, I'm not going to uninstall them. but I can disable them for a moment
@rany – the scan is still running....
 
5:03 PM
@nixda @miroxlav open devmgmt.msc from run
@miroxlav disable the adapters @nixda metioned to check if they are the source of the problem
@miroxlav but dont disable "Wireless LAN adapter Local Area Connection* 12"
@miroxlav it is important
 
@rany – I'm very sorry, your request to "not disable *12" has come too late
I already disabled all adaptors, then re-enabled them
 
@miroxlav did it help?
 
and now, 192.168.0.34 is gone
 
@miroxlav so is your problem solved?
 
yes. one of adapters was creating that IP address even if it was not reported in ipconfig /all
 
5:09 PM
As I thought :)
 
do you have any experience with this?
have you already seen that somewhere?
 
@miroxlav OK. Good job @nixda :)
 
Not in particular. Would be good to know which one of these adapters was the cause
 
before, Hyper-V network adapter was causing problems to me
 
@miroxlav interesting
 
5:11 PM
not this specific problem, but they were strange, e.g. inability to connect anywhere etc.
I suspect it was that adaptor again
as you said "*12"
 
@miroxlav what do you mean "*12"
 
"Wireless LAN adapter Local Area Connection* 12"
 
@miroxlav do you mean it caused all of this?
 
I checked that all 3 Hyper-V machines are off.
Answer to your question: I suspect so, because in the past it did it. (I tracked that down before.)
To me it seems, it has somewhat unstable behavior / driver.
 
That "*12" means something installed this adapter over and over again and increased the counter, not?
 
5:15 PM
@miroxlav It is installed by default on WIndows 8, 8.1, 10 to connect Wi-Fi direct devices using the Windows Pairing experience user interface
 
@nixda – yes. I cannot see older ones, otherwise I would remove them somehow. that *12 looks disturbing.
 
ok then, have a nice day. bye all
 
@nixda bye :)
 
@rany – oh... perhaps I was wrong this time. so you say that "Wireless LAN adapter Local Area Connection* 12" is not connected to Hyper-V?
 
@miroxlav absolutely not
@miroxlav it isnt related to hyper-v whatsoever
@miroxlav it is very important for some features in Windows to work
 
5:18 PM
I see. wait. I cannot see "Wireless LAN adapter Local Area Connection* 12" in the list of adaptors I disabled. SORRY for confusion
so I did not disable that one, I just created the confusion
 
@miroxlav did you disable Microsoft Wi-Fi Direct Virtual Adapter
 
I disabled these:
• Hyper-V Virtual Ethernet
• Bluetooth Network Connection
• Team Viewer VPN
• OpenVPN
 
@miroxlav OK, but I don't think Hyper-V could interfere
 
@rany no, I can't see "Microsoft Wi-Fi Direct Virtual Adapter" in the list
 
@miroxlav could you try to renable it?
 
5:20 PM
all are re-enabled now
 
@miroxlav could you ping 192.168.1.1?
 
I just disabled them all and then re-enabled immediately
now it work correctly
let me disconnect from wi-fi for a moment
 
@miroxlav OK
@miroxlav Are you still facing the same issue after re-enabling them?
 
no, 192.168.0.34 is gone since the first disable/enable cycle
solved...
 
@miroxlav Great.
 
5:28 PM
I'm still not sure which adaptor backed it and why, but now it can' be figured out
thank you for your dedicated assistance.
 
@miroxlav I think one of your VPN clients failed to connect and ended up connecting to nothing
@miroxlav This happens alot w/ OpenVPN
 
ok. I try to uninstall OpenVPN, currently I almost don't use it.
btw how you can create the chat room for the question? I cannot see any link in the question to do that.
 
@miroxlav I just named it the question's name :)
@miroxlav and left the description field blank
 
oh, OK, so there's no link to the question :) haha
thank you very much rany again
 
no problem @miroxlav :)
 
5:34 PM
perhaps you can add an answer and I'll accept it
 
@miroxlav OK.
@miroxlav done :)
room topic changed to Pinging router at 192.168.1.1 returns response from 192.168.0.34: superuser.com/questions/1112063 (no tags)
@miroxlav I just added a link to the question in the topic :)
 
6:11 PM
:) I see and I found where it is made :)
 

  last day (24 days later) »