Recent content by paleogryph

Ok, here is more detail: We have a mixed Novell/NT/AD network. The Novell client (4.9) allows access to some shares, the H: drive (the one having the problem) is in the NT domain. The new AD domain wasn't really being used until we converted from GroupWise to Exchange 2003, which is in AD...

W2K Pro with a mapped drive. Occasionally when a user tries to save a file to that drive they get: "An error occured while reconnecting H: to \\server\share Microsoft Windows Network: the local device name is already in use. This connection has not been restored." Apparently MS tells people...

I was wondering if there is a forum in tek-tips that is devoted to Symantec Ghost. Does anyone know of a good forum to post questions about Ghost? I'm having problems getting a PXE enabled client to accept boot image .sys files from the Ghost Server. >Think for yourself< ...or someone else...

jrbarnett, thats a great idea! Yea, I found that typo in an ad for a network admin position. Considering how much falsification of diplomas goes on in the world, I wouldn't be surprised if there are people out there who've already done it. Heres another for MCCE: "Microsoft Certfied Crisco...

Heres another good one: "Microsoft and Crisco certifications weigh strongly in the candidates favor." >Think for yourself< ...or someone else will do it for you.

We run uvscan on Redhat 7.2. This is the "virus scan for Linux v4.14.0" from McAfee. The .DAT files are updated automatically every morning. Has worked fine for the last few years until this last Saturday, when qmail started having major problems. Tracked it down to something with the .DATs...

We run uvscan on Redhat 7.2. This is the "virus scan for Linux v4.14.0" from McAfee. The .DAT files are updated automatically every morning. Has worked fine for the last few years until this last Saturday, when qmail started having major problems. Tracked it down to something with the .DATs...

Well, the issue is documented on Ciscos site. The fix was akin to uninstalling the client (version 4.0.1 running on XP Pro), rebooting, click "ok" on the network properties, then reinstall the client. It worked. The initial problem was not being able to connect at all. Once this "fix" was...

This is more of a rhetorical comment than a question: I've noticed that with several network related issues in XP, whether it's a vpn connection, wireless or good old pci nic, sometimes they won't work, or work correctly until I click "OK" on the Local Area Connection properties and reboot...

Marv, thanks for the tip. Unfortunately, all our printers are non-NDPS, setup that way from the beginning. I didn't build the servers or network. I also see that NDPS.NLM isn't loading either. Whats the advantage of doing printing that way? I figured out that unless I configure the Linksys...

Yea, and at $8/hour, thats gonna be a long 5-7 years! >Think for yourself< ...or someone else will do it for you.

NW 5, SP 6, had a printer/print server/printer queue that worked fine: HP 2500 CP (plotter), Linksys EPSX3 V2 and a queue called "hp_2500_q". Everything worked fine, until yesterday. When trying to print, it would just hang, ran pconsole, said the job was "ready", not "active" like it...

Ever tried Samba? >Think for yourself< ...or someone else will do it for you.

Ok, here is what worked: directory mask = 775 create mask = 775 force group = cad This sets it so that only those in the cad group can create/write in this share, and forces the files/dirs to be 775. I guess it helps to read the smb.conf man page... >Think for yourself< ...or someone else...

Oh, here is another great ad I saw on Monster: "LaunchpadIT, a nationwide information technology internship service, is THE career launcher for ambitious techies. LaunchpadIT combines serious comprehensive IT training, 1 year fulltime internship as a LAN/WAN engineer/analyst/administrator, and...