faq:bad_behaviour_no_terminals_available
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| faq:bad_behaviour_no_terminals_available [2007/01/31 17:33 (17 years ago)] – bob | faq:bad_behaviour_no_terminals_available [2007/01/31 17:33 (17 years ago)] – bob | ||
|---|---|---|---|
| Line 25: | Line 25: | ||
| ==== Cause ==== | ==== Cause ==== | ||
| * The error was caused by the firewall on the server having been configured to block TCP/IP traffic from the client PC | * The error was caused by the firewall on the server having been configured to block TCP/IP traffic from the client PC | ||
| + | |||
| ==== Resolution ==== | ==== Resolution ==== | ||
| We turned off the Firewall and everything worked. | We turned off the Firewall and everything worked. | ||
| - | -Enable NetBios over TCP/IP | + | - Ordered List Item |
| - | -Remove any bad hosts file entrys in c: | + | |
| - | -Set TCP/IP timeouts to avoid the two hour delay (see article...) | + | - Remove any bad hosts file entrys in c: |
| - | -Ensure that Name Resolution (DNS) is working properly by pinging Pervasive server by DNS name and correct IP is returned | + | - Set TCP/IP timeouts to avoid the two hour delay (see article...) |
| - | -Ensure System has R/W access to data files | + | - Ensure that Name Resolution (DNS) is working properly by pinging Pervasive server by DNS name and correct IP is returned |
| + | - Ensure System has R/W access to data files | ||
faq/bad_behaviour_no_terminals_available.txt · Last modified: 2007/02/01 19:41 (17 years ago) by lawrence