|
No userNew | |
|---|---|---|
| Item No | Site Type | Description | Domain (click will register but not will not resolve) |
Help |
|---|---|---|---|---|
| 1 | Coffee Shop w/internet | Internet Cafe Site | dnr.cs.internetcafe.client.loc | |
| 2 | IP Site | Code To Generate IPSite Folders | dnr.cs.ipsite.client.loc | |
Note you may need the Ad Table pairs for the domain in your ads/users/'domain' directory for correct ad insertion. You may also need to upgrade your site licence to multi client operation.
To create your own custom "ClientSite" codes go to tools under "code gen Client client site" or click. codeGenClientSite
Client site codes work, when a router or browser sends a DNS query to the WiAd server, the WiAd servers parses from the code the client site information (encoded as Base64) and generates a folder if none exists. In that folder the server administrator inserts table pairs unique to ads that should be delivered to the client site. The codes in the table above are reserved for the internal operation of the WiAdServer and Demo Client site's. You can create your own clientsite codes under this web sites tools link.
IPSite codes work simply by creating a folder under ....tables\ads\users\'ipaddress' where IP address is the actual IP address of the intended WiAd Enabled client. If you want the folder created for you, from a browser on the remote WiAd enabled network. click the ipsite link above. All WiAd servers that are under the remote sites DNS will automatically create the folder for you.
With the obvious limitations of dynamically assigned IP addresses it is strongly recommended to use the client site code rather than IP address. If you are configuring a client that uses static ip address then the IPSite system will eliminate the need for programming client site routers or update clients or browsers.
You can sub zone client sites under static ip addresses. Where the entire network will get IpSite resolves unless an individual browser is programmed with a client site code. Where all browsers programmed with client site coding will only get those resolved ads and un programmed client PC's or browsers will get IPSite ads.
The system resolves ads by precedence of site coding
By this ordering WiAdServer will always use the generic ad table pairs last if it does not find ClientSite or IPSite coding. Or if you will, it will override any normal pairs(3) with IPSite(2) then ClientSite(1).
To check if the remote network your are currently on is properly registered as a client site type http://myclientsite.rbp into a WiAd enabled network browser. This is a simple way to test a remote clients configuration if providing support.