Network Profiles
-
If DHCP is running in both places it shouldn't matter about the ranges, the laptop should just pick up the differing information from whichever DHCP server it is talking too at the time. XP is pretty good about that usually. I am guessing that I am missing something about this situation. Respond to this by calling me stupid and saying "phbbbt" and then tell me what I am mis-understanding. Then I will give you a proper answer. :)
Jason Jystad
"Real programmers can write assembly code in any language."
--Larry WallJason Jystad wrote: I am guessing that I am missing something about this situation Well the problem is that the DHCP server at work is handing out 192.168.0.X Addresses, however the work network requires a Static address in the 10.5.X.X range (not exactly sure on this). Maybe this makes more sense. Matt Newman
Sonork: 100:11179 "Whoa, that ruled! What function key do I gotta press to get that to happen again?" - Strong Bad -
Jason Jystad wrote: I am guessing that I am missing something about this situation Well the problem is that the DHCP server at work is handing out 192.168.0.X Addresses, however the work network requires a Static address in the 10.5.X.X range (not exactly sure on this). Maybe this makes more sense. Matt Newman
Sonork: 100:11179 "Whoa, that ruled! What function key do I gotta press to get that to happen again?" - Strong BadAh, so they have static addresses at work and the one you have at home is set up for DHCP. Now I follow you. One way to try to configure this is buy setting up the "General" tab in the TCP/IP properties for DHCP and then go to the "Alternate Information" tab (Something like that anyway, its the secon tab in the TCP/IP properties) and input the static information from work. This should cause it to query for DHCP information first, so this would get him on the network at home, and if that failed it would try to use the static address in the alternate tab which should get him on the network at work. That is how it is supposed to work anyway. :) Or you could try something like this program: http://www.netswitcher.com/[^] (I have never used it but it looks interesting). Let me know how it goes, I am curious to see if either of these work for you.
Jason Jystad
"Real programmers can write assembly code in any language."
--Larry Wall -
Ah, so they have static addresses at work and the one you have at home is set up for DHCP. Now I follow you. One way to try to configure this is buy setting up the "General" tab in the TCP/IP properties for DHCP and then go to the "Alternate Information" tab (Something like that anyway, its the secon tab in the TCP/IP properties) and input the static information from work. This should cause it to query for DHCP information first, so this would get him on the network at home, and if that failed it would try to use the static address in the alternate tab which should get him on the network at work. That is how it is supposed to work anyway. :) Or you could try something like this program: http://www.netswitcher.com/[^] (I have never used it but it looks interesting). Let me know how it goes, I am curious to see if either of these work for you.
Jason Jystad
"Real programmers can write assembly code in any language."
--Larry WallJason Jystad wrote: is should cause it to query for DHCP information first, so this would get him on the network at home, and if that failed it would try to use the static address in the alternate tab which should get him on the network at work. Thats how I had it, but the network is at work is handing out IP addresses, but that DHCP server isn't handing out correct information. Basically they are setting their Wireless AP up as a router X| Matt Newman
Sonork: 100:11179 "Whoa, that ruled! What function key do I gotta press to get that to happen again?" - Strong Bad -
Jason Jystad wrote: is should cause it to query for DHCP information first, so this would get him on the network at home, and if that failed it would try to use the static address in the alternate tab which should get him on the network at work. Thats how I had it, but the network is at work is handing out IP addresses, but that DHCP server isn't handing out correct information. Basically they are setting their Wireless AP up as a router X| Matt Newman
Sonork: 100:11179 "Whoa, that ruled! What function key do I gotta press to get that to happen again?" - Strong BadWhy not create a new user for the home network? That would create a new profile, and a whole new set of networking parameters to match the configuration at home.
"Welcome to Arizona!
Drive Nice - We're Armed..."
- Proposed Sign at CA/AZ Border -
Why not create a new user for the home network? That would create a new profile, and a whole new set of networking parameters to match the configuration at home.
"Welcome to Arizona!
Drive Nice - We're Armed..."
- Proposed Sign at CA/AZ BorderRoger Wright wrote: Why not create a new user for the home network? That would create a new profile, and a whole new set of networking parameters to match the configuration at home. There are 2 users, but they for some reason use the same network settings. Matt Newman
Sonork: 100:11179 "Whoa, that ruled! What function key do I gotta press to get that to happen again?" - Strong Bad -
Why not create a new user for the home network? That would create a new profile, and a whole new set of networking parameters to match the configuration at home.
"Welcome to Arizona!
Drive Nice - We're Armed..."
- Proposed Sign at CA/AZ BorderWon't work, users share network settings. :mad: They share Resolution settings as well. I was really hoping that they would fix that. X|
Jason Jystad
"Real programmers can write assembly code in any language."
--Larry Wall -
Roger Wright wrote: Why not create a new user for the home network? That would create a new profile, and a whole new set of networking parameters to match the configuration at home. There are 2 users, but they for some reason use the same network settings. Matt Newman
Sonork: 100:11179 "Whoa, that ruled! What function key do I gotta press to get that to happen again?" - Strong BadYeah, they will. Same if you use different hardware profiles, though it MIGHT be possible to trick it that way. I have never gotten it to work though.
Jason Jystad
"Real programmers can write assembly code in any language."
--Larry Wall -
Jason Jystad wrote: is should cause it to query for DHCP information first, so this would get him on the network at home, and if that failed it would try to use the static address in the alternate tab which should get him on the network at work. Thats how I had it, but the network is at work is handing out IP addresses, but that DHCP server isn't handing out correct information. Basically they are setting their Wireless AP up as a router X| Matt Newman
Sonork: 100:11179 "Whoa, that ruled! What function key do I gotta press to get that to happen again?" - Strong BadI was afraid you were going to say they were set up like that. X| The only choice in a situation like that is probably to go with a third party program like netswitcher[^].
Jason Jystad
"Real programmers can write assembly code in any language."
--Larry Wall -
Won't work, users share network settings. :mad: They share Resolution settings as well. I was really hoping that they would fix that. X|
Jason Jystad
"Real programmers can write assembly code in any language."
--Larry WallJason Jystad wrote: users share network settings Damn! That's incredibly stupid!!!:mad::mad::doh: Screen resolution, too? Dumb and dumber...
"Welcome to Arizona!
Drive Nice - We're Armed..."
- Proposed Sign at CA/AZ Border -
Jason Jystad wrote: users share network settings Damn! That's incredibly stupid!!!:mad::mad::doh: Screen resolution, too? Dumb and dumber...
"Welcome to Arizona!
Drive Nice - We're Armed..."
- Proposed Sign at CA/AZ BorderYep, my roommate and I regularly face toward Redmond and shake our fists in frustration over the screen resolution issue. What part of "Everyone has different eyes" don't they understand? :rolleyes:
Jason Jystad
"Real programmers can write assembly code in any language."
--Larry Wall