Hi Everyone, I was wondering if you could help? I've got a strange issue with an Exchange 2007 (SBS 2008) server. The server is at the customer's head office, and there are 5 remote sites. Hyper V is running, hosting an app server, so there is an additional physical NIC to allow network connectivity. The one physical NIC for the physical server is 192.168.0.1 The other physical NIC for Hyper V doesn't have a static, but an ipconfig shows it picks up 192.168.0.53, and is set to not register in DNS The original problem was anyone from a remote site cannot access OWA (https://sbs-server/owa). Originally thought it could be DNS or a firewall issue...but I got some interesting results back from testing: telnet sbs-server 25 - No response telnet 192.168.0.1 25 - No response telnet sbs-server 443 - No response telnet 192.168.0.1 443 - No response telnet 192.168.0.53 25 - connects telnet 192.168.0.53 443 - connects https://192.168.0.53/owa - connects/works I have checked the advanced settings in Network Connections, and the 1st NIC (0.1) is at the top of the list. In IIS, the bindings for OWA are to all available IP addresses. I suppose I could change it to explicitly use 192.168.0.1, but if it does work it would be a temp workaround, and not a fix. Any ideas would be GREATLY appreciated :)

Do you actually need an physical NIC for Hyper V? I've not tried it yet, but most virtual server products just install their own virtual NIC, and then route through the existing physical one.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m

Yeah unfortunately so... Without one, you are limited to traffic only between the physical and virtual machines (host to guest and vv) ie. clients on the LAN cannot talk to the virtual machines :(

Seems like a strange idea idea to me. Ah well, I guess you will have to do what you already suggested, and tell IIS to listen only on one IP address.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m