Tag Archives: Windows

Windows Network Discovery won’t stay on KB1039350

KB1039350

Description:  Windows Network Discovery won’t stay on

Common customer description:

“Cannot view computers on the network even after we try turning on Network Discovery.”

Probing questions:

When did this start happening?
Is it just you or everyone?
Any changes made lately?
Any odd pop-ups or “weird” activity on the computer that isn’t there normally?

Steps to isolate:

Remotely connect to computer.
Check the Windows Firewall Advanced settings inbound and outbound port settings.  Are they all listed?

Steps to resolve:

If the customers computer has been or is infected the infection very well could have removed much needed default firewall port settings.  Under the “Group” heading you should have “Network Discovery” among several others.  If it is missing it needs to be repaired.  Click on Restore Default Policy.

firewall

If you receive an Error 3 or Error 5 you will need to run ServicesRepair.exe from ESET.  This tool restores the default settings and replaces the missing port rules.  After it has finished it will ask to reboot the computer.  After the reboot everything should now be back in working order.  Test by turning on “Network Discovery” and also check Windows Firewall Advanced Settings to see if the rules have returned.  If all is as it should be you are finished.  If still not working consult a Tier 2.

Additional considerations:

http://kb.eset.com/library/ESET/KB%20Team%20Only/Malware/ServicesRepair.exe

https://social.technet.microsoft.com/Forums/windows/en-US/78fbca5c-41ad-4fa6-8ccd-f52045333fdd/windows-7-firewall-fails-to-restore-default-policy-error-3?forum=w7itprosecurity

https://social.technet.microsoft.com/Forums/windows/en-US/5366225a-46e7-4d6c-a389-8bd18a5c3aad/windows-firewall-damaged-by-windows-7-antivirus-2012?forum=w7itprosecurity

VPN Client Setup – The Basics KB1039291

KB1039291

VPN Client Setup

Windows VPN CLients
Cisco IPSec
Cisco SSL
Sonicwall IPSec
Sonicwall SSL
PPTP

MAC VPN CLients
Cisco IPSec
Cisco SSL
Sonicwall SSL
PPTP

What is VPN?
Virtual Private Network. Communicates from remote network to private network.

Why do we need it?
Securely access computers, files, connecting Outlook to Exchange remotely.

How do I set it up?
There are several different VPN clients to use.

What info is needed?
Local user or domain login, public IP/domain name, VPN group name, pre-shared key, username, and password.

Authentication methods
LDAP – Allows applications running on almost any platform to obtain directory info.
RADIUS – Authenticates to a RADIUS server installed on Active Directory.
Local Accounts – Uses local user accounts on the firewall itself.

When is it billable?
VPN client installs are non-billable. Troubleshooting connections are billable.

Public vs Private IPs
There are static and dynamic addresses.
Public IPs face outward to the internet.
Private IPs are for internal networks.

PCF files
Profile Configuration File. Automatically configures VPN client when imported.

TCP and UDP
Transmission Control Protocol (TCP) is a connection-oriented protocol.
User Datagram Protocol (UDP) is a connectionless protocol.
TCP will wait for information if it gets lost during delivery. UDP will not.

VPN Process
How the connection process unfolds

Installation
Communication
Authentication
Establishing a connection
Connected

Picture1

Try the VPN connection on your computer

Connection
Authentication
Group issues

The client only partially installs
Check to see if there is an error code
Uninstall the client
Clear temp files
Remove other VPN clients*
Reboot

Status stuck on “Connecting”
Ping Public IP or VPN domain name
New ISP or other ISP issue
Connectivity at remote location
Office down

Same subnet
192.168.0.x on both remote and office locations

See if their AV blocks communication
Trend Micro
Symantec
AVG

See if their firewall blocks communication
Windows Firewall

Find out if ports are blocked
Telnet
Open Command Prompt
Type telnet PublicIPAddress port

Picture2

Picture3

Common VPN ports
TCP 1723
TCP 1701
UDP 500
TCP 4500

Allow inbound and outbound ports
Start > Control Panel > Windows Firewall > Advanced Settings > Inbound Rules (or Outbound Rules) >
New Rule > Select Port > Click Next > Select which protocol (TCP or UDP) > Select Specific local ports > Type port or port range > Click Next > Select Allow the connection > Click Next > Select Domain, Private, and Public > Click Next > Name the rule > Click Finish >

Picture4

Picture5

Picture6

Picture7

Picture8

Picture9

Picture10

Cannot get past the group name or username screen
Check spelling
Case sensitive usernames
Verify username
Reset password

VPN connects, but there is no access to anything

Same subnet or wrong subnet
192.168.0.x on both office and remote locations
APIPA address – 169.254.x.x

Connect by IP or Fully Qualified Domain Name
Servername.domain.local instead of servername

Reinstall the VPN client.
Remove VPN client
Reboot
Reinstall

Consult Tier 2
Less common issues (Example: DNE Update for Cisco)
Firewall configuration
Escalate

Connecting to a firewall

Find the information to connect to a firewall
Sonicwall
Cisco

 

Put the IP address into a browser
May need to specify https:// and/or port number
Common ports: 8080 and 4443.
https://ipaddress:port

Picture12

Picture13

Picture14 Picture15 Picture16

Multiple consoles
ASDM
SSH (PuTTY)

Setting up a local user in the firewall
Sonicwall
Cisco

Local versus AD accounts


Local

LDAP not supported
Few users allowed
Not using Active Directory
ADPreferred authorization method
Less hassle on user’s end

Connect to Sonicwall Navigate to:
Users > Local Users > Add User… > Enter username and password > Go to Groups tab >

Picture17

Check Groups – Everyone, Trusted Users, and VPN
Highlight group name

Click the right arrow below to send it to Member Of:
Go to VPN Access tab

Picture18

Go to VPN Access tab
Find “Firewalled Subnets” under Networks and Highlight it
Click the right arrow below to send it to the Access List
Click OK

Picture19

Connect to Cisco Navigate to:
Configuration
Remote Access VPN
AAA/Local Users
Local Users
Click Add
Enter username and password
Set privilege to No ASDM, SSH, Telnet, or Console access
Click OK
Click Apply
Click Save

Picture20

Cisco Meraki
Escalate to Tier 2

Domain User Setup
Setting up or modifying a domain user
Active Directory

Suggested account setup
Username = (First initial of first name)(last name)
Password = Password1

Password settings
Uncheck all settings

Picture21

Picture22 Picture23

Uses Routing and Remote Access
Active Directory group
Dial-in tab
Local firewall user

Picture24

VPNs on laptops

Will not affect work functionality

How users might ask
“I need to get to my folders”
Could mean desktop folders (RDP)
Could mean server folders (Mapped Drives)

Verify
Can they access the resources they were calling in about?

Windows Sonicwall SSL Setup KB1039287

KB1039287

Windows Sonicwall SSL Setup

1. Install the client.
a. With some setups, you can go to a website in a browser, login with network username/password, and download the client. This will automatically set up the client for connection. Skip to step 4.

2. Find the information to connect

3. Creating a new connection

a. Open Sonicwall NetExtender client.
b. Enter the Public IP or fully qualified domain name.
c. Enter username/password.
d. Enter domain name.

213

 

4. Attempt connection.
a. Click Connect.
b. You should now be connected. Depending on how the client would like to use their VPN, we may need to set up an RDP connection, mapped drives, Outlook, etc.

Windows Sonicwall IPSec Setup KB1039282

KB1039282

Windows Sonicwall IPSec Setup

1. Install the client.
a. There are 32 bit and 64 bit versions. Be sure that the VPN client version matches the OS version. Go to Start -> right click Computer -> Properties -> System -> System type.

2. Find the information to connect

3. Creating a new connection

a. Open Sonicwall Global VPN Client
b. Click the + sign for a new connection
a. Click Next. Make sure Remote Access is selected. Click Next
b. Enter the Public IP or fully qualified domain name. Give the connection a name. Click Next.
c. Click Finish.

 

4. Attempt connection.
a. Highlight the connection. Click Enable.
b. Enter pre-shared key.
c. Enter credentials.
d. You should now be connected. Depending on how the client would like to use their VPN, we may need to set up an RDP connection, mapped drives, Outlook, etc.

 

Windows VPN PPTP Setup KB1039263

KB1039263

Windows VPN Settings

Start > Control Panel > Network and Sharing Center > choose “Setup a new connection or network”

1

Then choose “Connect to a workplace”

2

You may be prompted to use a connection that you already have. Choose “No, create a new connection”
Next you need to choose “Use my internet connection (VPN)”

3
Now you will need to enter the Internet Address. In our case it is mail.srweidema.com, and check the box at the bottom “Don’t connect now, just set it up so I can connect later”

4

You will then be prompted for a Username/Password/Domain. We can just leave these blank for the time being. Click “Create”
Locate the VPN we just created under Start > Control Panel > Network and Sharing > Look in the top left for “Change adapter settings”

5

Now find the VPN you just created. Right click on the VPN and create a shortcut ( will be placed on the desktop)

6

Locate your VPN icon on the desktop and double click it.

7

Fill out the username, password ( these are the same credentials the users would use to log into their desktops) and the domain.

8

Then choose Properties on that window. On the top of the properties box you will have a couple tabs. Choose the “Security” tab and make sure the Type of VPN: Is Point to Point Tunneling Protocol.

9

That is all you will have to do to configure the VPN on a new workstation. BUT we still need to give the new user rights to access the network remotely.
To give a user rights to use the VPN log into the SR2k8 Server with admin rights and open Active Directory Users and Computers. ( Start menu -> Administrative tools)
Expand SRWeidema.local, then expand “My Business”, expand “Users”, then expand “SBSUSERS” and locate the user we want to allow VPN rights and double click their name.

10

This will open the Properties for that user. Under the properties menu you need to select the “Dial In” tab and check “Allow access”

11

That is it! The user Paul Carter now has access to use our VPN with his credentials.

Windows Cisco SSL Setup KB1039233

KB1039233

Windows Cisco SSL Setup

1. Install the client.

2. With some setups, you can go to a website in a browser, login with network username/password, and download the client. This will automatically set up the client for connection. Skip to step 4.

3. If you are installing this on your computer, open the folder cisco anyconnect client install extracted and run setup.exe.

4. If you are installing this on a remote computer, send the folder cisco anyconnect client install zipped.zip to them, extract, and run setup.exe.

5. Find the information to connect

6. Creating a new connection

7. Open Cisco AnyConnect Secure Mobility client.

8. Enter the Public IP or fully qualified domain name.

9. Attempt connection.

10. Click connect.

11. Enter username and password.

12. You should now be connected. Depending on how the client would like to use their VPN, we may need to set up an RDP connection, mapped drives, Outlook, etc.