Changed IP addresses without reconfiguring port range in firewall....
-
Tuesday, April 10, 2007 3:34 AM
I had set up WHS and four client machines, working okay.
Today I switched them to a different DSL connection so they ended up with new IP addresses from router. They picked up OK and I can access the server from client by IP address.
But WHS does not work. When I try to use the connector software get stringbug error message.
I uninstalled software from client and attempted to reinstall (from share on server via IP address) but still got stringbug error message.
Is there anything documented about changing IP addresses for a WHS network?
Client system is XP Pro, there is an exception in windows firewall for WHS connector.
What I forgot to do was to change the port range in the firewall exceptions on the WHS machine.
That necessitated plugging in monitor and keyboard.
Is there any way to access WHS machine to do this sort of stuff (e.g. access control panel functions) remotely? I guess the smart answer is to have the WHS machine attached to a KVM to make it easier to access when any reconfiguration is necessary.
I suggest there should be a way to explicitly give the ip address of the WHS machine instead of always just letting the client resolve it. This could avoid delays and other problems.
All Replies
-
Wednesday, April 11, 2007 10:13 PMDid you run the server discovery software again on your client?
-
Wednesday, April 11, 2007 11:32 PM
When your IP changed from your ISP it will not affect your LAN connections. Your connector should still fine. I am not sure why you would of lost that connection. Have a look at these threads.
And here is a active bug at connect.
When your IP changed the only thing that will affect is your connection from your WAN to LAN. If you have your ports forwarded correctly, it just a simple, DHCP Release and DHCP Renew. I recently got a new IP too, and nothing was affected on my LAN.
-
Thursday, April 12, 2007 2:26 AM
Hi
I switched to a different DSL connection. Like the first one it went through a NAT router so all that happened is that the WHS server and clients got new non routable addresses (the ones that I had told the new router to give out).
One thing I realized was that the router did not support address reservations, I suppose that is not too significant but might be handy.
My mistake had been initially trying to have client machines on different subnets and entering the address ranges on the WHS server as opposed to simply leaving at default setting of using its own subnet.
What was frustrating was being able to access the shares on the server but not be able to have it work properly.
However I imagine that most of the time the finished product is going to get plugged into a network and the IP addresses given out by the local router are never going to change anyway.
-
Thursday, April 12, 2007 2:30 AM
Yes I ran the discovery software from the WHS server again but it did not work until I fixed the address range on the WHS server.
Most of this problem was my own fault for not realizing I had to change the address range on the server. The only real suggestions I would have is that the server might warn that it was being asked to install the connector software on a machine that it would not be able to access for backup purposes and that there be an option to change the address range on the server remotely.
Once I had things fixed up the only problem I had was a slight delay for one machine while it waited for the server address to be resolvable by name (broadcast?).
