I've checked the load command many times. I've even loaded the above with inetcfg utilities and does the same. By design you can only bind IPX to the primary card.
Bind ipx to xxx .. I I suppose to have the net=... at the end. It's loading the wrong net.
Thanks for your help
Most likely not. (havent' tryied it but I understand the implication and mechanics). You need IIS4 and a server.
If not an option, setup a shared folder on your workstation for user to connect to and publish your web on your local workstaion.
Hold on cowboy...
this might be your problem.
Only events that are commune to ASP and DHML are supported.
the onafteropen is not.
use advise() before opening the recordset
Deon,
I've had similar problems for the past two weeks. I've managed to install SP4 on Visual Studio and everything went away. Now I am able to post databases fine SQL and Access. My suggestion is look on your event viewer. It should give you some error (even the information once don't rule...
In your outlook profile, properties, advance tab, make sure it is set to NT Password Authentication. If it is set to none you will get what you just discribe.
You cannot. Older program such as you describe required full access in order for you to even view the data. This is of course because of the file permition limitation. With the new generation of NTFS, everything changed.
I am sure you could find a readme file on that directory for a phone...
Not true. I assume he's on NTWorkstation logged onto a domain.
From his workstation, log into your domain. From User manager make him part of the local admin group. I can understand the confusion but he will not have admin right to your network other then whatever you give him. This is just...
Greg,
Don't know about IIS3.0. I am sure you could find IIS4 (much better product). But it's very simple. If IIS is on the same as the exchange you could use NT challenge response and anonymouse access. If they are not on the same server, you need to use Basic Authentication (clear text)...
Hi again,
Looks like you will need a replication connector installed. Exchange will not do that for you but should not be hard to configure one.
As I explained earlier, I am sure there are people that will disagree with me but I will not put my exchange on a PDC. I found more bad things...
And don't forget to enable IP routing also if you want to route between subnets.
Funny think, win2k wants you to hack the registry to enable the iprouting.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.