Problem Connecting Server

**Bhardwaj** · 21-03-2009

I am facing a strange problem with my wireless network card. I have a asus notebook and a belkin wireless network attacahed on it. The problem is yesterday i ran Registry Fix programme. Some repairs were required on systems.

I turned the notebook on and tried to connect to internet and it said 'unable to connect to Server'.

**Milton.J** · 21-03-2009

To correct this problem, you should attempt to restore the metabase from a backup. If this does not correct the problem, however, you may need to restore the metabase from a system backup.

The metabase, Metabase.bin, is located in the (default) C:\WINNT\System32\inetsrv (%WinDir%\System32\inetsrv) directory.

**Spyrus** · 21-03-2009

What is the FTP server software?

Is it GlobalSCAPE Secure FTP Server? (Version?)

Or are you perchance connecting with a z/OS FTP server?

Have you tried any other FTP client software?

**Snake08** · 21-03-2009

You get this error when the server ip address or the port number is wrong.

If both of them correct and you are getting the error. Then the server services may not be running.

Start the service if your server is installed in windows

Start->All programs->SerivceCenter 6.1->Server->Console

It will open a window click the start button that will start the services.

Then try to connect the client.

**Zachary** · 21-03-2009

that error msg Invalid Instance() makes me think your providor is using a named instance, just ask them if they are, then reference your server as "servername\instancename" (check the slash direction, can't remember off hand if it's forward or backward). Another issue could be the port number, try either "servername,1433" or "servername\instancename,1433" as your server address. this is often a problem if your using load balanced sql server. also there's somestuff about the server knowing which port to reply on (for
sql2005), but this is a bit more complex and sometimes requires some server side config in awkward situations, anyways if it's 2k5 your connecting to read up about sqlbrowser replying to the client on port 1434 instead of 1433.