GETTING PALTALK TO WORK WITH YOUR FIREWALL OR NETWORK.Firewalls require some special configuration to work properly with PalTalk.
PalTalk is a relatively new program so many firewalls do not have standard
configuration available yet. This means that you may have to manually set your
firewall up to allow PalTalk to communicate over the internet. If you are running
a hardware router or configurable dsl or cable modem may need to open ports
on these ports also.Due to the vast array of products, and combinations of products that you may
be running on your system, we cannot give you help in this area beyond suggesting that you consult your documentation for configuration instructions or more help. You may also want to check the manufacturers web sites to see if they have any updates or pre made configuration scripts for paltalk.
A word about 'Firewall / Network support':
(box 6 under the advanced sound controls tab under setup)This forces PalTalk into TCP/IP mode for group voice and should NOT be used
unless you are using a network or other device or software that leaves no alternative but to use it.
Using a proxy server or NAT with PalTalk.If you are using a Proxy server or NAT you must configure it to be used
with PalTalk. You MAY have audio problems if you have and external
dsl or cable modem due to the fact that SOME of these modems contain
hardware firewalls or routers. If you do not configure properly you may
experience reduced functionality, including loss of audio, no video, and no
file transfer capability.
Ports used for PalTalk:
|
|
||
| TCP | 2090 | file transfer |
| UDP | 2090 | voice stream |
| TCP | 2091 | video listening port |
| UDP | 2091 | control stream |
| TCP | 2095 | file transfer - (older versions) |
| Outbound ports | ||
| TCP | 5001-5020 | text messaging |
| TCP | 8100-8700 | firewall / network mode group voice |
| UDP | 8100-8700 | group voice |
| UDP | 1024-2500 | voice stream - user configurable |
| UDP | 1024-2500 | control stream - user configurable |
The last 2 UDP outbound ports are usually set in pairs. 1024 - 1025, 1026 - 1027, etc... Most users never have to set these lower two ports. They are dynamically assigned if you leave the lower two boxes set to 0's on the 'paltalk port settings' tab.Outbound ports are usually not an issue but are listed here for network users who
may need to manually configure for a proxy or NAT server or other hardware device.
Using a proxy server or NAT with PalTalk.If you are using a Proxy server or NAT you must configure it to be used
with PalTalk. You MAY have audio problems if you have and external
dsl or cable modem due to the fact that SOME of these modems contain
hardware firewalls or routers. If you do not configure properly you may
experience reduced functionality, including loss of audio, no video, and no
file transfer capability.
I use SyGateI have an external dsl or cable modem and have audio problems
SyGate:This section assumes that your network is installed and
running properly and that you are familiar with SyGate.If you need to familiarize yourself with how SyGate works, go here...
http://www.sybergen.com/support/documents/applications.htmYou may find more help here from practicallynetworked.com.
PalTalk uses certain ports on your computer to stay in contact
with our servers and for various other functions. If you are using
SyGate you must allow these ports to communicate over the net.To open up these ports for communication you must edit the Apprule.cfg
file in your SyGate folder. When you are done you must STOP, then
RESTART the SyGate service for your changes to take effect.
This must be done on your SERVER machine.Open Windows Explorer
Go to the C:\Program Files\SyberGen\SyGate directory.
RIGHT CLICK on the Apprule.cfg file and select OPEN WITH when the menu pops up.
Select NOTEPAD and be sure to remove the check mark from the box that says always use this program to open this type of file.
If you don't get an "open with" when right clicking on the Apprule.cfg file, just RENAME it to Apprule.txt for now. When done editing you can just rename it back to Apprule.cfg. You will get a warning message about changing file types but it's ok. Just open it with notepad.
There is one trigger port associated with PalTalk. There is also the possibility that you may be logging directly into a message server by bypassing the PalTalk router. As of now SyGate does not support setting a range of ports for triggering. Therefore this script contains 20 sub-sections.
Insert this script somewhere in between the other little scripts you see......# PalTalk1
:INIT "PalTalk1"
OUT TCP 5001 5001 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk1
:INIT "PalTalk1"
OUT TCP 5002 5002 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk3
:INIT "PalTalk3"
OUT TCP 5003 5003 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk4
:INIT "PalTalk4"
OUT TCP 5004 5004 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk5
:INIT "PalTalk5"
OUT TCP 5005 5005 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk6
:INIT "PalTalk6"
OUT TCP 5006 5006 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk7
:INIT "PalTalk7"
OUT TCP 5007 5007 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk8
:INIT "PalTalk8"
OUT TCP 5008 5008 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk9
:INIT "PalTalk9"
OUT TCP 5009 5009 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk10
:INIT "PalTalk10"
OUT TCP 5010 5010 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk11
:INIT "PalTalk11"
OUT TCP 5011 5011 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk12
:INIT "PalTalk12"
OUT TCP 5012 5012 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk13
:INIT "PalTalk13"
OUT TCP 5013 5013 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk14
:INIT "PalTalk14"
OUT TCP 5014 5014 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk15
:INIT "PalTalk15"
OUT TCP 5015 5015 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk16
:INIT "PalTalk16"
OUT TCP 5016 5016 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk17
:INIT "PalTalk17"
OUT TCP 5017 5017 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk18
:INIT "PalTalk18"
OUT TCP 5018 5018 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk19
:INIT "PalTalk19"
OUT TCP 5019 5019 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END# PalTalk20
:INIT "PalTalk20"
OUT TCP 5020 5020 0.0.0.0 0 R
:SUB
IN TCP 2090 2091 0.0.0.0 0 0 AD
IN UDP 2090 2091 0.0.0.0 0 0 AD
IN TCP 2095 2095 0.0.0.0 0 0 AD
IN TCP 5001 5020 0.0.0.0 0 0 AD
IN TCP 8100 8700 0.0.0.0 0 0 AD
IN UDP 8100 8700 0.0.0.0 0 0 AD
OUT UDP 1024 2500 0.0.0.0 0 D
OUT TCP 2090 2091 0.0.0.0 0 D
OUT TCP 2095 2095 0.0.0.0 0 D
OUT TCP 5001 5020 0.0.0.0 0 D
OUT TCP 8100 8700 0.0.0.0 0 D
OUT UDP 8100 8700 0.0.0.0 0 D
:END
Q. I use Windows Internet Connection Sharing (ICS), how do i configure it for PalTalk?
A. This answer comes from one of our beta testers! Thanks Sam! (aka jjonkers on PalTalk)ICS is a NAT based system that first surfaced with Windows98. It requires special configuration and is not for the weak of heart. Help and a free configuration program is available at.... http://www.practicallynetworked.com. Go directly to the ICS section here.
Click here to get the ICS Configuration program.
WinProxy:Winproxy requires special configuration to allow PalTalk to work. Check their site here... http://winproxy.com/ Check their Tech Support area for the most up to date information available. All aspects of setting up your network with winproxy are available here. Be sure you make note of the port information that you will need while configuring winproxy. (Located at the top of this page.)
To use WinGate you need to map all of the ports that PalTalk uses. Check http://kb.deerfield.com/index.cfm?a=1057&k=1&CFID=167917&CFTOKEN=83328949
WinGate:Check the WinGate help desk at http://wingate.deerfield.com/helpdesk. This should help you with many common problems that you run into.
for information about port mapping with your version of WinGate.
If you have a configuration that works well and would like to contribute to this area please email admind@paltalk.com and we will include your information here.
Linux Firewall:
courtesy of VinnyAz (palsupport)This script depends on kernel 2.4.x
The author of rc.firewall is working to incorporate our changes into the next version of the script.
Compile the kernel with full netfilter support.
Install iptables.
Copy this script to an appropriate directory, such as /usr/local/bin, and edit it to reflect the ip addresses of your network. Other ports can be added to the configuration section to enable any other applications you may need to run.
Symlink the script to an init directory that will execute it on boot, this will vary by distribution.
I have tested this script on Debian, and video, audio and file transfer all work behind the firewall. Self test video doesn't work, so you will need someone else to test with.
Please do not contact Paltalk as they are just making this available through their web site for your convenience and have nothing to do with the script or this README. Check Vinny's site for updates at http://www.cybertrails.com/~monte/
I would like to thank Eddie Baker for all his work on the script to allow it to accept port ranges and making it all work.
This script is being made available as-is and carries no warranty.
External modem with hardware firewall or router:
Internet service providers usually supply external modems for connection to dsl or cable service. SOME of these modems contain hardware firewalls or routers. If you have no incoming, or possibly no outgoing audio, and have one of these modems you must configure the modem to allow traffic through the ports that PalTalk uses.
The first thing that you should do is press the SETUP button on your PalTalk buddy list. Then select the PALTALK PORT SETTINGS tab. On the bottom of this screen you will see two boxes with zeros in them. Enter any two numbers that you can configure easily through your modem. This will fix those ports (which are usually dynamically assigned) to the numbers that you specify. You should usually pick two numbers between the range of 1024 and 3000. I use 1096 and 1097. Now that you have these udp ports set to fixed numbers, you MAY be able to speak and / or hear. If not you will have to program your modem to allow traffic on the ports that PalTalk uses to communicate over the Internet
If you cannot program the modem yourself you will have to get someone from your ISP to do it for you. If they cannot or will not do this, you will have to switch to a dialup modem to connect to PalTalk. We are sorry, but some ISP's restrict your service by closing ports. There is nothing that we can do for you in this situation.
Information on Cisco 675 routers is available here. Thanks to Pandora for this info!
General networking info from practicallynetworked.com:If you are having problems in general or are new to home networking, you may want to visit http://www.practicallynetworked.com for more information. This is a rather complete site and may be very helpful to you. Visit the troubleshooting section by clicking here.