ICTCity

Reinstall windows on that pc, there's something broken with RDP.

Hi kerberos, What certifications are you planning to do? Anyway, WELCOME :)

You will learn more than you can expect right now :) Cheers

You can use VmWare workstation. Anyway, if you have a physical server / machine available, consider XenServer from citrix. There's a free version which can run up to 5 VMs.

I think in your question there's the answer. The problem could be something not properly managed which corrupt memory. You could try a different virtual software (VMware or virtual PC), just to try if you have the same issue.

I think the problem was a bad installation... I think there's no problem installing SQL with those services...

You must modify the policy on the server you are connecting to. The two policies I wrote before, simply don't force to use strong encryption.

You don't need to take the exam :) just buy the study guide and READ it, is ok: http://www.amazon.com/CompTIA-Network-Study-Guide-N10-004/dp/0470427477/ref=sr_1_2?ie=UTF8&qid=1308666730&sr=8-2 Anyway, I can help you, but you should google a bit more. The problem is when you say: "On server A, I wanted to have WSUS so that I can see if the Updates work for all Operating systems across the board, or if it would just update my Server 2008. (I have Server 2008, XP and Win7)" Actually WSUS does exactly this: it permits a single location to manage updates for many different OS. Now, I could tell you: "To set up WSUS, read this guide:" http://www.microsoft.com/downloads/en/details.aspx?familyid=df628245-8449-4b93-948c-0926deb1197a&displaylang=en Which is ok, but actually, WHAT you can learn from that? I think almost nothing, because of when you read on the document: "now, on the client side, set up this policy to point to the WSUS server". You should know where is the policy editor and what you have to do to apply those policies. The same for the domain. A domain is created to centralize computers on the same network. On a fresh install, every pc is on "WORKGROUP" which is the opposite of DOMAIN. My suggestion is: first of all, try to find articles which explain how to achieve your objective. You can google for example: wsus step by step Once you've read one time that guide, you can ask what you don't understand. But, if you don't know what is a POLICY, google it, you surely find an answer to your question. I can understand your situation, but trust me, the best thing to do is self-study. You are on a test environment, USE IT! I think you can learn in 10 minutes how to set a up and join in a windows domain, but if you don't know WHY are you doing this, what you can do next? Last thing: RRAS, if you don't know how to set up a static IP address, and actually how a TCP/IP network works, it's almost impossible to set up a RRAS server. Don't be despondent, I WANT help you, but try to follow my tips. Remember: first thing -> understand

From what I know, on 64-bits you can't use DAO, you must use ADO. If you prefer, install office x86 (32 bits) and it should work.

Hi, Honestly, without basics concepts, I can't see how you can accomplish your project. What I mean is that I can tell you how to do things, but if you aren't able to set a static IP on a server, I can't see how you can set up a domain, IIS and wsus. I know schools are expensive, but you need a base to start from. You may think about a certification like Comptia A+, which explains the basics of computers. It's not expensive, you can buy the study guide for 50$ or less. Now, tell me why you have chosen those roles. Do you know what is used for the RRAS role or the WSUS or WDS? Honestly to learn how a server works, you should learn what is a ROLE, a FEATURE and what is a domain. If you set up a file server with shared folder, you must understand the difference between the shared folder permissions and domain users under security tab. These are a bit complex topics, and they can take days to be understood. Maybe you should read a book that is a bit more easy: http://www.amazon.com/Windows-Server-2008-Dummies-Tittel/dp/0470180439/ref=sr_1_3?ie=UTF8&qid=1308664419&sr=8-3 Anyway, most of these books assume that you know basic concepts like how a network works. I can help you, but I can't explain everything from the basic.

Wait, do you want the AERO theme on your server? You must install the DESKTOP EXPERIENCE feature. Here you can find the tutorial: http://www.videotutorialzone.com/operating-systems/windows-server-2008/windows-server-2008-enabling-the-vista-aero-theme-and-programs.html

So, modify the local policy (gpedit.msc)

So rey this first: smb://username:password@ip/share If it doesn't work set this on your DC: (Policy) Computer>windows>security>(then navigate because I can't remember where is that policy...) And disable: Microsoft network server, digital sign communications (always) And enable: Microsoft network server, digital sign communications (if client agrees) Let me know

What about using connect to server and use the following strings? smb://ip:139/sharename cifs://ip:139/sharename Let me know

Hi, If you installed server on a separate partition, it's like another computer, so it doesn't depend on XP. Now, the only thing that can make your server looking like the old 2003, could be a compatibility issue. Maybe you need to update the GPU drivers or something like that. Regarding wireless card, you must find at least VISTA drivers. Let me know.

Sorry, can you upload the LOG FILE, (File > save as > PCAP file). With that screenshot I can see only the initial part.

Ok, that's starting to be annoying for me. I MUST know the hell what's happening on that network! Install wireshark http://www.wireshark.org/download.html on your server. Set the IP-address mode to DHCP, save settings and DISABLE each interface on your server. Now start wireshark on the right interface (start capturing), and than enable the interface. You should see some packets captured by the program. Wait until windows tells you that you are not connected and then stop capturing. Now save the result and upload here (the extension is the same, I prefer the native extension of wireshark). Thanks

Of course :) keep trying and practice

So the DHCP should be used only for clients, not for servers. I suggest you to use names when a client must contact a server. The advantage is the modulation. If you server must be re configured and you can't put the same static IP, you simply can change the A record in DNS (A record points a name to an IP address), which can be pointed to another IP. Then another advantage. Let's say your server is a DHCP, file server and print server. You can put 3 A records on DNS, for example: Storage, Printers. When your clients try to contact "storage.my.domain" (just an example), they will reach your server (IP). Now, the only drawback using names is the DNS itself. If the DNS fails, your clients will use their local cache (where are stored the successfully completed conversion from name to IP), but this cache expires (for example when a client is rebooted). If there's not in cache, your client will contact the DNS,but if it is death, your client will not be able to resolve the name. To resolve this issue, usually you set up two DNS servers, if one fails, the other will be able to resolve names. You can use only IPs, in this case you HAVE TO use static ip. Because of in case the DHCP will not give the same IP or it fails, you can not reach that server. Usually the DHCP assigns the same ip to the same machine, but this is not guaranteed.

Really... No idea... Sorry. I still think the problem may be the router...

For mail server you need Microsoft exchange, which is another program / license. For web server install IIS. Fileserver and other servers should use static IP because DHCP may assign another IP to your server and your server must to re register on DNS server. If your clients try to reach that server via IP it will not work, if they use the name, they may experience problem because DNS is not yet up to date.

It depends on what you want to achieve. Enable routing on win SRV is easy, it's a role. There are many KB on TechNet. The same for network monitor. Anyway untangle is ready to run, download install, everything is via a GUI. No Linux skills required.

Hi, First of all forget about a network virus scanner on a windows system. You must choose between two scenarios, a windows system or a Linux system. Essentially windows can run as a router and you can add a sniffer (network monitor, wireshark,...) to log packets. If you install a Linux distribution you can do a bit more. You can use UnTangle to monitor your network, it has many free packets and also a virus scanner (but it should cost, not too much anyway). To make your scenario working, you have to route traffic from Nic 1 to Nic 2.

Yes, and what you can do right now is to check what happen if you plug the same pc directly to a switch instead of router. Maybe on your router there're some port "shutted down".

It looks like the 2382 port is not opened. Take a look here http://blogs.msdn.com/b/karang/archive/2009/09/05/sql-server-analysis-services-port-sql-2005-2008.aspx Are you sure the service is working fine? Do you use IP or service name to connect?