Jump to content

Recommended Posts

Posted

I have this problem on one laptop. Every other client works fine.

 

Teacher is unable to run reports or access documents stored in the document server. When I log on as SIMS Administrator, and look at the Document server settings, all the details are correct. However, click on 'Test server connection' and you get the reply 'Document server not working.'

 

I have checked all the obvious settings on the laptop, re-installed SIMS .net, checked firewall settings, etc etc. Our Sims support team have been unable to sort this out and are now talking about changing the port that the document server uses to 8081 (currently default 8080) but I don't want to mess up the rest of the clients or the server for the sake of one laptop.

 

I do agree that it's a connection problem and the help desk seem to think there may be something conflicting on port 8080.

 

Any way I can check this or are we barking up the wrong tree?

Posted
I have this problem on one laptop. Every other client works fine.

 

I do agree that it's a connection problem and the help desk seem to think there may be something conflicting on port 8080.

 

Any way I can check this or are we barking up the wrong tree?

 

It's connecting to 8080 on the document server so I can't see it being something clashing as then the others wouldn't work

 

Possibly that it's trying to go through an outside proxy and back to the local network. Try adding an entry in the internet options > connections> lan setting> advanced> tick bypass for local address and add IP of the document server.

Posted

Possibly that it's trying to go through an outside proxy and back to the local network. Try adding an entry in the internet options > connections> lan setting> advanced> tick bypass for local address and add IP of the document server.

 

These settings are already set through group policy. All local addresses are bypassed and type specifically into the box.

Posted
You might also try a connection monitor & packet sniffer to see what's going on. I used TCPView and Smartsniff last time I was having problems with the Document Server which helped push us in the right direction, albeit only a little.
Posted

 

These settings are already set through group policy. All local addresses are bypassed and type specifically into the box.

 

I'm still suspicious as if the others work fine it has to be something with that machine, which pretty much comes down to firewall or proxy if it can connect to other things and is authenticating on the domain.

 

Personally I'd turn off both the local machine firewall and set it not to use proxy as a test, if that doesn't work leave off while your fixing it, then add them back once you've got it connected and working.

 

Might be worth checking that your DNS/DHCP doesn't have multiple entries for that machine/IP.

Posted

Well, I've done some investigating over the past day or so and basically I've got nowhere. I ran a port checker and when I do a connection test to the document server in sims, the port checker shows that port 8080 has connected successfully :?

 

Made sure the local firewall is off disabled the proxy and I've run a complete virus check which has shown up nothing. I'm beginning to think I will need to get the restore CDs out of the cupboard.

  • 4 years later...
Posted

Hi Mark,

Any chance you remember how you solved this? Exactly the same problem has appeared out of the blue on my PC.

Thanks a lot,

Tim

Posted

i know that when we have had issues with document server (on a RM Network) it is down to the proxy address putting a ; after the address. I am not sure if this is the same thing but worth looking over.

 

Nick

Posted

Hi Nick,

 

I remember reading about that in the Summer release notes now you mention it. That may well have been the problem.

 

Have fixed it now by resetting my CC4 profile.

 

Tim

Posted
i know that when we have had issues with document server (on a RM Network) it is down to the proxy address putting a ; after the address. I am not sure if this is the same thing but worth looking over.

 

Nick

 

This happened with us. Removing the semi colon worked.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...