Search results for query: *

Well, I have stopped trying to fix the cause of this and just created a batch file to run every 10 minutes that shares this printer. I've spent way too much time trying to figure this out. Oh well...

arrrrgh! I'm at my wits end with this problem. I completely deleted any trace of this printer, from the printers folder and from Active directory, deleted it's printer port and then restarted the print server. I then waited about 20 minutes before doing anything. I then recreated the printed...

Another little tidbit on my issue, I am using a program called PrintUsage Pro that monitors my print jobs and keeps logs and reports. I stopped this service and then deleted the duplicate printer objects listed under the print server itself using the ADUC tool. I then restarted the prinusage...

Hmmm, that is interesting because we have noticed for a little while now that we are seeing duplicate printers listed in the AD. Our printer server is not a DC but I think you may be on to something. I'll see what I can find within our AD structure. Thanks!

Hello, just wondering if you had any success with the audits. I had deleted this printer and it's port and recreated it with now success, still does it. What's strange is not all clients are unable to print. Only some clients report that they cannot print when this happens. Thanks!

Hello, I was just actually still banging my head against the wall on this one. I'm at the point of creating a script to share this printer and have it run every half hour. Tonight I am going to try deleting the port and recreating the printer from scratch. Extremely frustrating! I'll keep you...

I know for me, I just installed the Cisco software for the first time today on this computer and had problems right from the beginning. I don't know what it is, but their VPN software has never worked without some kind of problem for me.

Nothing that I can see, just the entries for the actual print jobs themselves which are successful.

I have never NOT had an issue with the Cisco vpn software. I've either got the BSOD at random intervals or now my computer will just lock up tight after being connected for a few minutes. Maybe I'll try to get version 5 somehow....

Hello, this is driving me nuts. I have a Windows 2003 sp2 server that is a print server. It has about 40 some printers shared with no issues. Recently, I deleted a printer and recreated it and since then, about 5 times a day, it will be unshared. I re-share it and it's fine for a while...

Someone shoot me. We just changed our wireless access points to assign ip addressses thinking this would correct the problem since it did on a test machine. On our test machine, we cannot get it to fail in this configuration. If we turn off DHCP on the access point, we can make it fail, and...

ARRRRRgh! We are still banging our heads against the wall on this. We bought on off the shelf Toshiba, and it just works with no issues. We did however manage to make it not work by messing with the Network discovery options. We turn it on, it breaks, we turn it off, it works. We try this...

Yeah, I have read those over and they do not seem to apply to this situation as we are using Windows 2003 Sever as our DHCP and we've checked the power save options.

Our plan is to do just that, compare to two, but we don't have a non-working system on a regular basis.

Ok, now I'm even more confused. We bought two copies of Vista Home, basic and Premium. We installed them on two different computers, both work perfectly fine! So, any new computer that has Vista pre-installed on it, seems to have this issue. And I mean all of them. I guess our next step is...

Hmmm, I'll check that, but this has not been an issue on any other version of Windows. But at this point, I'm willing to try anything!

I'll check on that on the Dell machines but this has been happening on HP's, Dell's, Sony's, Toshibas, you name it. I did end up setting up another access point (Apple Airport Extreme) and had it assigning IP addresses, and that works, but it still will not work using the Windows 2003 server...

Ok, have some more information. After doing some testing, we can get connected if we enter in the gateway address AND a DNS server address. This of course is a useless fix since this would affect their access to other wireless networks.

Hmmm, that's interesting, but we seem to have this issue even on wired connections as well. I do plan on enabling DHCP on a wireless access point the next time to test that though.

This issue continues to drive us insane, so we've broken down and bought a copy of Vista home to see what the deal is. Then I may end up calling Microsoft....