Samba-Simon
asked on
SBS 2003 & Firewall Issue
Dear Experts,
I have an issue with a SBS 2003 server & 2wire 2700HGV (BT Business Hub) router.
In summary server has static IP address and the relevant ports on the firewall have been opened to allow email etc etc to work. All works fine for about 6 days and then I will not be able to remote desktop into the server.
When I actually physically go to the server - the IP address is as it should be, however when I check the 2wire firewall configuration the IP address of the server has changed! And I really dont understand why?
This is causing me to pull my hair out so any help would be appreciated. If you need any further details please do ask.
Regards
Simon
I have an issue with a SBS 2003 server & 2wire 2700HGV (BT Business Hub) router.
In summary server has static IP address and the relevant ports on the firewall have been opened to allow email etc etc to work. All works fine for about 6 days and then I will not be able to remote desktop into the server.
When I actually physically go to the server - the IP address is as it should be, however when I check the 2wire firewall configuration the IP address of the server has changed! And I really dont understand why?
This is causing me to pull my hair out so any help would be appreciated. If you need any further details please do ask.
Regards
Simon
Irwin W.
The IP that has changed is this the External IP from your ISP? If so you have two options:
- Pay your ISP for a static IP that will not change
- Go to dyndns.com and sign up for a free account. If your firewall supports dyndns, then you can configure your router wit the account info. Now, whenever the firewall's IP changes, you will still get access.
ASKER
Hi Nappy_d,
The external ISP address is static and that is not changing. The issue is that the firewall for some reason has a different ip than the actual server.
Let me try to explain.
for example:
sbs server ip is - 192.168.1.10
external ip is - 100.100.1.90
configure 2wire firewall to open ports for rdp, smtp, etc etc to 192.168.1.10
all works fine for about 5 or 6 days then cannot access the server via RDP or VPN. check the firwall and the config shows ports open to 192.168.1.11. which incidentaly is not a client on the network.
So I dont undertand why this is changing. It is worthy of note that server ip is configured as static on the router/firewall.
thanks simon
The external ISP address is static and that is not changing. The issue is that the firewall for some reason has a different ip than the actual server.
Let me try to explain.
for example:
sbs server ip is - 192.168.1.10
external ip is - 100.100.1.90
configure 2wire firewall to open ports for rdp, smtp, etc etc to 192.168.1.10
all works fine for about 5 or 6 days then cannot access the server via RDP or VPN. check the firwall and the config shows ports open to 192.168.1.11. which incidentaly is not a client on the network.
So I dont undertand why this is changing. It is worthy of note that server ip is configured as static on the router/firewall.
thanks simon
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are you running the latest version of firmware on the router?
ASKER
Thanks so far for the information. I will check the firmware revision. it is interesting to note that this has been seen before.
If you do find a solution other than changing the hardware let me know, as I would be interested to find out.
In my case the router was running the latest firmware, and as I said even 2wire support had no idea.
But unfortunately I still think replacement is the only option.
In my case the router was running the latest firmware, and as I said even 2wire support had no idea.
But unfortunately I still think replacement is the only option.
ASKER
Hi MrJemson,
Thanks so much for the information. I agree that it I may have to swap out the router. This problem has had me pulling my hair out. At least I am not the only one to have suffered this issue. I was starting to think it was a server config issue.
I will keep you posted
Thanks Simon
Thanks so much for the information. I agree that it I may have to swap out the router. This problem has had me pulling my hair out. At least I am not the only one to have suffered this issue. I was starting to think it was a server config issue.
I will keep you posted
Thanks Simon
I don't totally disagree with swapping out the router. In my experience, once with a Sonicwall an firmware upgate resolved an issue. In another with my home Linksys router, I switched from the cheesey Linksys firmware to the DD-WRT firmware and I have been happy since.
Just my $0.02..... :)
Just my $0.02..... :)
ASKER
Thanks for all your advice so far. I did find that the 2wire gateways assign a specific range of IP addresses for static IP addresses. Have reconfigured the server ip to within the static range so hopefully that will do the trick.
Thanks
Simon
Thanks
Simon