windows 2003 server disappears

[klimber]

we have a windows 2003 server that is set up simply as a File server on a peer to peer network

set up as follows

8 windows 2000 pro machines and 1 windows 2003 server all connected to the same HUB, with it uplinked to the DSL router

all DHCP

most of the day there are no problems, files and folders are shared off of the server, but every so ofter (lately twice a day) the workstations mappings don't see the server and ther server can no longer see the internet or the workstations, but the workstations can still see the internet

event viewer shows that the server is reassigned an IP address that isn't even it the DSL routers range

disabling and re-inabling the network connection usually fixes the problem

Help, anyone please!

 

[lmoe]

Try repairing your IP Stack.

http://members.shaw.ca/techcd/WinsockXPFix.exe

LMC
IT/MIS
"Never stop learning.

 

[Zelandakh]

WINS server configured and running?

 

[ShackDaddy]

1. Is it a wireless hub? Maybe you're pulling an IP from a different network. Probably not an issue. Is the weird address that your server ends up with starting with "169"? If so, that means your server isn't properly renewing its address and the problem is probably with your router's DHCP engine.

2. If the DSL router is flaky, why not use your server for DHCP and use a static IP?

3. Even if the router DHCP isn't flaky, still set your server on a static IP within the larger subnet range but outside of the range being offered by the router DHCP.

ShackDaddy

 

[fs483]

Change the patch cable. Plug into a different port on the switch.

 

[klimber]

ShackDaddy

1. no, it isn't a wireless hub. yes the new IP does start with 169

3. I have now set it with a static IP but am confused about what you meen by setting within the larger subnet range but outside of the range being offered by the router DHCP. currently 255.255.255.0 do you mean setting it yo 255.255.0.0?


2. If the DSL router is flaky, why not use your server for DHCP and use a static IP? i'd need some guidance on this



ShackDaddy

 

[tfg13]

klimber and ShackDaddy,

If you can, just leave the server with a static. On the DHCP issue, I have run into some problems with having DHCP on the server dishing out IP's to clients on those darn routers. For some reason, even after disabling DHCP on the router, the clients can't get addresses, so I would be careful with going that route. If you got it working now with one static, I'd leave it as is (don't forget to set up a exception rule on the router's DHCP table). By the way klimber, what type of router are you using?

 

[klimber]

action tec router

thnaks everyone for your help by the way!

 

[tfg13]

Sorry klimber, I haven't had the chance to work on one of those, so I can't say whether you might run into problems.

 

[ShackDaddy]

Klimber, don't change your subnet mask. I'm just saying that your router probably doesn't offer all 254 addresses in its DHCP scope. There are probably a bunch out side of it's range. Maybe it offers from .10 to .100 or something. I'm just saying pick an address that's not in that range. Just make your server .2 or .254 or something like that. Once you give that server a static address, you probably won't have any more problems.

What I meant about using the server for DHCP is turn off the DHCP server on your router and install DHCP server on your server, through Add/Remove Programs -> Install New Components -> DHCP Server. If you don't feel comfortable setting that up, that's fine.

ShackDaddy