General discussion


IP Address Handshaking

By mashuqju ·
I have two serieses IP address in my LAN within more than 300 workstations and servers. series are 192.168.5.... and 192.168.3....Servers are holding static IP with 192.168.5.... series and all workstations are DHCP enabled. But I am facing problem to handshake between 5 series and 3 series IP of workstations. Some sharing activities violate between them. They cannot talk each other for printer share, file share etc.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by Toivo Talikka In reply to IP Address Handshaking

You are running at least two subnets. Which network mask do you use? How do you handle DNS? Or WINS?

Do the servers act as routers? Do you have one or more dedicated routers and/or firewalls? Have you checked the routing table?

Collapse -

by Jacky Howe In reply to IP Address Handshaking

You didnt specify the OS. Have you setup a Trust Relationship between the File Servers.

Collapse -

by Jacky Howe In reply to

How about rating these answers!

Collapse -

by sgt_shultz In reply to IP Address Handshaking

you do not mention any os? whew. why do they have you tshooting this one? did it used to work? what changed?
don't guess, find out. you have to pinpoint the problem with testing. which sounds like, you have done. to me, the problem narrowed to file sharing and printer sharing suggests a protocol problem. either you need to be running netbios over tcpip or your firewall(s) needs to be letting it through or both. wonder if there isn't something in the security and system Wndows event logs on an affected clients...
you have of course tried with administrator account to rule out permissions problem?
if i were in your shoes i would spend a little and call for MS tech support. it worth it for the education not to mention getting problem resolved. or you could look it up yourself at
you need more clues. you need hard data. the answers to the questions asked in the previous response plus the model of all switches and routers, printers involved etc. operating system versions and patch level...slow down, gather data. just on faith it is relevant. it will get juices flowing...
then go to and search kb. use what you have for symptoms and other clues, probably the big clue is Event ID, Source. look for ideas about more tests to help pinpoint. you may have to come back to kb a few times. the search is funky there these days and you need re-search with completely new parameters if you think something ought to be there but your not hitting....i have better luck Google'ing and selecting the mskb links google finds....

Collapse -

by zaferus In reply to IP Address Handshaking

Please try to keep this question active, if you cannot provide sufficient information it will make troubleshooting like throwing blindfolded at a dartboard.

On the surface it sounds like you are trying to multinet your network. If this is true I would first and foremost look at the L3 device that connects them together.

If this device has any ACL's this could cause problems for devices trying to talk to each other. Also if there is only a 10 MB link into and out of this device it could be bottlenecking your network with 300 systems.

Also, if these systems cannot see each other's DNS and broadcasts are by default disabled across L3 devices - this could be also causing this issue.

More information about your connection specifics as well as what your L3 device is and how it's set up will be key to troubleshooting with you.


Collapse -

by Greybeard770 In reply to IP Address Handshaking

You dont mention a router between the networks. If there is not one, that would be the problem. You can get beyond the limit of a 24 bit subnet (I assume you are using) by changing your subnet masks to 21 bit ( which would let you leave all your IP addresses as they are now.

Collapse -

by BobTheITBuilder In reply to IP Address Handshaking

If you are using a addressing then the network cannot communicate with 3 network. Change you addressing to a 172.16.x.x network (Private Class B). This will alow you to have more hosts on the network (254x254) or if you need more subnets then the 172.16 range will be better for you as your network grows. Good luck

Related Discussions

Related Forums