Thursday, June 23, 2011

Missing DVD device drive when installing Server 2008 x64 or Windows 7 x64

I have had major problems when trying to install Server 2008 x64 or Windows 7 x64 whene it tells you that a DVD driver is missing.

Many options online to try to resolve this issue has been found, but none of them works.
Some are related to the raid configuration, some related to bad download of the OS and so on... but the real probelm is from Microsoft itself.

Exactly what it is, might be unknown, but the problem only occurs when you try to install a 64 bit version of Server 2008 R2 without SP 1 or Windows 7 without SP1.

All other versions are fine, so if you have Server 2008 SP2 or R2 with SP1 (which you can download now from Microsoft), go ahead and enjoy a problem free (or one less error) installation.

Sunday, May 1, 2011

Passing ByVal acts like ByRef?

Did u know....
That regardless if you specify ByVal in the method that you are passing in a parameter, if the parameter is an object reference, it will still be passed in as a ByRef.

Duhhh... does many say, but if you are coding a lot, this might leave your brain to malfunction when trying to debug...

Yes, you should always look at the parameters being passed from the caller and not just look at the called method.

Just see this as a pointer :)

Tuesday, January 25, 2011

A non-SYN packet was dropped because it was sent by a source that does not have an established connection with the Forefront TMG computer.

If you notice that you are not receiving emails to your server, but can ping your mail server from the TMG server, you should be looking into the Logs & Reports. Edit the filter and set it to Protocol Equals SMTP.

In my case, I got a lot of "A non-SYN packet was dropped because it was sent by a source that does not have an established connection with the Forefront TMG computer."

Researching the web, I could not come close to what the problem was. The only place that I could get a hint was when I was looking at the Monitoring section where I found, by looking at the date and time, a "Server Publishing Failure".

It indicated that one of my firewall rules that I had created did not publish and it was my mail smtp server rule which I had duplicates of but to two different servers since I have two mail servers on my network.

Deactivating the extras, and applying the settings solved the problem.

Update 1:
I have learned that you recieve this error as a generic error when there is no communication between the firewall and the destination. If you are trying to make a servers service or protocal accessible to the outside, you need to publish a non-webserver protocol with the correct properties, not just open a port.

If TMG detects a protocal, and you have not defined a rule for it, it will apply its own system rule.