Adding computer to business network

[BarryG]

I'm adding a running XP SP3 to a network whose server is running Server 2003. The XP computer is connected to a router which is connected to the network. Knowing that the business software does not like DHCP I've set up the XP computer to use a static IP address on the router. As such it still connects to the internet and generally works fine.

However, it will not see the other computers on the network including the server. It does see that there is a network there but keeps telling me that I do not have permission.

On the server I have added the computer and the user to the list and given each appropriate permissions. From the XP machine I can right click the shortcut to the network, choose properties and advanced and successfully use the username and password to make changes.

So, the XP machine sees the network and can manipulate settings on the server but cannot see the other computers or the server. What's up??? Help!

Thanks, Barry

 

[VirtualLarry]

Is the firewall set correctly?

 

[imagoon]

Is this a Windows domain network?
If so:
Is DNS on the workstation pointed and the domain controllers?
Why is the router providing DHCP? The Domain controller should be doing this. (You mentioned you set it to static in the router)
If not:
Are you using NETBIOS to find the computer names? If so like Larry asked is the firewall set correctly. Is it enabled (default is on but both DHCP and network settings can turn it off)

 

[Emulex]

if you use active directory, dns is kinda part of it, and dhcp part of that, and lease reservations part of that.

That is how i roll. hp printers love dhcp and lease reservations keep your systems from moving around ip wise - dynamic dns then registers the machine to domain name and active directory is all happy. you have to use it all - or not. (simple-sake). you can make it more complex but there is no reason to.

 

[BarryG]

Is the firewall set correctly?

I don't know. What do I check? Which machine do I check it on?

Is this a Windows domain network?
If so:
Is DNS on the workstation pointed and the domain controllers?
Why is the router providing DHCP? The Domain controller should be doing this. (You mentioned you set it to static in the router)
If not:
Are you using NETBIOS to find the computer names? If so like Larry asked is the firewall set correctly. Is it enabled (default is on but both DHCP and network settings can turn it off)

I guess it's a Windows domain. Networking is nearly foreign to me.
A Linksys router was added to the system as an afterthought to provide a wireless internet connection for the country club's patrons. It was placed in between the switch and the XP computer. Until recently no one wanted or needed the club accounting software on this computer. Since they do now I've been asked to get it working. Obviously the software and the server don't like having something with public access connected. We tried to run a direct cat5 cable but it doesn't give me internet access for some reason. If I could use the direct cable I would be much happier.

if you use active directory, dns is kinda part of it, and dhcp part of that, and lease reservations part of that.

That is how i roll. hp printers love dhcp and lease reservations keep your systems from moving around ip wise - dynamic dns then registers the machine to domain name and active directory is all happy. you have to use it all - or not. (simple-sake). you can make it more complex but there is no reason to.

Boy, if you could tell me how to accomplish this . . .

Thanks, Barry

 

[Emulex]

well you need to answer is it a domain?

domain logins as mycompany.local are common or mycompany\myusername ?

most people would say not having two active directory servers is insane. i have 4

 

[BarryG]

It is a domain; blahdeblah.local. When I turn on the XP computer I log into that computer, not the network. When I turn on the XP computer and choose to log into the network as the same user it's actually a different user.

 

[Emulex]

so you have both active directory and not? usually you pick one.

you realize that if you don't have two servers in AD role ; you lose one. gone. poof. that login is toast. active directory is the achilles heal of windows server.

the domain admin login on the AD windows server should have tools (or enable roles) to do dns/dhcp/active directory - a properly installed active directory would have all of those roles enabled (AD->DNS->DHCP) to do all of the above. if you would like more explanation after you verify those roles are being used or not (VERIFY NOT CHANGE). AT folks will help.

biggest warning: no undo with AD. Restores are very dangerous. You never run anything else (maybe print/file share) off an AD server. Especially not exchange/sql (ask me how to P2V an AD server with Exchange/sql). or how to dcpromo demote an AD server with SQL running.

Do nothing until you have a microsoft supported plan with some support infrastructure if things go wrong. AD is the only thing that i fear from windows. There is a reason microsoft approes no method of P2V'ing an AD server.

 

[VinylxScratches]

Are the computers in the same subnet?

 

[BarryG]

The server does have an AD.
AFAIK the computers are on the same subnet.

 

[VinylxScratches]

Doing an IPConfig on all machines that work vs. don't work would help.

Can you ping anything on the network?

What happens when you try to do a \\ServerName from the machine that doesn't work vs. a machine that does.

Did you add the Computer to the Domain correctly? Just creating a Computer Object doesn't make it on the domain.

If you setup a static IP, did you set it in the right subnet?

 

[BarryG]

All questions I'll have to answer when I get back up to the country club tomorrow.

 

[VirtualLarry]

It was placed in between the switch and the XP computer.

That sounds like it would isolate the XP computer from the rest of the network. You should read up on "router as AP".

 

[BarryG]

That sounds like it would isolate the XP computer from the rest of the network. You should read up on "router as AP".

... and it does but supposedly you can tell the XP computer to use a static IP and things should be well. I could easily be wrong.

When I hook it all up directly, i.e. remove the router, I still don't get where I want.

 

[Emulex]

remember what i had said? AD should do dhcp and dns? not the router.

 

[BarryG]

Well, I don't believe it but it was simply Windows Firewall. When I turned it off (temporarily) I immediately had access to the server. We got the accounting software installed and restarted Windows firewall, adding exceptions for the programs.

Thanks to all for the quick responses!
Barry