Myke

It really depends on what game you are playing. The campus I lived on was a bit strict with this sort of thing, but was able to easliy play games online. Worst case scenario, you have to call your help desk to figure out if they allow it. What game(s) are you trying to play, specifically? I'd check into what ports they require and all. Also, check to make sure that your personal firewall is allowing the traffic outbound/inbound. A common oversight is the personal firewall. In addition, you might want to check the settings of any other software like ZoneAlert and the likes.

Thanks for your feedback. I took a look into the registry keys that you spoke of, but they match up just fine. Something I had not thought of, so I thank you for the insight. As far as the macro idea goes, that does happen to make some sense. We have a couple of customized macros that I wrote about 8 months ago which deal with a completely separate printer. These macros switch the printer, then prints the first page from a specific tray with other pages printing from of a different tray. Lastly, it switches the printer back to the default printer. The macro, although written earlier this year, was written in the latest version of MS Word that we use: 2002 (Office XP). All products have the latest service packs installed. The issue with this theory, in regards to our network, is that these macros are only used in Word, and the two main users who are experiencing this problem hardly ever even use the macros. Both are heavy users of Excel and this scenario only happens in Excel. When this happens, the user can print to the same printer in any other application or to another printer within Excel. After printing to another printer in Excel, the user can then print to the original (their default) printer. Sorry to sound like repeating record. I just wanted to clarify the situation.

I have a Windows 98 SE machine on my network which we cannot upgrade to XP at the moment, but that is outside of this issue. We recently changed domain controllers and have delegated it to be the primary server for our SAV system. All clients were successfully moved from under the old server to under the new server (in other words, being managed by), with the exception of this one machine: the Windows 98 SE machine. It keeps saying that the machine is not connected to the network, despite the fact that (1) it is, and (2) you can still view the log files from the SSC (Symantec System Center) Console. I know that in order to get full functionality out of SAV, TCP port 2967 must be open, as well as File and Print sharing to be allowed. Unfortunately, I cannot remember for the life of me how to open up a TCP port on a Windows 98 SE machine for an indefinite time period. Technically, I could just uninstall and then reinstall, but we're having some issues with networking protocols since the domain controller migration and only certain machines can see or be seen on the network. Also, I just don't want to uninstall to begin with; it's annoying. Any tips would be great. Thanks in advance.

I think that I may have found a work-around for this. Apparently, there is an option in the Symantec System Center console which allows the server to manage a legacy system. Installing this option requires a reboot, so we'll see if that works, although I'm still curious as to how to open up a port in Windows 98.

The answer to your next question is no. A wireless adapter is usually much slower than fast ethernet. Typically, wireless adapters can only transfer at a max of 11 MB per second, where as fast ethernet has the ability to transfer up to 100 MB per second. If you are in need of maximum performance, then I'd suggest dealing with the cables. If you hate cables lying around, you should look into purchasing Gecko Tape (it's amazing for tying up cables and such). If you are looking for convenience of mobility or have the PC located quite a distance from the router/modem, then go for a wireless connection.

I ended up creating a simple batch file which states: NET STOP "Print Spooler" NET START "Print Spooler" I placed it on the client's start menu for easy access. This is our quick fix until we research this more. I will provide updates if we find anything. This problem is now growing slowly to others (now our head exec. is experiencing the same issue). We have narrowed it down to only HP printers which clients are connected via IP rather than a print server. Bi-directional communication has been disabled, but that doesn't seem to help too much. We would like to refrain from using a print server for each individual printer.

I can't fully remember if 2000 does this or not, but I believe that it does. From 2002, this is how it is done, so you might want to see if this will work for you. In Outlook, click Tools, then Rules Wizard. From there, you should be able to do all sorts of things, like forwarding the message to anther person when received from another person or containing words in the subject or body, etc. Hopefully this will lead you in the right direction. Sorry I couldn't be exact when dealig with 2000.

Another thing to keep in mind is that sometimes when you receive this pop up, it doesn't necessarily mean that you have been infected by the virus. It may just mean that your AV system has noticed the virus and caught it before it could infect your system. As per Sampson, you should definitely run a few scans to see if you have caught it or not. A good indication if you have really caught it is to run the scan twice (don't surf in between). Run the first scan, then reboot, then run it again. If it shows up again, then you definitely haven't gotten rid of it. Running it in Safe Mode also helps. There are tools which you can download and run (usually from Symantec) which can fully remove these viruses from your PC (registry entries and all), but these are particular to the virus and some viruses do not have an easy removal tool.

There is. If you select the text you want to make caps, then hit CTRL + SHIFT + A. All of the text will be converted to CAPS. If you do that again, it will revert everything back to its original state. This only works in Word. Other applications use this shortcut for the Save As... function.

I'm still experiencing this issue with the printer. As Sampson has noted, this is a memory issue, which I have narrowed down to being associated with the Print Spooler service. Does anyone happen to know how to setup a simple icon that could restart the service for the user if this happens? While I'd prefer to fully resolve the issue, this would be a quick-fix that the user can do instead of waiting for me to restart the service for them. I'd rather they not mess with services.msc; who knows what they could accidently do. Thanks. It should also be noted that I have disabled bidirectional communication for the printer to eliminate that possibility, yet this still happens.

We've been getting this error on our network for a good while, now. I've also spent a great deal of time researching the cause and possible solutions to the problem, but to no avail. This error is happening on our Exchange server and with the following error message in the System log of the Event Viewer: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10006 Date: *date* Time: *every 8 hours* User: *domain\user* Computer: *server name* Description: DCOM got error "General access denied error " from the computer *server name*.*domain name* when attempting to activate the server: {D99E6E74-FC88-11D0-B498-00A0C90312F3} For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.'>http://go.microsoft.com/fwlink/events.asp. If I go to the user's desktop and look in their Event Viewer, I get the exact same error message in the System log at the exact same time the error occurrs on the server. In addition, I also get the following error message in the Application log at the same time: Event Type: Error Event Source: AutoEnrollment Event Category: None Event ID: 13 Date: *date* Time: *every 8 hours* User: *domain\user* Computer: *computer name* Description: Automatic certificate enrollment for *domain\user* failed to enroll for one Basic EFS certicicate (0x80070005). Access is denied. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. When I follow the links as instructed, they bring up information regarding Windows Server 2003. We do not use 2003. All of our servers use Windows 2000 SP 4 and each client uses Windows XP SP 2. All forums that I have read only show how to resolve the issues with 2003, not our systems. I have even tried to force the group policy updates on each client that has this error using gpupdate /force in the command prompt, but this doesn't help. These error messages are recurring every 8 hours for each user and I really would like to see them stop. In addition to this, it doesn't seem to do with the computer they are using. One of the users who were experiencing this error received a new computer and still continued to receive these errors, so I know it's user-based and not PC-based. Does anyone have any clues or hints that they could point me towards solving this issue? I thank you in advance.

PROBLEM SOLVED!!! Well, after spending a good while searching for a solution, I finally resolved this error. Thanks to peterh for pointing me in the right direction. After reading his explanation of the cause, I began looking into the personal certificates of the users on their local machine and found that they were missing a certificate issued to that user from the certificate authority (CA). All other systems had this certificate issued to the user using the PC. I tried to request a new certificate, but it said the CA would not let me. Moving to the CA server, I found that the Certificate service was set to manual and not automatic, and also was not started. However, I was unable to start the service because it claimed that this was not a Windows component (yeah, I wasn't thrilled about this). Some more research yielded the following article: http://support.microsoft.com/kb/842210/en-us It is titled "Certificate Services may not start on a computer that is running Windows Server 2003 or Windows 2000." Essentially, I had to download and install the Windows Server 2003 Administration Tools Kit onto a Windows XP machine, then copy 4 of those files onto a floppy and copy those files onto the local drive of the CA server. After words, there was a whole lot of comparing of certificates, dumping/renewing the hash, etc. In the end, starting the service back up fixed the entire problem. The DCOM errors that plagued our event viewer for the last few months have finally stopped. If anyone else has or is experiencing this problem and would like some tips or hints on how I resolved it, feel free to ask and I'll do my best. This was an extremely annoying thing to deal with and every forum I went to offered no solution. I'm more than willing to help out.

This may seem kind of a silly question, but I think it needs to be asked: did you unplug the old mouse from the computer with the machine still turned on, and then plug in the new mouse? If so, I'd try rebooting. If that doesn't work, then you might have shot your PS/2 port. If it is just your new mouse that does not work, but other mice do work, then your new mouse is dead and you should just get a new one.

I've been working with this situation and it is now happening to other machines as well. As Sampson said before, it is definitely a memory issue with the PC that is experiencing the problem, not the printer. I have found that if you stop, then restart the Printer Spooler service on the affected machine, the problem is resolved, although none of the previous jobs will print (they are not in the queue, as if they already were printed). While this does initially fix the problem, I am quite certain that this is not the last I have seen of this annoying scenario. Does anyone happen to know of a way to prevent this from happening in the future? I'd like to completely rid my network of this little pain. Thanks in advance, and thanks to Sampson for the input/insight he has provided; it is greatly appreciated.

Hey A.Kannan, Unfortunately, I think that the display you are speaking of is the default way of viewing mapped drives. I also don't think that there is an easy way to display the drives the way in which you wish. My guess is that you are just going to have to live with the fact that you will be unable to make that change. Sorry, man. Myke

Regardless of how "secure" Microsoft and others claim that the Preview Pane feature is, I do not trust it. If it weren't for my anal retentive habit of checking for antivirus updates about 3 times a day, my network would be severely compromised. This is partly due to the other employees' refusal to keep the Preview Pane disabled. Here is what I would like to accomplish, but have not found out how to do. I would like to completely disable Preview Pane from all machines on my network, so much that I want to probibit all uses from the ability to even turn it back on again. I've looked through a few articles, but couldn't really find a good answer. Each version just turns it off until the user turns it back on, which is stupid. Any help with this would be appreciated. Thanks in advance.

I do understand that disabling preview can allow for users to open e-mails they do not know the contents of, but our small agency has been thoroughly instructed to not do so (yes, we enforce it pretty well). The problem with preview pane is that if it is turned on in the deleted items box, it's opened when they try to delete it. And from my experience (despite what any documentation claims), the preview pane does, in fact, execute embedded code. We need to prevent users from enabling the preview pane. Anyone else have a solution which will do this?

I have a question regarding the Open File Option (OFO) on Backup Exec 10 for Windows Servers. BE 10 is running on a Windows 2000 SP4 server and backs up about 9 Windows servers and 1 Novell server (all of them have the appropriate Remote Agents installed). Through trial and error, I have had to tweak some of the settings to work around numerous errors that cause the backup jobs to fail or freeze. Here is the newest of them: "0xe00feba = An unknown error occurred within the NDMP subsystem" The doumentation that I was directed to and have read states that this error is usually due to an attempt to backup a file that is open and in use, which makes the file corrupt. It also states that the most common files that generate this sort of error are PST files. Users' Outlook Archive files are stored on the Novell server to save space on our Exchange server and are in constant use, so I'm 99% sure that this is what caused the error. The documentation also states that by turning on the OFO, the backup job will properly backup the file and keep the job from ending in a failed state (consiquently, it also backs up the file in use). So here is my question: I have read in additional documentation that there might be a compatability issue with OFO and the use of NAS emulation. Does anyone happen to know if this is the case with what I have described? Any help with this issue would be greatly appreciated. Thanks in advance.

The client is using an older computer, so I could see how that might have something to do with it. Where I get confused by this is that it has no problem printing Excel files to any other printer and can print any other type of file to the 2600n printer without any probelm. When this situation occurs, if we print an Excel file to another printer and then try to print to the 2600n, it goes through as it's expected to. It is almost like the printer needs to be shown how to print an Excel file before it can try to do it itself. Another note about this is that it is a brand new color printer, so it's internal print server has about 64MB of RAM installed. This is to help it print large, colored documents. So I can't really see how the printer would be having memory problems with printing such a small Excel file. I do thank you for the tip, Sampson; your help is very much appreciated. I'll look into it, but I'd like to refrain from using an additional print server in her office. Myke

Another thing to take a look at in order to see if it really is your internal NIC is to ping the loopback address (127.0.0.1) in the command prompt. If you don't receive any replies, then your NIC is fried and it needs to be replaced. If you do get replies, then it is something else. Try connecting the laptop to the router with a patch cable and see if you can even connect to the Internet that way. While all of this seems tedious, it will help diagnose your problem.

So I have a PC on the network that is attempting to send out data through port 8200. I have no idea what it is and nstat does not show that the port is open or listening to anything. A quick search on google showed that "trivnet1" is associated with this, but no one seems to know what this is. Anyone have any helpful information regarding this?

Just checking in on the situation, as I see a decent amount of people have read this thread. Does anyone have any news about this scenario? I'm still experiencing the same thing on the client and I really need it to stop. Any help would be greatly appreciated. Thanks in advance.

Like most of us out there, I've grown quite tired of the Windows splash screen on startup. I was wondering if anyone knows how to do change it in Windows XP. I know how to do it on 9x machines, but they've changed the logo file and I'm kind of stuck. Anyone have any clues to this one? Thanks in advance.

I have been trying to backup our ISA server for some time now, but to no avail. Using Backup Exec 10.0, I continuously receive an error message claiming that the program could not find the ISA machine on the network. When looking in My Network Places, you cannot see the ISA server, and you cannot ping it either. Does anyone happen to know how I can get the ISA server to be backed up? It is crucial that it is including in our backups, but I have not found any solution to this. Any help would be greatly appreciated. Thanks in advance.

Alright, I've now been able to start backing up the ISA server. For anyone else experiencing the same problem, I had to open up a certain range of ports in order to actually allow the backup service to connect and read from the ISA. However, I still am not able to see the ISA server on the network via any means, aside from viewing the ISA on the selections window in BackupExec 10.0. Because of this, I believe that the ISA's C:\ drive is not fully backing up. In fact, when comparing the numbers backed up by BE 10 and the numbers from the actual ISA files (the properties window when all of the main files are selected under the C:\ drive), the backup is missing what appears to be 1.5 GB! Here's my question, now: What the hell is going on? It looks like every other backup job on the ISA is going through smoothly, but not the C:\ drive. Does anyone have any clue as to how I can either (1) find out which files are not being backed up without having to manually verify all 3.7 GB, or (2) find a way to be able to see and connect to the ISA from another computer on the network? Any help regarding this issue would be greatly appreciated. Thank you in advance. Myke