chilifrei64

try the nlite forum http://www.msfn.org/board/index.php?showforum=89

check under the key HKEY_CURRENT_USER\Software\InstallShield and see if there are any funny listings there

you actually want to to be 0x07. 0x42 means dynamic disk. http://www.microsoft.com/resources/documen...kd_tro_kyrr.asp I would change it back to 0x07 and boot to a boot cd and run chkdsk on the drive to check for errors or if it is still in the other system just run chkdsk from there. Make sure you reboot inbetween changes via hex-edit

This is untrue. All but one of my clients use NAT and a Corporate firewall and I access them from one to the other all the time. Even on non-corporate firewalls. I have always been able to make this type of connection possible. What is your source? The only place where it doesnt work is actually on one of my clients where I filter the RDP protocol with the use of a Proxy server. But this is also me explicitly denying these types of connections.

exact share names would be a good start .. also you typed //ip but it really should be \\ip

you can try these settings http://winguides.com/registry/display.php/913/ this won't "Get rid of them" it just removes the default folders that Windows puts in.

Open regedit and go to key HKEY_CLASSES_ROOT\Installer\Products\ and search for the Microsoft Office Key and delete it... Obviously make a backup of this key before you delete

either manually remove it after you create it or if you join it to a domain it will not prompt you for another user.

where is it located on the sever.. what directory is it in?

I guess just to clairify.. home path and profile path are different.. if you want to create a path automatically when the user logs in then what you are going to want to do is create a share on the server called home$ and profiles$ (I like to use hidden shares for user folders). Keep the NTFS permissions default and make the share premissions everyone full control. In the user settings dialog Under the home folder path enter in \\servername\home$\%username% and for profile you would enter in \\servername\profiles$\%username%. Doing it this way will automatically create the users folder when they first log in and will automatically connect it givin you selected the check box to connect to the drive letter for the home folder path

use the custom setup.. as opposed to clicking VPN click custom then click VPN

if you want to forward requests from the VPN to the LAN then yes you will need to have 2 nic's ... if you only have one server, in your case the DC which stores all your files then there is no need for a second nic. Only if you want requests on the VPN to be forwarded to other lan clients will this be necessary.. Honestly, nic's are so cheap right now.. adding 100 bucks to a budget shouldn't be too hard of a stretch and like i said.. i like having 2 nics on a DC anyways

you can however everyone that logs on to that computer will have to be a local admin if you use the C$ share... make a share called profiles and give the users full share rights on the share. put the mandatory profile inside this shares folder.. Do it this way.. much more secure Administrative shares should only be used for administrators but yeah.. that path should work.. to test the %variable% the easiest way to test would be to go to the command prompt and type for example echo %computername% and see what it returns.. it it returns the computer name then you know it should work..

unfortunately everthing for me was linux and I am not tuned in to that OS as I would like to be yet so I dont have any feed back on anything.. I downloaded a few but couldnt get some drivers to work and just ditched the project pretty much everything I tried was the Asterisk based but i was unsuccessful on all attempts:(

If your 2003 server is a domain controller that is running DNS for the domain then make sure your PRIMARY DNS Server is pointing to its OWN IP address

Here is the tool.. . just drag the MSI over this script and it will prompt you with 3 dialogs and just hit OK on all of them. This will remove OS checking from the MSI file I use 2003 as a desktop and this has worked for me a number of times. I like TweakNT... but once I used it to change 2003 to XP pro and my computer didnt reboot from it so I am skeptical about that function now.. I just use it for its other functions now removechk.rar

For log off removal start-> run -> gpedit.msc -> User Configuration -> Administrative Templates -> Start Menu and Taskbar -> "Remove Log off from start menu" Set this setting to enable For MRU http://windowsxp.mvps.org/mrublaster.htm and run it as a task to clear them at intervals.

i did some searching not too long ago about this same thing. None found.. all are Linux Based. I remember finding one windows based (cant remember the name off hand) but it was commercial software and it cost MUCH more than a linksys or D-link gateway. If you happen to find one please post. or if anyone else knows of any good ones please let us know.

For starters I WOULD NOT use my domain controller as the vpn server as it adds much too easy access to the "Brain" of my network What you are going to want to do is forward pptp from your watchguard to the internal IP address of the VPN Server (which should be static) Once this mapping takes place you would be all set as long as the VPN Server is configured correctly. Sometimes firewalls get picky and want you to enable a few other things.. i dont rememver if watchguard is one of them. But as for hardware requirements of your VPN Server.. this would depend on the number of concurrent connections you plan on having connected to the VPN.. essentially a relatively small machine can handle a large number of clients as long as you have a good network card and alot of ram.. most of the processing of network connections never really make it to the CPU. It only NEEDS one card however if you do decide to use the DC (which I do not recommend) then I would say get another card so you can have one card dedicated to VPN and another card dedicated to the LAN domain functions. I like my DC's to have 2 nic's in them anyways, especially in a single DC enviroment.. cause if your only one goes you have nothing to fall back on.

Not sure exactaly what you are asking but if you are trying to set user profile paths for multiple people then you would use for example \\servername\profiles$\%username% if you are trying to reference an already created path of a folder already contained in an already created profile path then you would use for example "%userprofile%\My Documents" Hope this is what you are looking for

2 things.. Tools ->Internet Options -> Advanced Tab -> Reset web settings Security tab -> Internet Zone -> Default.. if doing these dont get it working then it is something external or you do not have permissions

Group Policy-> User configuration -> Administrative templates -> Desktop -> Active Desktop -> Active Desktop Wallpaper put in the path This obviously works as a "Batch" bets when using AD and GPO to be able to apply it remotely

I have never done this with XP but just by making an advanced connection of my own and fishing through the settings, one check box makes sends Go to "Incoming connections properties" then the networking tab then select Internet Protocol (TCP/IP) and select properties and check the box that says allow callers to access my local area network

RDP should work on XP PRO as long as the following are set It is checked under system properties -> remote tab User accounts that are used to log on have passwords set If the machine you are trying to access is behind a firewall, port 3389 must be forwarded to the computer. Terminal Services services is running on the machine you are trying to access. If you are accessing it via DNS try accessing it via IP address Those are the only settings I have ever checked anybody else know of any others that are necessary to run Remote Desktop

The device acting as the VPN server has to have a route to the network address.. right now you only have a route to the directly connected machine only and not to the rest of the subnet