Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
WinInet
 |
- !!NEWSFLASH!!
- !Limitations of the WinInet FTP Functions
- !List of Win32 Error Codes
- 12003 ERROR_INTERNET_EXTENDED_ERROR
- 12007 Error
- 12163 error trying to trying to open an FTP session
- Active vs Passive FTP Connections
- Allowing User to Accept Cookies
- Ascii vs Binary FTP Transfers
- Automating Web forms with Cookies
- Can WinInet Handle Framed Pages
- Change Phone Number of Connectiod-Ras entry
- Check for IE4
- Check if a File has been Modified on Web Server
- Check if FTP File Exists
- Check if iUrlOpen returns what your expecting
- Cookies Wont Go Through
- Delete Temporary Internet Files Cache
- Dialog Progress Bar not Working
- Download a Message directly to a Binary buffer
- Embed User Id and Password in URL
- Error 12045 Invalid Certificate
- Error 307 File Access Failed
- Error 321 iFtpFindNext failed
- Error code 632 on WinInet dial-up
- ERROR with iOptionSet
- FTP Directory Exist
- FTP File Exist
- Ftp Functions and OpenVms
- Ftp Issue with Large File Transfers
- FTP Keep Alive
- FTP Proxy Server and Passive Transfer
- FTP SSL
- FtpListFileNames UDF
- Get Wininet Error Description String
- Get Real Internet Address
- Get WinInet Error Description String
- Getting ERROR on iHttpOpen with HTTPS
- Handle Http Redirect
- How to Specifiy HTTP User Agent
- How to use iGetConState
- How to Use iHttpOpen - Do a Post - and Grab HTML
- HTTP and WinInet - An Opus
- HTTPDownload 1.4
- iBegin and Firewalls
- IE4 Dlls needed for Wininet Extender on 95
- iFtpCmd and MDTM command
- iFtpCmd and Quote Site
- iFtpCmd APPE Causes iWriteData to Crash using IE 7
- iFtpCmd APPE Example
- iFtpCmd Issues
- iFtpCmd RETR Crash on Windows 7 32-bit WinInet Only
- iFtpDirMake Error 318
- iFTPFileSize 300 Error FileOpen Failed
- iFtpFindInit Memory Leak
- iFtpFindInit Returns Zero
- iFtpFindInit Wildcards
- iFtpFindNext Problem with Date
- iFtpGet Newer Files Only
- iFtpGet to get INI file
- iFtpGet Wininet Error 12031
- iFtpPut Error 12002 ERROR_INTERNET_TIMEOUT
- iFtpPut Error 12003
- iFtpPut to Unix Server
- iGetConState Return Values
- iGetConState Returns False
- iGetConState(0) Returns 1 for No Connection
- iGetLastError Always Returns 2 with IE5
- iHostConnect and Return Codes
- iHostConnect Error 65535
- iHttpInit and 401 Error
- iHttpOpen Error 406
- iHTTPOpen Error Message 12044 ERROR_INTERNET_CLIENT_AUTH_CERT_NEEDED
- iHTTPOpen Not Returning 404
- Installation of a Certificate
- InternetCookieSetEx and InternetCookieGetEx
- iOptionSet Error
- Latitude and Longitude of An Address
- Logfile of FTP Session
- Make a WHOIS Request
- Multiple FTP Sessions
- Non Standard Port
- Post HTML Problem
- Print a Web Page
- Progress bar during HTTP download
- Removing Empty Directories with FTP
- Require Certificate for HTTPS Downloads
- Return Info on Web Server
- Sample code - Weather Watch
- Secure FTP Issues
- Select Links That Contain Java Script Code
- Syncronize FTP
- UrlEncode of Hebrew characters
- Website Forms with Viewstate and Eventvalidation
- Wininet and Cookies
- WinInet and JavaScript
- WinInet and OpenVMS Problem
- WinInet Errors
- WinInet Not Supported for Use in Services
- Yahoo Signin Form
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
iBegin and Firewalls
Keywords: iBegin Firewalls
Here's what I've discovered about firewalls (at least the way ours works) - more than I wanted to know! I'll describe what I found out for those who may run into this.
- The iBegin command must specify the firewall IP address or iHttpOpen won't work later. So, iBegin(1,"192.168.1.4:8080","") is the answer.
- The iOptionSet isn't necessary to set the usercode and password for the firewall. This is done on the iHostConnect command.
- iHostConnect specifies the usercode and password the firewall demands. You can include the domain if necessary in the usercode portion, such as "mafad\Administrator".
- If all works fine, you should be back a 200 result to the iHttpOpen command. If not and you get back a 403 - Forbidden or 407-NotAuthorized, you definitely have a firewall issue.
Thanks for all the help.
Article ID: W15095File Created: 2002:09:05:13:49:32Last Updated: 2002:09:05:13:49:32