ICTCity

Yes the FQDN (Fully Qualified Domain Name) is submarinefastfood.com in this case. Regarding the IP class, it's hard to say... it only depends on HOW MUCH is "LARGE COMPANY".

When you move the primary domain, everything goes to the new server. For example in my case, we moved from 2k3 to 2k8 and we changed also the domain name. Anyway the domain is still the old one, this is not a big problem. What you can do is to set client's dns to point directly to the new server, regarding stored credentials depends on what you have to do. For example if you have a network drive which is mapped with stored credentials, you must remove and re-add with the new domain if you really need this. For example: OLD: MyUser@Old_Domain.local NEW: MyUser@New.Domain.Name In order to change that property, you can use a GP script which can looks like this: set LOGONSERVER=\\YourNewServer Or if you prefer, remove clients from domain and rejoin... I hope this can help you!

Well, I've never said you don't have to create a virtual machine. If you want you can install a virtual machine inside your server... Anyway join a domain means that you have at least 1 server and 1 client, the client (in your case is Win XP) must be configured to join your domain. let me know.

You can buy an ebook (pdf format), take a look here: http://www.amazon.com/s/ref=nb_sb_noss?url=node%3D1286228011&field-keywords=Windows+Server+2008&x=0&y=0

actually you don't have to configure the site. You have to create a domain called submarinefastfood.com, which could be "name_of_fantasy.local.me.you", it doesn't matter, this will be the DOMAIN NAME. I don't understand if you really want to install a VIRTUAL XP INSIDE your server, if so, you just have to use Virtual pc, VmWare Player, Virtual Box, which can virtualize a OS. Specific configuration is not needed, once you installed XP, you can simply add it to the domain. To do this, set up PROPERLY DNS settings (correct IP), and then change from WORKGROUP to the domain name. To replicate the DC, it's more than easy. Install new Windows Server, add the same role you added to the existing server and during the installation select DOMAIN CONTROLLER IN EXISTING FOREST. Let me know if you need more help.

I just found this on .net classes: http://msdn.microsoft.com/en-us/library/system.net.servicepointmanager.servercertificatevalidationcallback.aspx Can it be helpful?

I think you have a PM...

Just to be sure... run this command and post output: net user guest |find /i "Account active" Then user this tool http://live.sysinternals.com/AccessEnum.exe to verify permissions on shared folder. You can also use this tool to do almost the same thing: http://live.sysinternals.com/ShareEnum.exe Now let's try another thing: On group policy / local policy find "DENY ACCESS TO THIS COMPUTER FROM THE NETWORK" (I can't remember where is it, maybe it's under Computer Configuration, Windows Settings, Security Options) and check who's in that policy. Then in the same path, find this policy: Network access: Shares that can be accessed anonymously be sure you don't have your share here. Last to try: find this policy: Network access: Do not allow anonymous enumeration of SAM accounts and shares and set it to ENABLED. Let me know.

I mean change manufacturer. I had some faulty modules and I changed all in one time with Kingstone modules. Anyway, I don't think the problem is hardware related, because after this change I also update our accounting software, which had in release note "Memory Management Improvement". Cached memory is a feauture of Win 7 / 2k8. Programs are stored in RAM if there's space, this improve the speed of your system and your programs will open faster then before. It's like CPU - Caching (L1,L2,L3,...), essentially it's the same thing. Now the problem is that what happens when a program is started. I don't know if your problem happens only with SQL or with another "external" problem. What I know is that some stored procedures / queries which need RAM, can cause Windows going out of memory! That's because you can set things as you want with the link I've provided before. Unless you want to investigate on WHAT it's really consuming your RAM.

You're not the only one. The main problem is that almost nobody understand WHO is the guilty. 6 Months ago I've set up SQL with server 2008, 16 GB and after 3 months I've upgraded to R2. I had the same issue but the AWE was enabled. Anyway the situation was similar... I changed ram type and the problem went away!

I know it's quite unbelievable but this seems to be the hard truth. The problem should be HOW windows can allocate dynamic memory. It looks like windows can't free cached memory when not used. With the provided link you can manage this setting.

Mhhhh MAYBE your server has been compromised... Because on your server there's VNC which is listening. My next suggestion is to go here: http://HTTP://www.logmein.com/ and install it on your server. Once you're sure it works, remove remote desktop connection and vnc, change the password of logmein again. Now in settings you can setup that you receive an e-mail everytime someone try to connect. Let me know.

It's not only with Sql... But it's not windows itself. Anyway, before using the procedure go to SQL manager and be sure that under memory you don't have AWE checked. Let me know

When I did it, it worked fine. You can read both topics which may help you: http://social.technet.microsoft.com/Forums/en-US/winserverMigration/thread/dab33e51-25f4-476c-b173-7e65ee253373/ http://mobile.experts-exchange.com/Q_23582347.html simply add the role, promote to master and demote the old one :) Cheers

Hi there, Unlucky this is a know-issue with x64 systems. The problem seems to be SQL, I can just suggest you to download this: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e24ade0a-5efe-43c8-b9c3-5d0ecb2f39af&displaylang=en ***PLEASE BE SURE TO READ AND UNDERSTAND WHAT'S WRITTEN IN THE ATTACHED DOCUMENT (README.DOCX)*** let me know if you need further help.

Hi there. First of all let's try to determine if the problem is really the timeout or not. So, increase the timeout (let's say 120000 ms = 2 mins), after this modify you need to restart your server. When you say "every 7 or 8 days" you mean that this problem occurs on a specific day AND time? If so, you could check if there's any scheduled task (backup, defrag, ...) which runs at that day / time. Another thing you could do, is to enable PERFORMANCE MONITOR LOG. This utility (installed by default on windows), allows you to write values on a text file (csv I think...), and then analyze it. Enable this log (don't use an interval too short), and let it register until you have this issue again. By doing this, you simply have the chance to understand if your server goes out of memory / cpu / disk / ... when this happens. Let me know.

Ok let's try in a different way. Open "Local Security Settings" http://technet.microsoft.com/en-us/library/cc775651%28WS.10%29.aspx Right click on "IP Security Policies on Local pc" and select "Manage IP Filter lists". On the first tab, click ADD, type a name and again click add. Click next and enter a description, Next and as SOURCE address select "A specific IP". Type the IP you want to block and click next. Under "destination" you can let ANY IP ADDRESS and click next until finish (you can select the HTTP protocol in the last screen, but it's not mandatory, you can block that IP completely, it's up to you!). Let me know if this help you. Anyway, is that correct you have enabled RDP/vnc on internet? (port 3389 and 5800+5900 opened)

Ok, just to be sure this is not a problem regarding the dns resolution... Open this file (on your win 7 client): C:\Windows\System32\driver\etc\hosts (open with notepad). This file should contains only rows with explanations on how to edit that file, at the end you should see this line: 127.0.0.1 localhost After that line type: IP_ADDRESS_OF_YOUR_DNS DNS's NAME Save and retry.

I still need the netstat output, anyway for now I can tell you one other thing you can do: Open Windows Firewall (start > run > wf.msc) Create a new INBOUND rule > CUSTOM > All Programs > Under protocol and ports let everything as is and click next > in scope select these IP addresses on the second text box (REMOTE IP) > Block the connection and then you're finish. Now under MONITORING > Firewall you should be able to see the blocking rule. Let me know.

I need more informations: 1) what is runing on your server? Which programs can be contacted from the internet? 2) can you post the output of "netstat -an |find /i "listening" "? 3) When you say that "blocking port 80 has no effect" I think it's because the connection COMES from port 80. You just have windows firewall or others systems to protect your server?

If windows allows you to sign-in without credentials, there are only two choices: 1) anonymous enabled 2) stored credentials. What does "net user guest /active:no" return from the server?

It could be! What I suggest you is to DOWNLOAD the latest version of the needed driver and then reinstall it completly. Remove the driver makes no sense... Maybe just a reinstall (with an updated driver) can fix this issue.

Check your DNS's settings (client side), it sounds like Windows can't contact the DNS to resolve the name... Let me know

In some way I think the guest account is still enabled. If you have made the modification to the registry and you don't have problems you can delete the exported registry.

Hi there You can do a sniff with wireshark to understand which port Are involved . the strange thing is that in your config file you point at localhost which means you should have another exe which opens a connection. Can't you see anything from ISA log?