Ian's questions

I used to set my WiFi security using WEP to support legacy WiFi dongles that can't handle WPA (or other new encryption scheme).

Recently, I've dumped those old dongles and got new ones. I am now moving to WPA2.

While setting up WPA2, there is a setting called "Group Key Renewal" that has a default value of 3600 seconds.

Question: Does this mean that all wireless connection to the router will be dropped every 3600 seconds to renew their key?

Thanks!

I am running Windows XP 32bit. I have a total of 3GB memory installed and I also increased the Virtual memory to 4GB (Properties --> Advanced --> Performance Settings --> Advanced --> Virtual Memory --> Change)

I've read here that the total available virtual memory is approximately the sum of installed RAM and the size of the pagefile(s).

However, launching "System Information", XP reported that the "Total Virtual Memory" is only 2.00 GB? Why is that?

When I checked on my Windows 7 machine, the "Total Virtual Memory" is the RAM + Pagefiles.

Thanks, Ian

In our company, I want to check if users are running web servers on port 80 and 8080.

I downloaded nmap and ran this command:

nmap -p 80,8080 192.168.1.0-255

I got a list of IPs and tried to access them in my browser (EG: 192.168.1.1:8080) but wasn't able to connect.

Is my nmap command correct?

Thanks!

EDIT:

Here's the response:

Host is up (0.050s latency).
PORT     STATE SERVICE
80/tcp   open  http
8080/tcp open  http-proxy

We have a product that uses Web Services. On our primary testing here on our local site, the product seems to be functioning well. When the product was deployed on another site, it went crazy with the infamous ISA HTTP 407 error.

So I have a couple of questions regarding ISA:

1. How do you know if a network is ISA enabled?
2. Can a Windows Machine be affected by the ISA server even if it is not joined to a domain?
3. Since the web service is on the SAME MACHINE as the product, is there a way to tell the machine to not process the HTTP traffic through the ISA Server?

Thanks!

Here's our scenario.

We have two machines, Machine A is a Windows Server 2003 SP2 machine that is setup as the Domain Controller. Machine B is a Windows XP SP3 machine that is to be joined to the Domain Controller that is Machine A. Both machines have a single LAN card.

Both computers are connected to our corporate LAN. Since our corporate LAN has DHCP enabled, both computers were automatically assigned their dynamic IPs and DNS servers (Both lan cards were set to "Obtain an IP address automatically" and "Obtain DNS server address automatically")

Machine B was joined to the domain (ian.sd.local -- Machine A). The machine was successfully joined to the domain (validated by a welcome message) after asking for a domain admin account. It then asked for a reboot.

After reboot, we logged in to the domain using a domain admin account. It went in normally. We then created a new folder then shared it to check if we can retrieve the accounts from the domain controller, we can't. From the Sharing tab -> Permissions -> Add -> Select Users or Groups dialog box, clicking on the Locations button, the DC won't show up.

Another thing, pinging the domain controller from the client machine using FQDN will fail. While pinging it using the machine name only will succeed.

I somehow know what the problem is. Since the client machine is set to automatically obtain the DNS server address, our corporate LAN gave us our own "corporate DNS server" (used by our corporate domain controller), thus resulting on the client machine not being able to "resolve" the FQDN. However, I am still not sure why the "domain controller" cannot be found on the "Select Users or Groups" dialog box.

Anyway, hardcoding the domain controller's IP address as the client's Preferred Primary DNS server fixes the problem.

My question is, is there an "official" Microsoft document that tells the user to set the domain controller's IP address as the client's Preferred Primary DNS server? I am asking because a tester on our company used the above setup to install one of our software and it is failing because of this. I need to prove to him that this is a configuration issue and not an issue with the software.

Thanks!

For some reason, the IT department at our company does not want to add Windows 7 and Windows Vista machine to the domain controller.

I hate to always provide my network credentials everytime I access a shared folder on a machine that is joined to the domain. I also hate to always provide my password when I launch outlook or Visual Studio (Team Explorer).

Is there a way to mimic the behavior of a machine that is added to a domain without actually adding the machine in the domain?

For shares, I can create a batch file that will NET USE the different fileservers we use here but that is a huge security risk as I will type my password as plaintext.

Thanks!