Network Help Needed

[countryboy60]

I just took down a client's "simple network" (pseudo network) and set them up with a real network running Windows 2003 Server Small Business. The client purchased the server with a ten (10) seat license and there are seven (7) workstations connected to the server. I have every one except ONE connected to the server and able to access both the network and the Internet. This one system sees the network and all the systems on it and even connects to the Internet. What it will NOT do is connect to the server even though it sees it. When I try to log in with the user name and p/w word, it kicks back, placing the workstation's name in front of the user name (i.e. The workstation's name is "wrkst2". I enter "userid" and the p/w and hit "ENTER". It kicks back with "wrkst2\userid" in the user id field and doesn't connect to the server.) The down side is that the client has ALL WinXP Home SP2 and WinVista Home systems for the workstations. Would flushing the DNS and release/renew the IP help any?

Any help is greatly appreciated... I've fried my brain trying to make sure I have all bases covered given the messed up environment.

Kevin

 

[burtsbees]

I can't remember how to do this exactly, something like joining the domain properly should fix it. Make sure the ws in question has joined the domain just like the others have.

Burt

 

[gb0mb]

If the machine is not part of the domain it tries to authenticate against the local host.

To fix this:

Username: Domain\user
password: password



Gb0mb

........99.9% User Error........

 

[countryboy60]

<b>gb0mb</b>,

Thank you for the info but, the situation has been resolved. Just to let you know, the machine is a member of the domain and all permissions properly assigned. Any other user on the network could go to that machine and log in without difficulty; it was just that one specific user.

If you want to know the solution...

It appears this individual had experienced the exact same issue at every other company he had worked for. There is something about his specific name that creates issues within WinServer 2003. The work around was to simply create him a completely different user account; one in which no part of his name was used for the userID.

To verify this issue with WinServer 2003, I spoke with two (2) Microsoft techs, two (2) MCSE techs and several computer experts. Apparently, there is an issue with certain names/letter patterns which create the issue. The second Microsoft tech even asked me for the exact spelling of the individual's name as he suspected that was where the problem lay.

Anyway... the situation is resolved and everyone is happy. Thank you everyone who provided some assistance.

Kevin

 

[gb0mb]

I would be interested in more detail of the name that causes this issue if you can share some info on it. Wierd issue though. I would have still been scratching my head.

Gb0mb

........99.9% User Error........

 

[burtsbees]

The name is probably close to "Share" or something, or has a $ in the name...lol

Burt

 

[gb0mb]

lol, that would cause some issues.

Gb0mb

........99.9% User Error........

 

[AndrewTait]

Just out of interest, how did you get the home editions of XP and Vista to join a domain, or are you just signing in as a domain user, but on a standalone workstaion.

It is "meant" to be impossible to join a home system to a domain, in order to protect Microsofts revenue stream.

=======================================
I got to the edge of sanity....then i fell off
======================================

 

[countryboy60]

AndrewTait,

You have a legitimate question. Without hacking the OS, it is impossible to get the Home editions to join a Domain specifically. While the logging in as a Domain user is one workaround, there is actually antoher... believe it or not.

Once you have set-up and configured the server and have established the Domain, create a user-/work- group within the Domain. In so doing, the systems act as though they are a part of the Domain. You still have to contend with the local stand-alones but you now have the benefit of user logs registering which users have accessed specific files on the server.

It's a bit tedious and not for the faint but it is possible. Personally, I would have preferred it if the company's owner wouldn't have been so cheap and bought systems with Professional or Business editions on them. It would've made my job A LOT easier.

Kevin

 

[AndrewTait]

countryboy60,

Thanks for that, it makes interesting reading, as I have come across this problem and have always upgraded to professional/business versions. It is worth knowing as a work around.

In so doing, the systems act as though they are a part of the Domain.

So in effect they are stand alone machines authenticating against a domain user/group, and as such will not be subjected to Computer GPO's as they would if they were part of the domain.


=======================================
I got to the edge of sanity....then i fell off
======================================

 

[countryboy60]

AndrewTait,

Correct in your observation that they are not subject to the GPO's. There are trade offs and to be completely honest, I would much prefer to have the Professional and Business editions as opposed to this set-up. As far as Window$ is concerned, it makes life a whole lot easier.

Kevin

 

[Walter349]

Come the time to start exercising any sort of control over these workstations. The owner is going to have fun, at the moment anyone can shove a USB stick/Drive in, and rob the server blind, including any company data.

'If at first you don't succeed, then your hammer is below specifications'