Are you getting any errors, either in the browser UI, in the SharePoint
logs, or in Event Viewer?

searching from the site, i get the generic error: "No results matching your
search were found" - I've tried different keywords and still the same results.

I've checked the eventvwr and there are no errors in regards to being unable to
search the site, or unable to reach the site.. i get these error though from SQL
though, not sure if they are related to the problem:

Event ID: 318
Source: SQLSERVERAGENT
Description: Unable to read local eventlog (reason: The paramater is incorrect)

I even have this in the eventvwr, which i think means that the search  is
working, but just not to the NEW SITE..

Event ID: 10042
Source: Windows sharepoint  Services 3 Search
Description: A new query machine, "SERVERNAME", has been added to the query
rotation based on changes to farm topology. Component
bd69f3bd-ba35-4500-b8d9-9bb6013a5ec0

Nothing in the sharepoint logs, i think.. here's an example:

Timestamp Process TID Area
Category EventID Level Message Correlation
07/09/2010 12:00:17.27 wsstracing.exe (0x12EC) 0x35E0 ULS
Logging Unified Logging Service uls1 Monitorable
Tracing Service lost trace events. Current value 3.
07/09/2010 12:05:17.35 wsstracing.exe (0x12EC) 0x35E0 ULS
Logging Unified Logging Service uls1 Monitorable
Tracing Service lost trace events. Current value 1.
07/09/2010 12:13:17.45 wsstracing.exe (0x12EC) 0x35E0 ULS
Logging Unified Logging Service uls1 Monitorable
Tracing Service lost trace events. Current value 1.


ANY IDEAS?

When searching from the site, i get the generic error: "No results matching your
search were found" - I've tried different keywords and still the same results.

I've checked the eventvwr and there are no errors in regards to being unable to
search the site, or unable to reach the site.. i get these error though from SQL
though, not sure if they are related to the problem:

Event ID: 318
Source: SQLSERVERAGENT
Description: Unable to read local eventlog (reason: The paramater is incorrect)

I even have this in the eventvwr, which i think means that the search  is
working, but just not to the NEW SITE..

Event ID: 10042
Source: Windows sharepoint  Services 3 Search
Description: A new query machine, "SERVERNAME", has been added to the query
rotation based on changes to farm topology. Component
bd69f3bd-ba35-4500-b8d9-9bb6013a5ec0

Nothing in the sharepoint logs, i think.. here's an example:

Timestamp Process TID Area
Category EventID Level Message Correlation
07/09/2010 12:00:17.27 wsstracing.exe (0x12EC) 0x35E0 ULS
Logging Unified Logging Service uls1 Monitorable
Tracing Service lost trace events. Current value 3.
07/09/2010 12:05:17.35 wsstracing.exe (0x12EC) 0x35E0 ULS
Logging Unified Logging Service uls1 Monitorable
Tracing Service lost trace events. Current value 1.
07/09/2010 12:13:17.45 wsstracing.exe (0x12EC) 0x35E0 ULS
Logging Unified Logging Service uls1 Monitorable
Tracing Service lost trace events. Current value 1.


ANY IDEAS?

Are there any items in your index? What happens if you manually initiate a
full crawl? How many results, any errors, etc?

You need to provide us with more details about your old farm and new farm.

You have said it was complicated... What was complicated?
What resources did you use when you migrated from WSS 2 to WSS 3?

Ok, here it goes:

1. Before we had WSS 2.0. Client wanted to upgrade  to WSS 3.0 even if they're in
a SBS 2003 environment we managed to upgrade their Sharepoint site to 3.0
2. We made a backup of WSS 2.0, created a VM of Server 2003 standard, and
installed WSS 2.0, set same settings as the one in SBS.
3. Restored the backup copy of the site to the new server 2003 standard using
stsadm.
4. Installed WSS 3.0 side-by-side with 2.0 in the SBS 2003 server.
5. Did the in-place ugprade of 2.0 in the 2003 standard server to WSS 3.0.
6. Then made a backup of WSS3 in Server 2003.
7. Restored the backup of WSS3 from server 2003 to SBS.
8. Changed Alternate Access Mappings of WSS3 to use http://companyweb
9. Turned off WSS 2.0 in SBS2003.
10. All is working  even in RWW.

Then they wanted to upgrade their site so that it utilizes the BLOG template.
1. So we created a new WSS 3 site in SBS server, named: http://server:8888
2. Used Sharepoint Site Migration Manager by Metalogix to migrate all contents
from the http://companyweb site to http://server:8888
3. Once all contents, lists, etc. are migrated over we switched the Alternate
Access Mappings. so from http://server:8888 TO http://companyweb AND from
http://companyweb TO http://server:8888
4. Both sites are accessible, they use the old http://companyweb (now
http://server:8888) as a test site.

Is that clear enough?

So now, we noticed that the search  function is not working on the current
http://companyweb site BUT it is WORKING on the http://server:8888 site. Why is
that?

After a couple of weeks trying to solve this problem, i finally figured it out..
with the help of guys at Experts-Exchange

Here's how I fixed it:
http://support.microsoft.com/kb/896861
Method 2 (DisableLoopBack)

never would have guessed loopback check from those symptoms (at
least not without pondering it for several days). Thanks for letting us
know.

Any time you have a single server farm, you will need to disableLoopback