Standalone server connection problem

[dachaney]

We have a small remote office where we have a standalone Windows 2003 server in its own workgroup. We also have a number of Windows 2000 Pro laptops which are part of our corporate domain. There is no access to any domain controllers in this office.

The problem is the laptop users cannot connect to the server to use the shared printers or folders, an error occurs - no logon server available.

Any Ideas?

Thanks

 

[technome]

Not a great deal of time, but search google for SMB signing, turn off SMB signing at the server for a starter.



........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[itsp1965]

How are these users mapping drives? If the server is not on the domain, then they will need authenticate to this server using a local user account as follows;

net use x: \\yourserver\share /user:<localuseracct>

Hope this helps.

 

[WhoKilledKenny]

The problem is the laptop users cannot connect to the server to use the shared printers or folders, an error occurs - no logon server available.

This error occurs because as you have stated there is no access to the domain controllers. I would assume the users are getting this when they logon to the laptop, not when attempting to connect to the stand alone servers.

itsp1965 is correct. Since the server is in a workgroup, you would have to create local accounts on the server to allow them to connect.

So you might consider a re-design as AD would be the way to go as it centralizes user management.

Since it is a remote office, is there a WAN connection between your corporate office and the remote office? if yes, what type of bandwidth?

 

[juniper911]

Or log on locally on the laptops and then map a drive to the stand alone server using a local account on that server as mentioned by previous peeps.

by logging on locally on the laptop there is no need to look for a DC and no need to change your AD structure.

 

[WhoKilledKenny]

Or log on locally on the laptops and then map a drive to the stand alone server using a local account on that server as mentioned by previous peeps.

by logging on locally on the laptop there is no need to look for a DC and no need to change your AD structure.

We as IT guys no we can do this and it works, and we agree that this is the only solution if there is no access to AD. From a user standpoint, this solution has always been a nightmare.
1. Client needs to be trained on how to log on locally. As stupid as it sounds, they still don't no how to use the domain dropdown box.
2. Client needs to remember Three usernames and Three passwords (one for their Domain Logon, one for their local Logon, and the third for the local logon to the stand alone server). I don't know how many calls your help desk gets, but clients seem to have issue remembering one logon. And if you have apps that don't do Single Sign On... How many more passwords do the users have to remember.

Again I prefence this with "if no AD is available." Still I blieve setting up remote offices as part of an Active Directory is the best way to go...

So how is your bandwidth looking dachaney?