VMware issue specific client IPs work others don't!

Hi,

I have a server 2012 running Apache and depending on the client IP address on the same LAN depends on whether the page will load from the client. The clients connect both over WiFi and hardwired Ethernet on the same subnet. Then the VM is set to a particular VLAN that is different then the other VMs on that host. Also, RDP is affected in the same way. When the webpage won't load, RDP won't connect. With the 'working' IPs both work.

Thoughts? hanccocka!?
Thanks!
LVL 32
Blue Street TechLast KnightAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

IKtechCommented:
i would look at DNS.  Do all the computers use the same DNS server?  Is there an A record for the 2012 box?

If the IP address works but by name does not something DNS related would be my first guess.
0
IKtechCommented:
Also the hosts file on the computers that can't reach the server by name may have an entry that is causing issues.
0
Blue Street TechLast KnightAuthor Commented:
There is no DNS involved...all clients are using IP addresses to connect.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
what are the IP Addresses, are they being routed between VLANs?
0
Blue Street TechLast KnightAuthor Commented:
Hi hanccocka,

The Server is 192.168.17.10 (subnet 255.255.255.0) and clients are 192.168.17.106-109, which don't work. However when I switch them from 192.168.17.106 to 192.168.17.216 they work. or another client when switched from 192.168.17.109 to 192.168.17.209 they also work.
      
No, all on the same subnet/VLAN

Thanks!
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
those IP Addresses are not in use?

can workstations on 192.168.17.106-109 ping 192.168.17.10
0
Blue Street TechLast KnightAuthor Commented:
Correct, they are not in use.

Yes, they can all ping the server OK.
0
Blue Street TechLast KnightAuthor Commented:
It's bizarre, right!?

So, no one has experienced this before???
0
asavenerCommented:
How is your vSwitch configured?  Do you have multiple uplinks?  What is the load balancing policy?
0
Blue Street TechLast KnightAuthor Commented:
It's a single up-link. Switchport is set as trunk. There are two port groups...one that is on VLAN 1 and used by 4 VMs and another that is set to VLAN 150 and used by the webserver VM. The clients are also on VLAN 150, same network 192.168.17.0.

Do you guys have a list of things to do to setup a VMware VM? Like best practices or just general musts?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Are these clients virtual or physical?
0
Blue Street TechLast KnightAuthor Commented:
Regular Win 7 / XP PCs.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you host a virtual VM, does this work?
0
asavenerCommented:
Is there a router connected to the subnet/vLAN?

If so, can you post the routing table here?  ("show ip route" on Cisco routers)
0
Blue Street TechLast KnightAuthor Commented:
@hanccocka - I haven't tried it.

@asavener - Below is the table:
Gateway of last resort is X.Y.Z.1 to network 0.0.0.0
C 192.168.12.0 255.255.255.0 is directly connected, Phone_System_DMZ
C 192.168.13.0 255.255.255.0 is directly connected, COMM_DMZ
C 192.168.14.0 255.255.255.0 is directly connected, CHATSRVR_DMZ
S 192.168.15.201 255.255.255.255 [1/0] via X.Y.Z.1, outside
S 192.168.15.200 255.255.255.255 [1/0] via X.Y.Z.1, outside
C 192.168.10.0 255.255.255.0 is directly connected, inside
C 192.168.11.0 255.255.255.0 is directly connected, DVR_DMZ
C X.Y.Z.0 255.255.255.0 is directly connected, outside
C 192.168.17.0 255.255.255.0 is directly connected, mobile_wireless
S* 0.0.0.0 0.0.0.0 [1/0] via X.Y.Z.1, outside
0
asavenerCommented:
Can 192.168.17.106 and 192.168.17.109 ping other devices on the subnet, such as the router?  And each other?

Also, after you change 192.168.17.106 to 192.168.17.206, have you tried pinging 192.168.17.106 to see if anything responds?


Can you provide the arp table from the hosts that won't respond to 192.168.17.106?  Perhaps there's a static ARP entry, or something.
0
Blue Street TechLast KnightAuthor Commented:
Interestingly enough, ping always works...and yes, I have tested it in any combination... to and from working/non-working IPs, the WAP, the firewall, the server - all resulted as expected.

I can't get to the ARP table now...but I have checked it...no static ARP. I've tried deleting the dynamic entries from both the PC, WAP, and on the server.
0
asavenerCommented:
Can you telnet to port 80 or 3389?
0
Blue Street TechLast KnightAuthor Commented:
No, I can't. That's the interesting part.
0
asavenerCommented:
OK, if ICMP is working, but TCP is not, then it is not a layer 2 issue.

Next item is to check the firewall on the host running the services.
0
Blue Street TechLast KnightAuthor Commented:
Software firewalls for the clients and servers are disabled.
0
Blue Street TechLast KnightAuthor Commented:
Update: I tried disabling TCP & UDP offload, large packet offload, and TCP checksum offload on the virtual NIC in the VM, which worked or at least I thought it did until the issue sprang forth again one day later.

Now it's back with the same symptoms except I can't find an IP that works!

New approach: We're now switching to using 2 NICs, one on the internal network, one for the wireless, static IPs in the cars and disabling DHCP and eliminating the VLANs.

That's what the manufacturer recommended and we called a neighboring department and that's how they have it setup as well.

I'll keep you posted but let me know if you guys have anymore insights in the event this doesn't end up working. Still wondering what the root cause is.

Thanks!
0
asavenerCommented:
Is it always machines on the wireless subnet that can't connect?
0
Blue Street TechLast KnightAuthor Commented:
Both wired & wireless cannot connect.
0
Blue Street TechLast KnightAuthor Commented:
As an update...I'm looking to call this one (REF: http:#a39539133) as the solution:
We're now switching to using 2 NICs, one on the internal network, one for the wireless, static IPs in the cars and disabling DHCP and eliminating the VLANs.
I'm going check a few things but it looks as thought the solution is stable.

Thanks for everyone's feedback.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Blue Street TechLast KnightAuthor Commented:
I have confirmed the solution is stable. Thanks again for everyone's feedback.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.