• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 491
  • Last Modified:

DHCP Assignment After Login

Hello Experts,

I've been struggling with this for a while now and can't figure this out. I have Windows XP users in VLAN6 that is not able to map network drives because DHCP assignment seems to occur after the user logs in thus not being able to contact the DC and run the login scripts.

My Windows 2003 DHCP Servers are located in VLAN1 with the IP Addresses 192.168.1.80 and 192.168.1.81. My users in VLAN6 has the router config below:

interface FastEthernet0/0.6
 encapsulation dot1Q 6
 ip address 192.168.6.1 255.255.255.0
 ip helper-address 192.168.1.80
 ip helper-address 192.168.1.81
 ip virtual-reassembly

Only users in VLAN6 is having this problem. Can anyone help?
0
katredrum
Asked:
katredrum
1 Solution
 
gmbaxterCommented:
Do you have static or dynamic vlans?

If static, how about making the computer wait for the network before logon via group policy?
0
 
intellingenceCommented:
We had similar issue while ago and wait for the network through Group Policy seem to resolved it.
0
 
katredrumAuthor Commented:
I actually have the GPO in place, "always wait for the network at computer startup and logon" and is applied to the VLAN6 computers. Any ideas why this is not working?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
AggieTexCommented:
Have you checked that the policy is actually being applied to the computers in VLAN6?
0
 
katredrumAuthor Commented:
Thank you for that suggestion. I've since checked the computer in VLAN6 and they are receiving the policy when I run gpresult but still not being applied with same outcome. I've also noticed that the other policies such as Software Deployment is not working also. Any ideas?
0
 
intellingenceCommented:
Are you sure you can access Server machine on Vlan1 from Workstation on Vlan6? Ping, data transfer, sysvol folder? Also have you got all your sub-nets correctly configured in AD Site and Services?
0
 
katredrumAuthor Commented:
Yes, inter-VLAN routing is enabled and working. Everything works after the user logs in and then I have to manually run the startup script. I checked the event log and it shows event id 1003 EVENT_FAILED_TO_RENEW. Any ideas?
0
 
intellingenceCommented:
For the time being I would deploy Group Policy Object with shortcut placed in users "start up" folder - pointing to your script (ideally it want's to be in sysvol) so you can get your drives mapped once the user logs in.

Also if your software policy does not work, you must have other errors relating to windows client not being able to locate & communicate with DC during start up. Have you got any problems with user passwords not being up to date etc? - this will be down to the windows client not getting ip config before log on. Have you tried differed NIC drivers for your client machine(s) just to see if it goes away. I would also try setting up Windows 7 pro client machine (could be virtual - 30 day trial) and set it up as your physical xp machine with the same Group Policy Objects - same OU - as a test bet.

Can you let us know if you can do that?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now