I need somebody to help me configure one of our work computers so that it can be on the network. We run a parts and invoice database so I need help ASAP. I have AIM and MSN so we can talk there.

topnotch

 

sure, billing starts at 65/Hr (SRIC low-price)

 

Ah dude, I'm serious. Any FREE help is appreciated. I don't need somebody to do it for me. Just to clue me in on how to configure it to recognize the network.

 

what's the command???
>c = overwrite

(i know that's right but it's something like that)

 

Ok, I'm not that experienced with networking. I just know how to get into the settings and change stuff.

 

Since you want the free kind of advice, here it goes. If I was making a small business network I would get get the following.

A Linksys Broadband Router with 4 ethernet ports, and enough ethernet cables to connect your PC's to the Broadband Router. With default set to DHCP, the PC's in theory should be able to speak on the same network. As far sharing files, that is a whole different can of worms, XP has a home networking wizard you could try but I avoid it and just set them up to see a common workgroup name.

If you already have a network and your PC's don't automatically "work" on the internet and stuff, there isn't going to be a lot we can help you with over forum messages and chat. If it is for a business, they should shell out a couple hundred bucks and get it all set up right.

Soggy is more expensive than I am, but I hear he always leaves customers with the happy ending.

 

I think I got it. The computer was on the network it just didn't want to recognize the server. So somebody told me I have to open the command prompt and ping the server. Anybody got an idea on how I do that?

*EDIT* We already have the whole network setup. The problem is that we got new computers and I was testing one out to see how it is. Everything is working dandy except for the database and invoice program. So now I need the computer to recognize the server.

 

Duplicate the settings on the PC that works with the server on the new ones. If they have "Manually assigned IP Addresses" increase the number by one on each new machine.

If you need any more advice Oaf will help!

 

command prompt
ping xxx.xxx.xxx.xxx(enter your server ip address)

that should do it.

 

Do what illy said.

 

IP Addresses are obtained automatically and each IP address is the same except for the last 3 digits: ie. 100,101,102,103,104

100 is the server and 104 is the computer im working with. I've tried pinging both the server name and server IP address and still nothing. Here is the error I get when I try to load the program:

System.Exception: Errors occured while trying to log on to SQL Server! ---> System.Exception: Please check the network connection and make sure that the SQL Server is running. ---> System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.
at System.Data.SqlClient.ConnectionPool.GetConnection (Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.Get PooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at DaPartsPro.DaMain.TestConnection()
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at DaPartsPro.DaMain.TestConnection()
at PartsPro.mdlMain.Main() in C:\AAA\PartsPro\PartsPro\mdlMain.vb:line 21

 

If you can't ping the SQL server then it looks like your network connection is bad. But it looks like your system is being assigned an IP address (most likely via DHCP). which requires a working network. You can run the command (windows) ipconfig to see your address and other settings. Possibly you gateway IP or mask is set wrong.

You might try pinging another system and pinging the SQL server from another system.

The problem may be with the SQL server in that it is not authorize to connect with your system. Don't know how to change SQL if that is your problem.

Sorry, can't help out much more.

 

Ok go into Control Panel -> Adminstrative Tools -> ODBC

Most likely you are using a system DSN to connect to the database on the working computer. Duplicate that information, page by page on the new machines.

Go get em' snotch! (that is your new nickname btw)

 

Oye, I duplicated everything and still no go.

 

When I ping the server IP address it says that four packets sent, four packets received, zero lost. No errors in the command prompt.