Pc america adding another terminal to sever

hi Lloyd,
need more info about your setup to help you. is this a stand alone station or connected to a server? your question wasn't clear about this.
[email protected]
Feel free to email me with more details if need be.

it's a rather lenghty explanation so please go to this site and follow the instructions...
http://portforward.com/english/routers/port_forwarding/Linksys/WRT54G/

Robert

Please rate this solution ... thanks

Hi

Not clear whether you installed SP1 on the client or the server.

Try resetting or powering off and on the L230 and let it reintroduce itself to the network.

Also restart the computer that had the SP1 installed on it.

If none of the above resolves the problem, enter Network settings on the client and ensure that Neywork Discovery and File Sharing are not turned off. If they are off, enter Network and Sharing Center and use the Drop Down arrows on the right to turn them and any other desired options on.

Hope this helps.

First make sure all stations are on the same version, then uninstall the enterprise server/client services from the appropriate machines. Next, direct connect the client to the server. pcAmerica no longer supports the "enterprise" sync (which is lame) but have switched over to sql replication in the newer versions (which costs $$$). so the only way to do sync w/o redundancy is with direct connect. id also check out faq.pcamerica.com for some help

station stopped error in client pc

Your getting a connection successful because your looking at the localhost. The server would be the network name of your server. And the password is case sensitive and is pcAmer1ca. (Note the number 1, not an i)

easiest solution is to avoid their sync stuff all together, i've almost never gotten it to work correctly. what i generally do is set up the client station as a "stand-alone" and put the server address for the server name. that usually does the trick, only lick is that if the server goes down, your toast, the client goes down too.

W2000 Terminal Server used to corrupt the accounts of RDP users every now & again. Wouldn't surprise me if W2003 did the same thing :{ I used to create a copy of the user's account on the server (with an incrementing number on the end of the account name) & change the default account in TS management to that new one when this sort of problem occurred. I then made a copy of the new account & deleted the corrupt one.

Of course there are all sorts of other reasons this may happen but that may take a fair bit of hands-on investigation to sort.

For info on what's actually happening: Have you looked in the TS logs? Or the System and Application logs? Have you looked ta the logs in the client? Can you connect to the same TS server & account using a PC & the MS RDP client? If not, try the solution above :)

Are you remoting into your server from a differnet location than where the server is? I need to know th physical location of the printer to the server. If the printer is connected to the server there is a problem with the driver. if the printer is connected to your local PC you will need to click on the options button in remote access and tell it you want to use local resorceses. If the server / Printer / PC are in the same location do not access the server thru terminal services, set it up as a client server.

Well i'm just going to start where i would start. First off, how do your machines on the network get their IP? DHCP?

Is the first listed DNS server the AD server? 192.168.1.1?

Also make sure your using case sensitive domain information when your trying to connect. It is rare but i have had that be my trouble.

I have remote software available and would love to help you fix this hands on if possible. I live for network problems ;)