In the field I often need to perform remote debugging on a target PC using my Delphi development IDE running on my (host) laptop. Because I cannot use any pre-existing network address infrastructure I use a cross-over network cable directly linking the two PC's. I then setup manual IP address of (say) 100.100.100.1 and 100.100.100.2 for the two and after much rebooting and fiddling I get the shared folders that I need. Finally after working in this way I have to carefully put things back to how they were.
This is pain though. There is a lot of typing and room for error. Further, sharing can take a while before things become visible. Is there some way that I can run something (or write a script) that would ease this process in any way?
Use the designated intranet IP ranges: 10.x.x.x or 192.168.x.x, not 100.x.x.x.
Run a DHCP server on your box. The other box will most probably be already configured to use DHCP to obtain an IP address, this is the default. Windows comes with a bundled DHCP server (at least some versions, install it as a Windows component), or you can use a third-party one.
You need zero rebooting on either box: all modern OSes allow to change IP addresses and routing on the fly, Windows is capable of this for at least a decade. Note that you don't need to change the IP address of your box. Often the secret of fast folder access is using the IP address, like \\192.168.1.1\share_name because name resolution services may take long time to kick in.
If you want both the link via the cross cable and a wired Internet/LAN link, just add another network card to your box (slightly more expensive with notebooks) and have the DHCP server only work with that dedicated card, so you don't need to touch the Internet-connected interface at all.
Related
I am running a Hyper-V lab for a client to test the functionality of a Powershell script and due to memory constraints, I would like to move my file and database VM servers off of my main desktop PC to my laptop. I set up Hyper-V on the laptop, and successfully exported/imported the VM's into the other Hyper-V server. I can boot them, all the configuration and files are intact however, I am predictably having trouble reconnecting to the domain they were a part of prior to the move. I understand I need an External virtual switch to handle that communication, as internal and private will not reach outside of the Hyper-V server they reside in. Obviously I would prefer to not use an external, but this is strictly to continue testing. I've trouble-shooted entering different DNS server values from the client machine's IPv4 properties and changing the virtual switch to External for the existing Hyper-V server, and re-register the DNS records on the DC. All result in the same error when I try to connect to the domain: "(error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc."... "The DNS SRV records required to locate a AD DC for the domain are not registered in DNS".
In summary, I want to move a VM from the first server listed to the second, and then re-connect to the domain they were part of previously. Both machines are just running Windows 10, not Windows Servers, if that matters. Another note, I can do remote sessions from the desktop to the laptop just fine which would lead to believe this is not related to a firewall. Thanks!
The best it to set up a VLAN. If you can't do that, change the network class of your AD lab machine (192.168.55.x ?) to another in order to avoid conflicts.
Your DNS server has to be AD to make your machines connecting to it.
And last but not least, if you're on 2 different hyperV servers, you have to use external switch in hyperV:
https://redmondmag.com/articles/2018/05/04/hyper-v-private-networks.aspx
My work recently purchased a Synology DS3617xs NAS. How do I find the default IP of the NAS so I can do the initial setup?
For security, we're running on a closed system - no internet
Running RHEL 7.4, so the Synology Assistant won't work (Win /Mac /Debian only)
We have two switches but no routers, so no DHCP
From the documentation it seems you need either an internet connection or DHCP for automatic IP assignment (where you can then find the IP from your router).
Any help is greatly appreciated.
I figured out a work-around.
I connected the NAS directly to my workstation using another LAN port I have installed on my workstation. I set the IPv4 connection for this port as Link-Local Only. When the LAN port identified its IP address, I used nmap to search the network to find other IP addresses. Since the only other item on this connection was the Synology, I was able to figure out the IP.
As you dont have DCHP option, please check the subnet and IP Range of the Switches. Then set the IP for the synology diskstation manually (search with the App Synology Assistant Windows download Link). Run synology assist from your computer makes sure the NAS is up and running all lights on and the blue light solid. LAN and disk lights should be flashing. It does take a few minutes for the unit to become available the first time. if you see the IP you can just type in the IP and get to you NAS as well without the synology assistant. You will need just the DSM file for your version/ unit. usually xxx.PAT. its that easy . Maybe the extra switch is the problem.
Pat file of your Diskstation: Link
As others said, it will spend time looking for a DHCP server to allocate an IP, and if it can't it'll eventually(*) default back to a self assigned IP in the 169.254.x.x range.
It takes quite a while to time out, so if you want to set it up without a DHCP server, you need to power it up and wait for 10+ minutes till it times out looking for DHCP responses.
IF you want to set it up without DHCP, you'll want to ensure your computers IP is setup to be able to talk to this range. (eg set your netmask to 0.0.0.0 so all traffic is sent directly, instead of any configured gateway)
I have a setup with a few Linux devices and one windows device connected to a switch. I would like a way to tell the windows machine which IPs the Linux machines get when booting. I have tried to populate the arp table on the windows machine by pinging broadcast but I have not succeeded because windows doesn't reply to broadcast.
I have tried also nmap but that is not an option because it takes really long to scan (the net mask is 255.255.0.0)
You could set up a static IP and other network settings on all the Linux machines.
then on your Windows system edit your HOST file with the names and ip addresses.
This should bypass the need for a DHCP or DNS.
However other systems on the network will not be able to find your systems.
Regardless you still need to speak to the guys who administer the network to add your linux systems in.
It is rather impolite and/or against policy and somewhat bordering on illegal; to simply plug in your systems into the network not owned by yourself.
So if you have a right or need, the administrators will listen and should help you.
Let's say I have a shared folder on my machine, for example : \MyMachine\foo.
If I try to access it on the "MyMachine" computer, will it be smart enough to know that it is on the same machine and won't try to use the network adapter and be super slow? I tested it by disabling my network adapter and it was still working, but it might have been because I disabled it that it checked locally instead of using the network adapter.
My concern for not wanting to use the network adapter is speed. Large amount of data needs to be acceded sometime by network path if used outside, but if it is getting acceded locally it has to be quickly.
Every UNC is resolved down to it's core protocol address. Assuming a standard network of TCP/IP, your UNC will be resolved to local machine and the IP will be the same as your loopback IP. The network adapter won't be needed in this case so nothing will be sent over the network. In short, communication will be via the loopback address which does not require network.
Extracted from:
https://serverfault.com/questions/411389/does-traffic-from-accessing-locally-shared-file-via-unc-path-still-go-through-th
It wont, because the changes are taking place in your computer.
However if someone else is trying to access that directory then your computer must send the directory's information to the other computer, thus using the network.
I often visit various sites and like to do so anonymously from behind a proxy. However, it seems as if some websites are still able to detect my real IP address. I know this because they use the IP address to attempt to geolocate me for services.
How did they actually get my real IP Address if I am using a proxy?
How can I truly hide myself?
Most proxies you'll find online are so-called 'transparant proxies'. This means they identify themselves as proxy and even give your real IP-address to the site.
These proxies are commonly used to load pages on the proxy-server instead of your PC.
IP proxies won't protect you at all, to be honest.
What you need are VPN's (Virtual Private Networks) a.k.a. Network Tunnel.
VPN's allow you to do everything online via an external PC inside that network. You'll get that PC's IP and all loading etc happens on that PC.
Not all VPN's are undetected. If you always want to browse the web anonymously, you'll need to find some HQ VPN's (barely for free) and you'll need to change VPN frequently.
Try searching on HideMyAss, SecurityKISS, ... or maybe even the TOR-network