Router and Firewall Configuration
Your router and firewall protect your network from unauthorized access while allowing legitimate ProPay WEB traffic. This guide explains how to configure your router and firewall to enable external client access to your ProPay WEB server.
Understanding Routers and Firewalls
What is a Router?
A router connects your local network to the internet. It:
- Shares one internet connection among multiple computers
- Assigns local IP addresses to network devices
- Routes traffic between your network and the internet
- Provides network address translation (NAT)
What is a Firewall?
A firewall protects your network by controlling incoming and outgoing traffic. It:
- Blocks unauthorized connection attempts
- Prevents malicious traffic from reaching your computers
- Allows legitimate traffic you specifically permit
- Logs security events for review
Most modern routers include a built-in firewall, protecting your entire network from a single device.
Before You Begin
Gather this information before configuring your router:
- Router's IP address (default gateway)
- Router's administrative username and password
- Server's internal static IP address
- Port number for ProPay WEB (usually 80 for HTTP, 443 for HTTPS)
- Your external static IP address from ISP
> Important: Paysoft personnel are not trained in router configuration. Contact your router manufacturer's technical support or your IT professional for assistance. For step-by-step router-specific guides, visit http://portforward.com/.
> Important: If you don't have administrative access to your router, contact your IT administrator or network manager.
Accessing Your Router Configuration
Find Your Router's IP Address
- Open Command Prompt on any networked computer
- Type `ipconfig` and press Enter
- Find Default Gateway (e.g., 192.168.1.1)
- This is your router's IP address
Log Into Router Interface
- Open a web browser
- Enter your router's IP address in the address bar
- Press Enter
- Enter the administrative username and password when prompted
Common Default Credentials:
| Router Brand | Default Username | Default Password |
|---|---|---|
| Linksys | admin | admin or (blank) |
| Netgear | admin | password |
| Cisco | admin | admin |
| D-Link | admin | (blank) |
| TP-Link | admin | admin |
| Asus | admin | admin |
| Belkin | (blank) | (blank) |
> Security Note: If you're still using default credentials, change them to a strong password immediately after configuration.
Router Interface Not Loading
If you cannot access the router interface:
- Verify you're connected to the router's network
- Try a different web browser
- Clear your browser cache and cookies
- Disable VPN if running
- Power cycle the router and try again
- Check router documentation for specific access instructions
Configure Router for Static IP
Your router needs to use your ISP's static IP address instead of obtaining one automatically.
Change WAN Connection Type
- In router interface, find WAN, Internet, or Setup section
- Locate Connection Type or WAN Connection Type
- Change from Automatic (DHCP) to Static IP
- Enter information from your ISP:
- Static IP Address: Your ISP-assigned public IP
- Subnet Mask: From ISP (usually 255.255.255.0)
- Default Gateway: From ISP
- Primary DNS: From ISP
- Secondary DNS: From ISP
- Save settings
- Restart router if prompted
- Return to router interface
- Check Status or WAN Status page
- Verify IP Address shows your static IP from ISP
- Confirm Connection Status shows "Connected"
- Test internet connectivity from a computer on your network
- External: 208.57.66.39:80 → Router receives traffic
- Router forwards to: 192.168.1.2:80 → ProPay WEB server
- Find Port Forwarding, Virtual Server, NAT, or Applications & Gaming section
- Click Add, Create, or similar button
- Enter forwarding rule details:
- Enter: ProPay WEB
- Enter: 80
- Enter: 80
- Enter: Your server's internal static IP (e.g., 192.168.1.2)
- Enter: 80
- Select: TCP or Both (TCP/UDP)
- Check: Enable or Active
- Save or apply the rule
- Create a second forwarding rule
- Use the same settings as above except:
- Service Name: ProPay WEB HTTPS
- External Port: 443
- Internal Port: 443
- Save the rule
- Click Applications & Gaming
- Click Single Port Forwarding
- Enable a numbered line
- Enter application name and ports
- Enter server IP address
- Click Save Settings
- Click Advanced or Advanced Setup
- Click Port Forwarding/Port Triggering
- Click Add Custom Service
- Enter service name and port information
- Enter server IP address
- Click Apply
- Click Applications & Gaming
- Click Port Range Forward
- Enter application name
- Enter start and end ports
- Enter server IP address
- Check Enable
- Click Save Settings
- Click Forwarding
- Click Virtual Servers
- Click Add New
- Enter service port and IP address
- Select protocol
- Click Save
- Find Security, Firewall, or Advanced Security section
- Verify firewall is enabled
- Look for any settings blocking incoming connections
- Ensure port forwarding rules override general firewall blocks
- Should be: Enabled
- This is good - allows established connections while blocking unsolicited traffic
- Should be: Enabled
- But port forwarding rules should override this for specific ports
- Should be: Disabled
- Don't use DMZ for ProPay WEB - use port forwarding instead for better security
- Find Access Rules, Inbound Rules, or Firewall Rules
- Add a new inbound rule:
- Service: HTTP (port 80)
- Action: Allow
- Source: Any/Internet
- Destination: Server IP
- Add another rule for HTTPS (port 443) if using SSL
- Save rules
- On the server, open Control Panel
- Click Windows Defender Firewall or Windows Firewall
- Click Allow an app or feature through Windows Firewall
- Click Change settings (requires administrator)
- Scroll down and find World Wide Web Services (HTTP)
- Check both Private and Public columns
- If using SSL, also check Secure World Wide Web Services (HTTPS)
- Click OK
- In Windows Firewall, click Advanced settings
- Click Inbound Rules in left panel
- Click New Rule in right panel
- Select Port and click Next
- Select TCP and enter 80 in specific ports
- Click Next
- Select Allow the connection
- Click Next
- Check all three: Domain, Private, Public
- Click Next
- Name the rule: ProPay WEB HTTP
- Click Finish
- On the server, open a web browser
- Go to `http://localhost`
- Verify you see IIS welcome page or ProPay WEB login
- On another computer on your network, open a web browser
- Go to `http://[server-internal-ip]` (e.g., http://192.168.1.2)
- Verify you see the same page
- From outside your network (use mobile data or ask someone external), open a browser
- Go to `http://[external-static-ip]` (e.g., http://208.57.66.39)
- Verify you see ProPay WEB login page
- https://www.canyouseeme.org - Enter port number and click "Check Port"
- https://www.grc.com/x/portprobe=80 - Tests port 80 directly
- http://www.yougetsignal.com/tools/open-ports/ - Enter port number to test
- Access router configuration
- Find Administration, Management, or System section
- Click Change Password or Set Password
- Enter current password
- Enter new strong password (12+ characters, mixed types)
- Save changes
- Document new password securely
- Find Remote Management or Remote Access setting
- Set to Disabled
- This prevents internet users from accessing router settings
- You can still manage router from your local network
- Find Logs, Logging, or System Log section
- Enable logging
- Review logs periodically for suspicious activity
- Look for repeated failed connection attempts
- Check router manufacturer's website for firmware updates
- Download latest stable version
- Follow manufacturer instructions to update
- Never interrupt firmware update process
- Router will restart after update
- Find wireless security settings
- Use WPA2 or WPA3 encryption (not WEP or WPA)
- Set a strong wireless password
- Hide SSID broadcast (optional but helps)
- Power cycle the router
- Wait 30 seconds before turning back on
- Try accessing again
- If still fails, perform factory reset (last resort)
- Verify server's internal IP hasn't changed
- Confirm port forwarding rule is enabled
- Check Windows Firewall on server
- Verify IIS is running on server
- Test with firewall temporarily disabled (testing only)
- Contact ISP - they may block port 80
- Use a different port (e.g., 8080, 5899)
- Update port forwarding to use new port
- Configure IIS to listen on new port
- Clients access via http://yourdomain.com:8080
- Only one server can use external port 80
- Use port 80 for primary server
- Use alternate ports (8080, 8081) for others
- Or use a reverse proxy to distribute traffic
- System Requirements
- Static IP Setup
- Iis Setup
- SSL Certificate Setup
- Troubleshooting Connections
- Security Best Practices
Verify WAN Configuration
After router restarts:
Configure Port Forwarding
Port forwarding directs incoming internet traffic to your ProPay WEB server.
Understand Port Forwarding
When a client connects to your external IP address on port 80, the router needs to know which internal computer should receive that traffic. Port forwarding creates this mapping.
Example:
Create Port Forwarding Rule
Application/Service Name:
External/Start Port:
External/End Port:
Internal/Server IP Address:
Internal/Server Port:
Protocol:
Enable:
> Note: Some routers only require the last octet of the internal IP address. For example, if your server is 10.0.0.1, enter 1 in the IP address field. Check your router's documentation if the full IP address does not work.
> Note: Port 80 is standard for HTTP. If port 80 is in use or blocked by your ISP, you can use an alternative port such as 5899, 8080, or 8888. The port number must match in three places: router port forwarding, IIS website TCP port setting, and Windows Firewall exception. When using a non-standard port, clients must include it in the URL (for example, http://yourdomain.com:5899).
Add HTTPS Port Forwarding (If Using SSL)
If you use SSL certificates for HTTPS:
Port Forwarding Examples by Router Brand
Linksys:
Netgear:
Cisco:
TP-Link:
Configure Firewall Rules
Your router's firewall must allow incoming traffic on forwarded ports.
Check Firewall Settings
Common Firewall Settings
SPI Firewall (Stateful Packet Inspection):
Block WAN Requests:
DMZ (Demilitarized Zone):
Allow Specific Ports
Some routers require explicitly allowing ports:
Configure Windows Firewall on Server
Your server's Windows Firewall must also allow web traffic.
Allow IIS Through Firewall
Create Custom Firewall Rule (Alternative Method)
If IIS is not listed in allowed apps:
Repeat for port 443 if using HTTPS.
Verify Port Forwarding Configuration
Test that your configuration works correctly.
Test Local Access
If this fails: Check IIS installation and Windows Firewall.
Test Internal Network Access
If this fails: Check server static IP and Windows Firewall.
Test External Access
If this fails: Check router port forwarding and firewall rules.
Use Online Port Checker
Test if port 80 is open to the internet using any of these free tools:
If the test shows the port is closed, review your router and firewall configuration.
Security Best Practices
Change Default Router Password
Disable Remote Administration
Prevent external access to your router's configuration:
Enable Logging
Track connection attempts and security events:
Update Router Firmware
Keep your router secure with latest firmware:
Use Strong Encryption
If your router handles wireless connections:
Troubleshooting
Cannot Access Router After Changes
Problem: Cannot log into router after configuration changes.
Solution:
Port Forwarding Not Working
Problem: External clients cannot connect despite port forwarding.
Solutions:
ISP Blocks Port 80
Problem: ISP blocks residential customers from hosting on port 80.
Solution:
Multiple Servers Need Port 80
Problem: Need to run multiple web servers on one network.
Solution:
Router-Specific Resources
For detailed instructions specific to your router model:
Linksys:
Netgear:
Cisco:
TP-Link:
Asus: