Thread: 3/4 of the day later...

XenApp Fundamentals is not compatible with the 64bit version of Windows 2008 Server. It sure would have been nice for that to be on PAGE 1 of the installation guide instead of PAGE 11!



Okay, let's start again... calling Chloe, I will be home late tonight.

[quote name='Gypsy' date='09 January 2010 - 04:47 PM' timestamp='1263084420' post='95829']

Does it matter that you spent 100% of your day here? lol

[/quote]

This is what keeps me from banging my head against the desk when my servers are misbehavin'!!

The arrogance of Microsoft is one of the great mysteries of the IT world.



After I got my A+ and Network+, I started my MCSA cert program. But the raging illogic and stupidity of Microsoft just snuffed out my enthusiasm for pursuing M$ certs.



Here's one example..



For the uninitiated:



WINS stands for Windows Internet Naming Service (Microsoft).....



So do you know what it has to do with the Internet?

[quote name='kmiller1610' date='09 January 2010 - 04:59 PM' timestamp='1263085141' post='95857']

The arrogance of Microsoft is one of the great mysteries of the IT world.



After I got my A+ and Network+, I started my MCSA cert program. But the raging illogic and stupidity of Microsoft just snuffed out my enthusiasm for pursuing M$ certs.



Here's one example..



For the uninitiated:



WINS stands for Windows Internet Naming Service (Microsoft).....



So do you know what it has to do with the Internet?

[/quote]

/raises hand



I know! I know!



It's a trick question, because DNS supports name resolution on the Internet. WINS just supports resolution of netbios names. It's antiquated now, as a correctly configured and populated active directory uses DNS. WINS will rarely be used as a backup name resolution solution.

It's pretty strange, Bla. If it works once, then it should simply work. When you have two workstations on a LAN they find each other by broadcast. You might check your windows firewall on each PC and see what the settings are. Also, make sure they are in the same workgroup. You could create hosts and lmhosts files. They are text files in this format:



192.168.0.1 (computer1 name) <- use your real IP address and computer names of course

192.168.0.2 (computer2 name)

192.168.0.3 (computer3 name)



The first file is named hosts (with no . or three letter extension at the end)

The second file is named lmhosts (with no . or three letter extension at the end) and both are located:



c:\windows\system32\drivers\etc



After you create these, run two commands. nbtstat /R <- purge and reload your netbios name file. ipconfig /flushDNS <- does the same thing for DNS cache.



That may help. If not, then I will tease you mercilessly.