captainjack913

gunsmokingman, honestly, that's not what I'm talking about. I do not have any clients that map printers. Everything is done on the server side since the vast majority of my users use Terminal Services with only one application allocated to them. Any and all printing uses printers mapped locally on each terminal server. I need a way or at least the info I need to construct a script to change the IP address of printer ports ie change the IP address of a port named IP_10.X.X.1 from 10.X.X.1 to 10.X.X.2. The Windows 2000 Scripting Guide was a great resource and I have yet to find the equivalent for Windows 2003.

I need resources on how to create VB scripts for Windows Server 2003. Specifically I need information on how to manage print servers. Technet has examples on how to create TCP/IP printer ports but I need to know how to change the IP address associated with that port.

If i'm guessing right, that looks like it's talking about the trackpoint driver on the thinkpad. I'll see of lenovo has an updated driver. Thanks Culberti

This should be the dump file from the latest crash Mini092807_01.txt

this is taken from the event logs: Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 9/24/2007 Time: 7:06:04 PM User: N/A Computer: Description: Error code 0000010d, parameter1 00000004, parameter2 f812fc80, parameter3 00000000, parameter4 82164f18. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 31 30 0000010 0020: 64 20 20 50 61 72 61 6d d Param 0028: 65 74 65 72 73 20 30 30 eters 00 0030: 30 30 30 30 30 34 2c 20 000004, 0038: 66 38 31 32 66 63 38 30 f812fc80 0040: 2c 20 30 30 30 30 30 30 , 000000 0048: 30 30 2c 20 38 32 31 36 00, 8216 0050: 34 66 31 38 4f18 Does that help at all?

Has anyone ever had a case like this: I have an XP Pro laptop with Remote Desktop enabled. I can log onto the console in the morning, check my IMs, lock it and go to work. I can remote into the machine from work with no problems. When I get home and unlock the console, the machine blue screens. this is about the only time it does this. Any thoughts?

No problem. Just be sure that port 5900 is open on any and all firewalls that need to be traversed.

I have offices all over the US and I use VNC, RealVNC specifically as much as possible. Their site lists a few versions but I use the free version. Only problem I've run into is service mode doesn't work on Vista, at least not yet.