ICTCity

DHCP activation is just to tell you if you received the address from DHCP or not. Now my question is: Can you plug another client on the same port /location? And the strange thing is the default GW... Where does it come from???

The only thing is a limitation in the router... Try to connect another pc (notebook or other) which wasn't in your network before and try if this work. Maybe the router has blacklisted / blocked the mac address or other...

You are welcome :)

So, first issue this command: route add 0.0.0.0 mask 0.0.0.0 192.168.0.1 This will set the default route (default gw). Now, once you can have the following situation from IPCONFIG: ip: 192.168.0.120 mask: 255.255.255.0 gw: 192.168.0.1 (in reality this is not needed until you are on the same network). Try to ping the following: ping 192.168.0.120 ping 192.168.0.1 ping IP_Another_Client_On_Your_Network (for example the NAS) If all are ok, try to ping 8.8.8.8 If not, please try the following: Plug your server directly to one of your switches (just for a test), and try the DHCP. Let me know.

Hi, The only thing I can tell you is to disable the card from device manager, but actually I don't know what can happen. I *think* after a restart, the secondary VGA should show up the image... but I'm not sure... I think if your VGA is on the first PCI slot, and you restart the system with monitor plugged in into the new card, it should work...

Wait, I think you don't have the proper routing in place... from the server, type the following and post results: route print Unless you have a switch (programmable) from your server and your router, or another device that knows where is your router, I think you can't reach the router, it is on another network. So first of all type this command: route add 0.0.0.0 mask 0.0.0.0 IP_ROUTER (which is 168....) Let me know.

Hi there, I never understood if you can migrate from 2000 to 2008 directly, but actually, I would not do that... So, your idea seems to be the best way, first migrate to 2003 and then to 2008. There are well documented procedures provided by MS: How to migrate from 2000 to 2003: http://support.microsoft.com/kb/325379 Migrate to 2008: http://technet.microsoft.com/en-us/library/cc731188(WS.10).aspx Be sure to understand everything before upgrading. I just have a question for you: why do you have a 2000 domain? This is really important, because if you need to mantain backward compatibility, forget 2008! What's your domain's name style? something like my_domain or my.domain? If you have the "underscore", you may have trouble migrating the domain. You can install VMs to test this scenario. When you set up AD (domain) on the test scenario, make sure to select NEW DOMAIN and not NEW FOREST ON EXISTING DOMAIN or other. If you have any other question... just ask.

Remember you can disable firewall for local network (LAN) and enable just for public network. But this is another story. Anyway, try this command on the server and post the output: netstat -anb |find /i "listening" Just to know, here you can find a guide on how to configure windows firewall for SQL analysis service: http://msdn.microsoft.com/en-us/library/ms174937.aspx To manage your firewall you can use the netsh command. To display the current state of your firewall (also ports), type the following: netsh firewall show state firewall seems to be deprecated... (the hell?!) on a command line type the following: netsh advfirewall now just type HELP and at the end you can find the "commands in this context" section. Let me know.

So actually, you can restart that pc, ping it, but not RDP... Have you tried the TELNET command on port 3389? Do you have a black screen? If you do a port scan on that host, are there any open ports?

The DNS is a secondary problem. Once you successfully ran the command "netsh interface ipv4 set address name="" source=static address= mask= gateway=" and you don't have any error message, what happens if you type IPCONFIG /ALL ? And if you try to ping your router (via IP)? And if you try to ping 8.8.8.8?

Open a command prompt and try the following: (copyrights by microsoft technet) To set a static IP address At a command prompt, type the following: netsh interface ipv4 show interfaces Make a note of the number shown in the Idx column of the output for your network adapter. If your computer has more than one network adapter, make a note of the number corresponding to the network adapter for which you wish to set a static IP address. At the command prompt, type: netsh interface ipv4 set address name="" source=static address= mask= gateway= Where: ID is the number from step 2 above. StaticIP is the static IP address that you are setting. SubnetMask is the subnet mask for the IP address. DefaultGateway is the default gateway. At the command prompt, type: netsh interface ipv4 add dnsserver name="" address=index=1 Where: ID is the number from step 2 above. DNSIP is the IP address of your DNS server.

Have you already tried to RESTART that pc???

if you CANNOT set the static IP, and your don't have any error when you click "OK", so try to reinstall windows... but this is really really strange.

I assume your IP is 169.254.x.y which is an APIPA address (when DHCP is not available). if you set the ip address manually (for example 192.168.1.10) does it work?

have you already tried to change the port on the switch / router? Just to be sure there's not a problem with that port... When you set up a static IP, is it applied correctly? If you type ipconfig /all does it show the correct IP? Can you ping another client on the same network (without pass the router)?

can you restart that remote pc? Try to connect to another pc via RDP and type: shutdown /r /f /m \\IP_PC /t 1 Let me know.

The suggestion provided by ASH was to test the RDP in this way: telnet IP_PC 3389 if you have a blank screen with no errors, RDP is working fine. Otherwise, restart that pc :)

If there's a share on that pc (also the c$ is ok), try the following: (from the RUN window) \\IP_PC_NOT_WORKING\SHARE_NAME if it works, restart that pc (remote pc), maybe the protocol (RDP) is stucked somewhere.

The only thing I can tell you is to update drivers, this sounds like an incompatibility.

Netstat is the tool used to show the LOCAL CONNECTIONS (active, timed out, listening, ...). I can install a web server on my PC, the port 80 will be in a "LISTENING" state and I should be able to reach my web server by typing http://localhost/ (http is by default on port 80). If this work and you run netstat, you should see localhost and your IP (private IP) listening on port 80. If you have a firewall, it should block every port unless you specify others settings. In this case, the port 80 CANNOT be contacted from the outside (outside your PC), but LOCALLY it must work! In netstat output you can't understand if a port is blocked by firewall or not. So, first of all answer to the following questions: 1) From the server running the service "Analysis for SQL", can you test if the application is working properly? I mean, can you connect to that service? 2) When you say "remotely", you say "from the internet" or from the other pc on another lan? In others words, do you have a firewall on that server which is windows firewall, but are there others firewall active? (usually network firewall)? 3) if you disable (temporarly) your firewall, does the application work?

Well, first try to ping that PC, if it doesn't respond, there's a firewall blocking the echo from ping or the pc is down. Try to connect to another working PC, once logged in, try to ping the pc that is not working. Just to know, you can add the telnet to your Win 7 / vista, it is under "turn windows features on or off" in control panel.

Hi, Usually when the VSS fails, the problem are the DLLs. Try the following: http://blogs.technet.com/b/sdoakes/archive/2006/02/03/418722.aspx

OK, Microsoft gave me a solution: http://support.microsoft.com/kb/981466/en-us let me know

Hi, I think your problem is not the firewall or AV but the program itself. If a port is blocked by the firewall, it can still be able to "listen" but not to initiate a connection. That means if you start (for example) a web server, it listen on port 80 regardless of what you've specified on your firewall. In other words, this port appears in netstat. Then, if the firewall is not configured to pass connections on that port, your server will not respond to requests. Check your program first, then the firewall.

So, there's a problem with that REMOTE pc. If you can connect remotely to others PCs from your pc, and just one of them doesn't work, the problem is that remote pc. Not your ;)