I have 3 cisco routers with gateway to gateway vpns setup. Location 2 can ping the local domain (mydomain.local which resides at Main Location1) and everything works just fine. Users can connect to the domain perfectly.

Location 3 cannot ping mydomain.local or the netbios name of the server at MainLocation1. I can ping the ip address of the server at MainLocation1.

MainLocation 1 (Where the server resides)
Location 2 (satellite office)
Location 3 (satellite office).

On the workstation at Location 3 I manually assigned dns 1 to the server's ip.

Other details: All of the routers are the same. Any help I can get would be much appreciated!

Its been a while since I shared a folder in a Workgroup let alone a Windows 10 workgroup. We have a 2019server that is part of the workgroup and its where we want to share one folder from.  Does anyone have a good step by step reference on how to setup a user from another computer to access a resource from another computer?

I am having problems sharing a folder from my Windows 2007 R2 server,

If the folder to be shared is (target folder) is in the root of a local drive then simply selecting, right-clicking and selecting 'Share With...' allows me to create a share. This can be confrmed by a) I can see the share from another machine b) on the server's  [Device Manager - System Tools - Shared Folders - Shares] the new share is listed.

If the target folder is not in the root of the drive then repeating the above actions does not create a share - verified by the two methods above.

Can someone advise the correct way to create a sub-folder share ? I need this becuase I am using the share on another location but that folder can't' be moved on the home server.

DNS and DHCP Interaction

Recently we had to replace old  computers with new ones but we kept the same hostname , the new computers get different IP address than the old ones from DHCP.

Example :

Old ComputerA  replaced and named  the same ComputerA
Old ComputerA IP address: 10.10.10.10
New ComputerA IP address: 20.20.20.20

What I have noticed after replacement:
If I login locally to New ComputerA, and run Ipconfig, I will see 20.20.20.20  which is correct.
If Remotely I ping by hostname the ComputerA,  I get 10.10.10.10 with Destination Host Unreachable. [you can see it looks for old IP address]
if Remotely I ping Reverse lookup : Ping -a 20.20.20.20 , it will Reply properly and shows ComputerA  with IP 20.20.20.20


So the problem seems to be the DNS A record does not get update quickly,  I said Quickly because after sometime, if I go and ping by hostname ,ie : Ping ComputerA, I get a proper Reply with 20.20.20.20

My question is I do not understand why Reverse Ping [Ping -a <IP address>] will Reply quickly and Ping Hostname did not Reply until later time....

Any clarification will be very much appreciated.

Thank you

i stop ip6 in windows but for ping a hostname in windows 10 i have return   ::1:
how to change it?
it should return ip address

Dear Wizards, our users need to modify the Date/Time settings on domain-joined PCs. Can we do that? please suggest.

Hello Experts,

I am trying to access an IP Video camera on my private network from the Internet.

1. I have verified the camera can be accessed via a web page from the private LAN.
2. My IP camera is currently using port 80
3. I set up port forwarding in my DSL modem to access the IP Camera IP via Port 80.
4. I can verify the port is open using canyouseeme.org (If I remove the port forward in my modem, the route from canyouseeme.org fails)

When I try to access the IP camera from the internet by typing http//"MyPublicIP:80" the the browser times out.

So I believe I have port 80 open but I cannot access the IP camera on my local LAN from the Internet.

Does anyone know what may be going on here?

Good morning-

I'm running into an issue I've never seen before and am seeking some assistance.

Background:
Windows Server 2012 R2 AD domain with 30 users and 2 domain controllers: dc1 and dc2

File server /w 2 file shares: R and T drive

After a Windows Update users are no longer able to access these file shares. They are receiving the following error:
"the target account name is incorrect"

Sometimes you can access the share drive but it will time out and go back to the error mentioned above.

However, users can browse to the file share via explorer just fine using the UNC: \\dc1\share. Computers can also ping both dc's by DNS just fine as well. I have rebooted both dc's along with the file server in question. Additionally I have disjoined and rejoined the file server from the domain no avail.

Can someone please point me in the right direction as to how to proceed?  Thank you!

Is there a way to set IP address, mask, gateway and DNS at a CMD prompt? Going through the GUI
is a pain. Thanks!

I think this is a simple question for folks with more experience than I, with shared workstation files in a domain:
I'm trying to suitably limit access to files on workstations while still providing for file shares on them.
The "current user" logged onto the machine should have Modify, Read & execute, List folder contents, Read and Write
A single domain group needs have Read & Execute, List folder contents and Read but doesn't need Modify nor Write.

How would you set this up so that wider access is blocked BUT not limiting normal / accepted administrative maintenance, etc.
(Yes, I know that even doing this is a bit unusual - so please humor me).

Do I have this much right?:
In a peer-to-peer network, shares with Everyone permissions (Guest inactive) are fairly well limited to local users with accounts on that workstation.
If nothing is changed, except to join a domain, shares with Everyone permissions (Guest inactive) let in all of the Authenticated Users on the network.
??
So, something needs to be done with those Everyone permissions - at least!

I have a Windows desktop application that I need to be used by several people from different locations around the country.
Please advise what I can do about it.
Thanks

Luis R
Mexico