Some of the most frequently asked questions to common problems are listed below. Please take a look at this list before contacting the ukbusiness.com Support desk:
How Can I know if my email is working OK?
There is a simple test that can done to check if you can send and receive email to and from the mail server. If you compose an email and send it to 'test@ukbusiness.com', the mail server will receive it and an auto-response message will be sent back with confirmation that the server is working fine.
Why do I keep getting the same email message(s) again and again?
The mail server does not delete the contents of your mailbox until the entire transaction is completed. If you keep getting the same message(s), you may have a very large message in your mailbox, which is continually only being partially downloaded before you disconnect.
Why do I occasionally get disconnected while reading a Web page or writing E-mail?
- You may have a problem with line noise
- You may wish to ask your Telephone Company to check the phone line. - You may have a call waiting tone
- check that this is not enabled and if it is, disable it before using the modem. - You may be viewing web pages from the hard drive cache.
- This will mean you are not using the modem to get the data, thus there is no activity on the line.
Error 691: The computer you're dialling in to cannot establish a dial-up Networking connection. Check your password and try again?
This error is probably the most common message users receive. This may result from the user accidentally entering an incorrect password, or having the caps lock active when typing it in. Before contacting the ukbusiness.com support desk please check thoroughly that you have set this correctly.
Error 645: The Microsoft Dial-up Adapter is not installed or not responding properly in the network section of control panel, remove the driver and then add it again?
This problem can be caused if the network protocols have become corrupt or are not installed. To check these go to My Computer/control Panel/Network and check that the following components are listed in the 'installed components'.
- TCP/IP-> Dial-up Adapter
- Dial-up Adapter
If they already exist then remove them, restart your machine and then add them again. Please Note that this may prompt you for your windows 95 or 98 installation disk. Once installed you will also need to restart your machine for the changes to take place.
When establishing a dial up connection it seems to take a long time to log on?
This may be because when connecting to the server when it is busy or incorrect settings within Windows 95 or 98. To check this go to My Computer/Dial up Networking then highlight your dial up connection and select properties from the file menu.
- Select the Server Types tab and make sure the 'Log onto Network' is NOT ticked.
- On the general tab, Click the configure button.
- Make sure the 'Maximum speed' is set to 115200.
When I try to make a connection, the computer dials but disconnects straight away?
Check that your modem is correctly installed and your cables are correctly plugged in. If this does not correct the problem you may need to check some settings within Windows.
- Go to My Computer/Dial up Networking and highlight your dial up connection
- select properties from the file menu.
- On the general tab, Click the configure button and select the connections tab. Make sure you have 'Wait for dial tone before dialling' ticked, and 'Cancel the call if not connected within' is set too low. Sometimes windows may default this setting to 0 causing your connection to disconnect straight away.
Error 602: The modem is being used by another Dial up Networking connection. Close the other connection and try again?
Sometimes when a connection is disconnected the modem may not automatically close the port, which it is connecting through. To correct the problem, restart the machine and try again. If the Port remains open try disconnecting and then reconnecting the modem from the computer to solve the problem. If this fails then you should contact the supplier of your modem, as it may be faulty.
Web Site questions
Error Message When Publishing: Web < web name > is busy
The information in this article applies to:
- Microsoft FrontPage 97 for Windows
- Microsoft FrontPage 98 for Windows
SYMPTOMS
When you try to publish a FrontPage Web to the Web server, the following error message may appear:
CAUSE
This problem occurs due to an interrupted connection to the server during the publishing process.
STATUS
Microsoft has confirmed this to be a problem in Microsoft FrontPage 97 for Windows and Microsoft FrontPage 98 for Windows when connecting to a computer running Internet Information Server 2.0 or 3.0. This issue was resolved in Internet Information Server 4.0.
MORE INFORMATION
When the connection to the server is lost during the publishing process,
the Service.lck file remains in the _VTI_PVT directory of the Web.
The Service.lck and Frontpage.lck files deny the FrontPage client access
to a Web on the destination server during publishing.
WORKAROUND
To publish after a lost connection, you must do the following:
On the server, stop and restart the HTTP service.
Delete the file \<Web Root>\<Web Name>\_vti_pvt\service.lck.
Delete the file \<Web Root>\<Web Name>\_vti_pvt\frontpage.lck.
Publish the Web.
Additional query words: Time out busy lock service
How to Publish a Single Page Using the Web Publishing Wizard
The information in this article applies to:
- Microsoft FrontPage 98 for Windows
SUMMARY
This article explains how to publish a single Web page containing FrontPage WebBot components to a sever with FrontPage Server Extensions installed.
MORE INFORMATION
The Web Publishing Wizard can transfer a single file while allowing the
FrontPage Server Extensions to recognise any FrontPage components that
are on that page. To publish a single file to a FrontPage Extended Web
server using the Web Publishing Wizard, follow these steps:
Install the Web Publishing Wizard (latest version) from the Internet Explorer
4.0 product update page at:
<http://www.microsoft.com/ie/ie40/download/rtw/x86/en/download/addonnt.htm>
Click Start, point to Programs, point to Internet Explorer, and then
click the Web Publishing Wizard.
Click Next.
Type the path to the file that you want to publish, or click Browse to
find the file location.
Click New.
Type a Web server name or IP address, and then click Advance.
Select FrontPage Extended Web, and then click Next.
Type the URL or IP address to which you want to post the file and click
Next.
Type the URL or IP address again and click Next.
Click LAN and click Next.
Click Finish.
For more information on using the Web Publishing Wizard, please refer
to your Web Publishing Wizard documentation.
Name and Password Are Not Accepted When Opening Web
The information in this article applies to:
- Microsoft FrontPage 97 for Windows
- Microsoft FrontPage 98 for Windows
SYMPTOMS
When you try to open a Web in FrontPage Explorer, you are prompted for
a name and password. After entering the correct name and password, you
are repeatedly prompted to re-enter your name and password.
A Windows NT Administrator can open the Web in FrontPage Explorer and
verify that the user name is listed and allowed to access this Web, yet
you are unable to open it.
CAUSE
This only occurs when the security is edited with the Fpsrvadm.exe or Fpremadm.exe command-line utilities. User tokens are not refreshed until the server is restarted.
WORKAROUND
There are three methods to work around this problem.
Method 1 (Applies to IIS 4.0) FP2000: "HTTP Error Code 405" Opening or Publishing a Web
The information in this article applies to:
- Microsoft FrontPage 2000
SYMPTOMS
When you open or publish a Web in Microsoft FrontPage 2000, you may receive the following error message:
CAUSE
This problem may occur if FrontPage cannot access the server through
the FrontPage Server Extensions.
The FrontPage Server Extensions are a set of programs that are installed
on the Web Server. They support authoring and administering FrontPage
webs and provide browse-time functionality.
RESOLUTION
If you are opening or publishing to a remote server, contact your Web
Presence Provider and insure that extensions are installed.
If you are opening or publishing to a local web, insure that the server
extensions are installed correctly by using the Microsoft Management Console.
The Microsoft Management Console is located at:
\Program Files\Common Files\Microsoft Shared\Web Server Extensions\40\bin\fpmmc.msc
MORE INFORMATION
For more information on the Microsoft Management Console, click "Help
on MMC" on the Help menu in the Microsoft Management Console.
For more information on FrontPage Server Extensions, click "Help on FrontPage
Extensions" on the Help menu in the Microsoft Management Console.
FP2000: "Socket Code 4" Error Connecting to Server Using SSL
The information in this article applies to:
- Microsoft FrontPage 2000
SYMPTOMS
When you attempt to connect to a Web server using Secure Sockets Layer (SSL), you may receive the following error message:
The server log might also show the following error:
CAUSE
The third-party products included here are manufactured by vendors independent
of Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
FrontPage currently recognises the following certificate authorities:
However, if Internet Explorer 5 is installed on the client computer, FrontPage will recognise all certificates that Internet Explorer 5 recognises.
RESOLUTION
Method 1: Configure the Web Server Software with an SSL Certificate
To allow FrontPage to connect to the server via SSL, configure the Web server software with an SSL certificate from one of the certificate authorities listed in the "Cause" section of this article.
Method 2: Upgrade to Internet Explorer version 5.0.
NOTE: FrontPage supports 40-bit encryption without the use of Internet Explorer version 5.0. If Internet Explorer version 5.0 is installed with 40-bit encryption, then FrontPage will only use 40-bit encryption. If Internet Explorer version 5.0 is installed with 128-bit encryption, then FrontPage can use 128-bit encryption. FrontPage does not support 128-bit encryption.
FrontPage will accept certificates authorities supported by Internet Explorer version 5.0, if Internet Explorer 5 is installed.
FP2000: FrontPage Times Out While Trying to Connect to Server
The information in this article applies to:
- Microsoft FrontPage 2000
SYMPTOMS
When you attempt to open a Web, you may receive the following error message
Where <xxxxx> is a number (IP address).
To work around this problem, use one of the following methods.
Method 1: Use the 127.0.0.1 IP Address
Use the loop back IP Address (127.0.0.1) as the name of the computer you are trying to access. This reserved IP address corresponds to your local computer.
Method 2: Use Localhost
Use localhost as the name of the computer you are trying to access. This reserved host name also corresponds to your local computer.
Method 3: Use at Least One Alphabetical Character
Rename the host computer so that it includes at least one alphabetical
character.
If you are using Microsoft TCP/IP with DHCP and WINS resolution, you must
change the computer name on the Identification tab of the Network Properties
(in the Control Panel).
If you are using Microsoft TCP/IP with DNS for your name resolution, follow
these steps:
Double-click the Network icon.
Click the Configuration tab, click to select TCP/IP from the list, and click Properties.
On the DNS Configuration tab, change the name in the Host box.
CAUSE
The network is attempting to resolve the numeric value as an Internet
Protocol (IP) address, instead of recognising it as the server name.
This problem is caused by the way host names are resolved. If the host
name you are trying to resolve is numeric, the network may assume that
the name is actually an IP address; therefore, the host name is not converted
to an IP address. The network will time out attempting to reach this non-existent
IP address.
FP2000: Multiple Errors Trying to Access Web Sites
The information in this article applies to:
- Microsoft FrontPage 2000
SYMPTOMS
When you try to access an existing Web site, you may receive the following error messages:
the site reports that the item you requested could not be found. 404 Not Found. The requested URL /page was not found on the server.
CAUSE
This error message occurs because FrontPage cannot find the page. This problem occurs when any of the following situations are true:
- You typed the address incorrectly.
- The proxy server setting in FrontPage is invalid.
- You are trying to follow a link created by one of the following components:
NOTE: These are browse-time components, which require the server extensions to be installed in order to work. The links are valid, but the browser is unable to find the corresponding page until the server extensions are installed.
- The Web folder was deleted.
- The Web content was moved.
RESOLUTION
To work around this problem, use the appropriate method for your situation.
Method 1: If You Typed the Address Incorrectly
Ensure that you typed the Uniform Resource Locator (URL) correctly. If it is incorrect, retype the URL correctly and try again.
Method 2: If the Proxy Server Is Invalid
FrontPage allows you to specify a proxy server. To verify that the server is correct, follow these steps:
In the Internet Properties dialog box, click Connections, and then click LAN Settings.
In the Local Area Network (LAN) Settings dialog box, verify that the Proxy address is correct. If the Proxy address is correct, confirm that the proxy is functioning properly.
Method 3: If You Are Using Browse-time FrontPage Components
The browse-time FrontPage components require the FrontPage Server Extensions to function. If the FrontPage Server Extensions are not installed on the Web server, the Web server administrator must run the Microsoft Management Console and install the appropriate server extensions to the Web server that you are using.
Method 4: If the Web Folder Was Deleted
If you deleted the folder that contains all of your Web pages, FrontPage still maintains pointers to that information in another file.
Method 5: If the Web Content Was Moved
If you moved your content from its original location, move it to its original location, start the Microsoft Management Console, uninstall the server extensions, and then move the content where you want it and reinstall the FrontPage Server Extensions.