I have 2006 STD configured as my main gateway/firewall for my network (single DHCP ISP connection). Nothing fancy for this small network, but I love to tinker! So (as usual) I have some web server publishing rule or something of the kind that I need to troubleshoot as users from the external/internet side see issues which need to be addressed. But to me, troubleshooting is easiest if done when you can see what the rest of the world sees coming in from the outside. So up until recently I was able to log into a colleagues wireless network and access my network from the internet while troubleshooting from a server console.
I no longer have that wireless connection and would like to know if the follow is possible (and or recommended) Is there any way to introduce an additional piece of hardware such as a router in front of the ISA server which would allow me to access my network as if I were an external/internet user? At the moment our ISP is rather insane with their pricing policy and we are quite content with a single dhcp connection, except for the fact that it only has one address... I have heard of people looking into ideas like putting a simple router in place and forwarding all traffic to the ISA server, but Iíve also heard many issues can arise from that too.
No problem with putting a NAT device in front of the firewall. However, the experience won't be the same as have an external connection, since you need a real external connection to check problems with the NAT device and inbound connection issues that the NAT device might introduce.
Thanks! I was thinking that if a machine was hooked up via a router, then the general ip config would be pulled from the ISP side. So, if I tried to access the full dns name of my network then the query would actually be resolved into that then directed back through. The 'back through' part is what I'm questionable on in terms of what will really happen.